french fries are pommes frites. the french term is also used in germany (though sometimes shortened to pommes or fritten).

a term falling out if use does not make it foreign. even if no longer common pommes frites is still a french term. the french wikipedia page also does not give any indication that the term is no longer used.

whether client-side rendering exposes alternative content really depends on how the code is actually written. i could still send different data depending on the type of client. but i agree with the general point.

i actually used that server-side approach to achieve something like that on an old site. that was before client-side rendering was a thing. i had sections of content that by default were folded, so you would only see the headline had to click and load a new version of the page with the content open, but for a search engine the server would serve the page with all sections opened and none of the headlines clickable.

when building an airplane one of the goals is to figure out what you can remove without affecting the stability of the plane. performance (use of fuel) matters here too. so it's kind-of the same thing?

it's not double jeopardy because they are being tried for different crimes at each court. splitting up trials is not uncommon. not just because of jurisdiction.

how did netflix manage to use blender then? doesn't seem to be that much of a showstopper.

distributions started out with solving the problem that most developers at that time didn't even bother to build ready to run packages. they couldn't, because there were to many different architectures that not everyone had access to. so developers had to rely on users to build the applications for themselves. distributions then organized around that to make this easier for users. that's how the port system in BSD came about. linux distributions went a step further and built distributable binaries.

the problem was to not predict that developers would want more control over the build of their applications, which, thanks to architectures consolidating, became easier because now a single binary will reach the majority of your userbase. and the need to support multiple versions of the same library or app in the package manager. that support should have been there from the start, and now its difficult to fix that.

so it's unfair to say distros are wrong. yes, it's not an ideal design, but this is more of an accident of history, some lack of foresight, and the desire to keep things simple by having only the newest version of each package.

there is a conflict between the complexity of supporting multiple package versions vs the complexity of getting applications to work with the specific library versions the distro supports. when distros started out it looked like the latter would be better for everyone. distributions tended to have the latest versions of libraries and fixing apps to work with those benefited the apps in most cases.

the threat here is not "cloud losing your data". the threat is "cloud denying access to your data". it's like when someone breaks up with you and you still have stuff at their house. good luck getting that back.

the way i understand it is that the law says decisions must be reviewed by a human (and i am guessing should also be overrideable), but this still leaves the question how the review is done and what information the human has to make the review.

exactly this. FOSS was always driven by those who could code and did so driven by their own intrinsic motivation. those people won't disappear. there may be less people because some are more driven by quick results and while in the past they had to code to get there, now they don't, which means they won't discover the joy of coding.

but for others coding will become an art and craft like woodworking or other hobbies that require mastery.

People wrote code in the hopes that others would read it think positive about them and maybe improve things. Those projects are going away

having been involved with FOSS for more than 30 years, i never came across that sentiment. not that it didn't exist, but i'd guess it is a small minority. people who write code to feel good about themselves likely don't make good project leaders anyways. they won't be missed.

People write code for a variety of reasons but the ones who stop coding and spend time trying to publicize their project generally want people's attention. They find pleasure in sharing.

People will still write code for a variety of reasons but why bother sharing if no one is listening.