If you haven't figured out that 'the peasants' pay for everything, you're just not figuring anything out. Blaming is not understanding.

'We' pay for everything.

It's in the summary.

You should go find out, then let me know.

Yeah it's actually perfectly fine for daily use if anyone actually cared to try it. Even "less competent" programmers would figure it out with not much time.

These days we mostly choose languages for library availability, not for features of the language.

In science,the way "wrongness" is fixed is by experiment. The only way to decide one way or the other is to collect more data.

The summary says the data was wrong, and the camera system reported he was present when he was not.

Not from you, that's for sure.

Thanks.

Forget about relying on people.

Rely on facts. That's the scientific way.

"Got a designer baby, but I'm a good parent so I won't vaccinate that kid."

Some people are able to read scientific studies and understand them to figure out what is true or what is not.

A large segment of the population is unable to read much at all, and relies on consensus to determine what is true and what is not. So when there's a question, they ask all their friends, their therapist, their husband, people around them, and get people on their side.

The people in the second group are VERY confused about life, but they are too large a segment of the population to ignore.

No.

The main aim of Stop Killing Games is to ensure the practice of rug-pulling eventually comes to an end. They are not trying to save MMOs, for example.

Moreover they don't demand that every game currently on the market comply with open-sourcing requirements: at a minimum, companies always have the option of simply providing customers with adequate notice before shutdown. Open-sourcing the server would be nice, but it's hardly the only way to protect consumers' interests. Scott has, for example, suggested game boxes being marked with an estimated expiry date for online service functionality.

But most importantly: because this is about future games, not the present, the market has time to change. If studios and publishers are designing their games with a fair EOL in mind, then they can make decisions from the get-go to avoid licensing dependencies that they won't be able to release in a possible 'afterlife' version of the game. As suggested by your example of GameSpy in C&C: Generals, when a commercial dependency is crucial to a game's success, it tends to be a client-side library, but typically the problematic dependencies aren't crucial; they're e.g. add-ons for Unity or Unreal that the studio bought to save time. In a world with SKG laws, the providers of these dependencies aren't going to be a stagnant target either—demand for compliant libraries will motivate development of open-source versions.

Interestingly, the will for doing this does exist among game developers; they just need the institutional support from legislation to twist the arms of the studios and publishers. Ross Scott has talked to a lot of devs who are burnt out from having their projects cancelled, leaving them with huge gaping holes in their resumes and portfolios where they've spent years on unreleased projects that are stuck under NDA. In general they tend to see SKG as a path to ensuring the games that do see the light of day aren't also scrapped, which would erode their work histories even further. (Apparently it also just plain feels bad to have your work erased from history. Shocking, I know.)

I remember back in 2001 reading in the newspaper that the next OS from Apple was going to be based on Unix. I thought, "Wow, I guess Apple won't be dying after all." A massive upgrade over System 9, and clearly better than Windows.

OOP is a way to organize your code.

LISP doesn't give any guidance at all on how to organize the code, but it is an extremely flexible language. The flexibility allows creative people to come up with new ideas and test them immediately. That is how Alan Kay came up with Smalltalk, which is a close cousin of Objective-C.

It's where Javascript came from (an excellent language for its original purpose: setting values). It's where the concept of the | in unix came from.

But LISP is not an easy language: the programmer needs to find the beauty. That is why it is not suitable for work: when money is involved, beauty goes out the window.