reminds me of the "Kurzgesagt – In a Nutshell" youtube video "Why Alien Life Would be our Doom - The Great Filter"[0] that discusses many of the same ideas!
this strongly reminds me of the hn post from five days back in which the main thread talked at some length about a very similar scenario
> "He missed a big one: you have no way to stop Linux distributions from hacking up your software, and you'll suffer the consequences of whatever they do."
"respectful" as in let's wait years for a maintainer to come up with a solution and when we try to propose our own the maintainer trows a fit and turns it down?
Eh. Although we don't always do things perfectly, Fedora has a pretty strong policy of working with upstreams first.
By contrast in my personal experience as a developer of something that got packaged in Debian, I discovered later that that package had a bunch of patches added, a man page written (!) and so on, none of which was bad, but also none of which was fed back to me at all.
(In case not obvious: I work for Red Hat on Fedora.)
this reminds me of the documentary "the fog of war"[0] in which robert macnamara talks about the conventional type bombing of japan's cities with firebombs before using any atom bomb.
Iraq and Afghanistan have each 5 times the population of Israel, and only 33% more aid than Israel. Also, both Iraq and Afghanistan are desperately poor countries against which the US waged war, causing further destruction. What's the reason for Israel's aid?
Hm. I see very well what the US does for Israel: 4.5 billion in military aid, constant international support (vetoed 44 UN security council resolutions against Israel), passed illegitimate laws in several states to punish those who support a boycott of Israel, recently recognized the illegal annexation of Jerusalem and the Golan Heights, puts orthodox Jews in charge of drafting peace plans with the Palestinians, etc.
But what does Israel do for the US? It's not very clear to me. The only thing I know of is intelligence. Is that enough? I think even Saudi Arabia provides much more support: military bases, etc.
[...Quebec Premier François Legault said that SNC-Lavalin was one of ten publicly-traded companies headquartered in Quebec that the province considers to be "strategic" and therefore in need of protection from a takeover that would force the company to leave the province....]
this video[0] from "mentour pilot" on youtube explains the stabilizer system quite well.
it seems the trim wheels are connected manually to the trim mechanism in the back, but when the trim stabilizers are in an extreme position the wind loading on them makes it very hard/impossible to rotate the trim wheels manually.
from what i understand, one way to relieve/lessen the wind loading so that the manual wheels can be used again is to (in the case of trim down) dive the plane. this would lessen the wind loading on the stabilizer and allow the manual wheels to move again. but you would need "room" to dive, something they did not have in this case.
Its possible and I think it was demonstrated in one of Mentour Pilot's videos that both pilots can work together to manually trim. Boeing put notes in the manual that this may be needed and it would not break the manual trim system to apply that much force to the trim wheels.
the fact that the combined strength of two humans would not be enough to _break_ the manual trim system does not tell us whether that combined strength would be enough to _turn_ the trim wheels at all.
https://news.ycombinator.com/item?id=19575318 "option 2)" (on this same page) refers to a situation where a "dive" could be executed in a situation where manual strength is not enough to trim the aircraft.
Recall that at the same time it's taking the strength of both pilots on the yoke to keep the plane approximately level. You're saying they should both let go at low altitude and see if they can crank a trim wheel together?
the cloop[0] system from knoppix is something i use often to back up arbitrary file systems. debian has the cloop-utils which includes create_compressed_fs, and this is great for making compressed copies of file systems which can then be read without uncompressing the whole blob.
however i have found debian's cloop-src module to be problematic in that i have never been able to get it to compile. the actual module comes as source only, and without this part it is not possible to read the backups without uncompressing, which is a shame. in fact it appears debian has recently removed cloop from debian testing[1] for this reason.
so it is still necessary (and enjoyable) to have knoppix around to use the decompression system, although it is a huge pain to do it this way. i hope debian is able to get things sorted finally with cloop-src! that would be great.
the difference that i find valuable is that cloop is not a file system, whereas squashfs is. this means that i can use cloop to compress _any_ file system at the block level. very useful as a sys-admin.
what about cinerella? when i researched what video editor to learn next after kdenlive it was cinerella. it seems to work fine, and i am surprised not to see any comments regarding it. seems like it is completely out of the running?
[0]https://www.youtube.com/watch?v=UjtOGPJ0URM