Removed by mod

Source?

In the EU at least this is demonstrably false. LNG has slightly risen since 2000 but other fossil fuels (namely coal) have gone way down. Total consumption has been steadily declining in the past few years and is down to 2004 levels. So overall our electricity is a whole shitload cleaner.

The story is even starker for domestic heating. Gas and coal are vanishing since the mid-2000s.

There’s probably a whole thesis or five to be written on the subject.

The “traditional” AAA pipeline is “make big games with loooots of assets and mechanics, maximize playtime, must be an Open World and/or GaaS”. Both due to institutional pressures (lowest common denominator, investor expectations for everyone to copy the R* formula, GaaS are money printing machines) and technical reasons (open worlds are easy to do sloppily, you can just deliver the game half finished and have it work (e.g. Cyberpunk), GaaS/open worlds are a somewhat natural consequence of extremely massive development teams that simply could not work together on a more narrowly focused genre).

That’s not to say there aren’t good expensive games being payrolled by massive studios like Sony or Microsoft. But AAA is a specific subset of those, and blandness comes with the territory. However if I was a betting man I’d say we’re nearing the end of this cycle with the high profile market failures of the last few years and the AAA industry will have to reinvent itself at least somewhat. Investors won’t want to be left holding the bag for the next Concord.

I would argue that Valorant or CS are terrible games for casual enjoyment anyways. The skill floor is already pretty damn high for a shooter.

In the FPS genre I’ve found Battlebit has faithfully replicated the feel of BF3/BF4 for those of us who just want to run towards the objective and shoot, and it had old school community servers.

The competitive scene happened. Can’t have meaningful competitive matchmaking against the same 100 players. People don’t just want to frag noobs, they want to grind the ladder to be able to say “I’m GE and you’re Gold, therefore I know for a fact I’m better than you”.

This is a global phenomenon. Even goddamn chess has this, first thing players ask each other nowadays is “what’s your chess.com ELO”.

I’m not a competitive player myself but I get why people rush after ELO progression. And it’s not much of a stretch to say CS, Valo, and especially chess wouldn’t have seen such widespread success without competitive ELO-based matchmaking.

It’s not about the bindings. It’s, as always with kernel devs, about gatekeeping and unprofessional if not outwardly hostile behavior.

Maintaining bindings is a hard problem for sure, but no hard problems have ever been solved by the key stakeholders refusing to partake in honest discussions. Asahi Lina’s breakdown of her rejected contributions to the fundamentally flawed drm_sched, which do not involve a single byte of Rust, demonstrates an unwillingness to collaborate that goes much further than the sealioning about muh bindings.

… What’s that about culture war bullshit? Whatever corner of Xitter that youtuber went scurrying under, there’s like a couple dozen people there.

Some people (conservatives and some absolutely brainrotted terminally online leftists) love attributing sales data to Wokism or Wokism being Defeated. thisengineiswoke.jpg.

Literally no-one actually cares, not even conservatives, because they sure as shit play Elden Ring despite the character creation presenting gender as “A” and “B” or whatever. It does not matter. “Go woke go broke” is a literal fucking meme. If people actually cared about gaming politics then FIFA wouldn’t be one of the top selling games every year and reddit would have killed pre-orders as a practice 10 years ago.

The game is bland, a cheap knockoff, already very old-fashioned, infinitely too expensive, terribly marketed and uniquely non-appealing. That’s it, no need to bring weird politics into this.

Without good and realistic answers to how the long-term maintenance of such changes would be managed, it is myopically unrealistic to propose those changes

Lina is talking about a minor change though. It challenges the dominant paradigm but her opinion seems to be that it doesn’t have negative impact on the overall maintainability. To shift the discussion to maintainability is whataboutism; if these kernels maintainers can’t accept patches that do not have a negative impact on maintainability or directly involve Rust in any way because they are related to Rust in general, that’s disappointing tribalism regardless of your opinions on Rust or Rust developers.

I might be missing some context here as I’m only going off what Lina has said, but if half of it is true then we need to shift attitudes before talking about how to integrate Rust in the kernel ecosystem. It certainly feels very disingenuous and retrograde to present Rust as some kind of existential threat rather than a novelty or opportunity, as if no combination of processes and tools could ever possibly overcome the stated maintainability challenges.

