I thought you were talking about cloud compute and I was interested, but then I saw that it's just cloud file storage.

I'm pretty sure that's a sidequest in Starfield. The ECS Constant colony ship set off in 2140 to colonise a planet, arriving in 2330 at the planet Paradiso, which had become a luxury resort planet for the rich, because shortly after the ship left, humanity invented the grav drive and every ship just zoomed right past them.

It's a good thing I trusted my instinct on that one. Any MMO with a 'founders pack' prior to release is a scam, or if it's not a scam, it says that the developers have no faith in their product and want your money now while they don't have to actually deliver anything of note.

Only 150 light years away?! Wow, that's practically next door! Now all we need to do is figure out how to go light speed and even then it'll take a further 300 years just to know if the colonists got there safely or not!

The more I think about the late 90s and mid 00s, the less I want to go back to it. What I want is to not know things, not know how horrible things are, because I know things in the 90s and 00s were horrid too, I was just too young to notice.

I'm sure there are some people out there that have nostalgia for 2012 because that's when they were a child. I remember the massive push for Ron Paul 2012 and how insufferable everyone was.

Only if you're going by the strict UML definition of composition, which doesn't really apply here, since the industry has moved on a bit since UML was king.

Either way, you can use DI to do composition in the strictest UML way, provided every single dependency is transient and creates a new instance every single time. Even then though, when most devs talk about composition, they aren't referring to the strict UML definition.

If you've used Dependency Injection before, you've used the principle of composition over inheritance. So, if you've ever used .Net (C#), Spring Boot (Java) or Laravel (PHP), you've likely used it. Modern C++ also has the DI pattern.

Rust and Go force you to use composition and don't support inheritance at all, so if you've used either of those languages, you've followed the practice, though Go doesn't support DI out of the box. Functional languages like Haskell also use composition over inheritance.

all of them?

I'm not sure what you mean? Doing composition over inheritance is considered good practice across the board, regardless of whether it's frontend or backend.

Always favor composition over inheritance if you can.

"passive consumers of unthought thoughts" is an apt way of putting it. With AI, it's so easy not to think and have it think for you, even in things that you should really want to think about because it's entertaining.

For example, I've been re-watching Game of Thrones, and I wondered how things would have changed if Joffrey had a father figure in his life that wasn't Robert, say a teacher in swordsmanship. I could spend a lot of time thinking about how Cersei would see this teacher as a rival and want him dead, whether Robert would protect that teacher because he's making Joffrey into more of a 'man', whether Joffrey being trained as a swordsman would make him braver, and even if everything happened as written up to the Blackwater, would Joffrey find his courage and go out into battle, and ultimately get killed by one of Stannis' soldiers? What would happen to Sansa?

Or... I could just ask ChatGPT, get a quick answer, and forget all about it.

Elon Musk immigrated from South Africa to the US, so I can think of at least one thing that made things distinctly worse in the US at least.