Jajcus

We have the same about a shit whip – „z gówna bata nie ukręcisz”

In Poland it is „nosić drewno do lasu” (bring wood to the forest). Similar, but a bit different (pointless not just by being pointless, but by being impossible): „nie zawrócisz kijem Wisły” – ‘you won’t turn Vistula (our biggest river) with a stick’.

Non-toxic glue would be starch or gelatine - both used as base of some ‘real glues’, both with valid culinary use, including exactly this use case. We just don’t call those ‘glue’ in this context.

Otherwise they should be forced to state the game is a rental not purchased if it requires a server that may shut down.

But that is what they already do. Currently this might be hidden in the EULA, that no one reads, but even making this plainly visible during purchase wouldn’t change much. I is not like the players have much choice when they want to play that specific game.

Those would be different kind of regulations. Not just ‘you need functioning brakes’ kind, but also ‘you must serve this route that hardly anyone uses and and you cannot make any extra money from’. Or ‘no extra fees, even where some people would pay them’.

If that means proper regulations (as it should) I bet they would hate it.

And that is the problem with this idea.

Subscription to a software is not mutually exclusive with self-hosting. Developers deserve to earn money, especially those who do not rely on collecting data, showing ads and enshittification of their cloud platform.

Sounds like what happened to Kerbal Space Program 2… it didn’t end well

Didn’t they just move the code that was previously executed in the proprietary kernel module to the new also proprietary userspace driver

Probably. And that is exactly what was expected from them since the beginning of their Linux drivers. Kernel is not a place for such big and proprietary piece of code. So this is the important change.

Yes, the driver is still proprietary, but it does not break the kernel any more the way it did.

But this is the part where being open source is most important. For security, maintainability and convenience reasons

One could even argue if the usespace part, the OpenGl or Vulkan implementation, is still ‘a driver’. (I think it is, at least partially)

Upvote for the great analogy in the last paragraph

Sounds like a mobster kind of favor. If that is true, then it sounds like Sony took advantage of Arrowhead weakness.

Also not a fan of #16 since it sounds to me like forced labour for the poor

That is how actually that worked in some (if not all) communist countries. No unemployment, but people (mostly those ‘undesirable’ for various reasons) would be sent to hard work in bad conditions, which would often cost their health or life. The other side of the coin was: everybody had a job and little fear of losing it, so people rarely treated the work seriously enough. There were factories full of workers, but so inefficient, that nothing was produced in sufficient demand. People had money, but little to buy with it.

Then every charakter would probably need his own AI model, otherwise everyone would know everything, which would not be immersive at all.

‘Pay to show a link’ is the way Google wants us to see this legislation. But linki are not what the news sources are fighting. The problem is Google presents the news and other information in the search result in the way that users often do not need to leave Google and foll9w the link.
Someone produces content so people visit their się and make them money, but those users get the information they want (sometimes incomplete or broken) straight from Google and only Google gets the money. That is not fair and that is what laws like this try to fix (better or worse). But Google and such have powerful propaganda and here we are.

Another thing is: users of services like Reddit or Lemmy also do similar thing (posting content in a way that preventing monetization at its source), so they have extra reason to take Google side.

…and if you are interested in the sound of static rather than the image, then the Polish word is: „szumi”. This can be approximated in English as: ‘shoomy’. The ‘sz’ sound does sound like static.

The funny thing is that our ‘sz’ (in „szumi”) and ‘ś’ (in „śnieży”) usually sound exactly the same to English or French speakers, while for us they are quite distinct sounds.

I am not even able to write it phonetically in English. Ask Google Translate - its pronunciation is close-enough.

In IPA it is: /ɕɲɛʑɨ/

In Poland it was „śnieży” (snowing).

My experience with C++ was when C++ was a relatively new thing. Practically the only notable feature provided by the standard library, was that unholy abuse of bit shift operators for I/O. No standard collections or any other data types.

And every compiler would consider something else a valid C++ code or interpret the same code differently.

I am little bit prejudiced since then… and that is probably where the author is coming from too.

Then things were just getting more complicated (templates and other new syntax quirks), to fill the holes in attempts to make C a ‘high level language’.