The vibes I got in the other thread about Wedson’s announcement is that the concerns may be valid but there are indeed a handful of contributors who are aggressively shouting down Rust contributor’s efforts to set up the processes you outlined based on hard prejudice. The video Wedson posted was hard to watch. From the outside looking in it looks to be way more about ego than any particular technical roadblock.

Furthermore Lina’s concerns here are only broader what you are saying:

When I wrote the DRM scheduler abstractions, I ran into many memory safety issues caused by bad design of the underlying C code. The lifetime requirements were undocumented and boiled down to “design your driver like amdgpu to make it work, or else”.

My driver is not like amdgpu, it fundamentally can’t work the same way. When I tried to upstream minor fixes to the C code to make the behavior more robust and the lifetime requirements sensible, the maintainer blocked it and said I should just do “what other drivers do”.

Mainlining memory safety improvements, in C, for C code should be welcomed and it is very concerning if she indeed got shunned because the end goal was to offer lifetime guarantees (which to my admittedly non-expert eye sounds like it would be a good thing for memory safety in general).

The concern from those contributors (and we might soon see the same in QEMU) is that these bindings are essentially a weaponization which forces the great majority of contributors to learn Rust or drop out. Essentially a hostile takeover.

Seems like a moral panic over absolutely nothing (where are the Rust developers allegedly forcing people to learn Rust? all I’ve seen in these threads today is Rust developers asking for an open mind and a willingness to collaborate), and that the response to this “concern” is to block any and all changes that might benefit Rust adoption is really concerning (but unfortunately not unsurprising) behavior.

I think that is the most controversial take I have read in my entire life.

What good has Microsoft done for Mojang/Minecraft? They kneecapped development by splitting the codebase and tying most features to their ability to run on mobile hardware, slowed development to an absolute crawl to increase long-term revenue (these motherfuckers openly develop three new features for minecon every year, then delete two of those for no reason other than “we can”), turned the console/mobile versions into garbage microtransaction boxes, started policing private speech in private servers hosted on private hardware, turned the mod-supporting version of the game into a second-class citizen, basically made for-profit private servers illegal, etc.

Minecraft was a great game that stood on its own merit when Microsoft bought it. Everything they did only brought it down, and the few good features the game has gained since then were long overdue and done despite Microsoft’s meddling.

So you’ve never once in your life bought a laptop or prebuilt PC, used or otherwise? Because if you have then you’ve paid the Windows Tax.

I’ve read the exact same comment a year ago, and the year before, and probably the year before that tbh.

So I’ll say what I always say; I’ll believe it when I see it.

“Color terminal” isn’t a thing. Applications can choose to output ANSI escape codes which most terminal emulators will render as color changes. Whether and which colors get used depends on the value of $TERM, which informs the application of the capabilities of the terminal emulator.

So if your remote servers don’t have color, either $TERM isn’t being set or its value is unknown to the server. Most modern terminal emulators support at least the same escape codes as xterm-256color though so you can always try to export that.

I’m just surprised the purists aren’t all up in arms that this isn’t KISS and that it doesn’t fit in their 80x24 teletype.

… sorry, guess I’m not over that whole systemd “debate”.

Anyone can fork at any time. The US gov could theoretically hold Wikipedia’s brand and servers hostage, but the actually valuable stuff is already mirrored in a decentralized fashion that is completely unrestricted under US and international law.

EDIT: Maybe you meant that the US could covertly vandalize Wikipedia? Maybe, if they keep it very low-key. Editors are used to this kind of stuff though, it happens all the time from all governments since they can just, y’know, edit it. Anything actually impactful will be noticed by the editors which will just cause a fork.

Wikipedia also releases all content for free download under a permissive license, so I don’t think it’s fair to say that the US government is a meaningful threat to its quality of information, especially over non-English languages that are managed by an independent set of volunteers who could pack up their bags and move everything over wherever they want at any point.

Still a cool project and technological diversity is good though.

There are quite a few mature projects in 0.x that would cause a LOT of pain if they actually applied semver.

I am generally of the opinion that version numbers do not matter at all until the author/distributor has GUARANTEED that they do. Until then they’re worthless, including in places where semver is supposedly enforced like NPM. If I had a penny for every NPM package that broke my project after removing the package-lock.json, I could retire.