josefx

Within the context of this discussion portability was mentioned as key feature of the standard. If C23 adoption is as limited as the, possibly outdated, tables on cppreference and your comments about gcc, clang and msvc suggest then the functionality provided by the gcc attribute would be more portable than C23 conformant code. You could call it a de facto standard, as opposed to C23 which is a standard in the sense someone said so.

> GCC, Clang and even MSVC

Well, if that is the standard for portability then may_alias might as well be standard. GCC and Clang support it and MSVC doesn't implement the affected optimization as far as I can find.

Doesn't that just describe low level file IO in general?

> non-standard extension and thus not portable

Modern versions of standard C aren't very portable either, unless you plan to stick to the original version of K&R C you have to pick and choose which implementations you plan to support.

These "edge cases" were required knowledge to get a license in my home country. You make room for any emergency vehicles, you don't try to score an ultra kill when passing a school bus and you certainly don't drive on rail tracks.

Wouldn't AI be trained on data using innerHTML?

> An ABI can't control whether one or both parties either end of the interface are honest.

You are aware that Rust already fails that without dynamic linking? The wrapper around the C getenv functionality was originally considered safe, despite every bit of documentation on getenv calling out thread safety issues.

> ... position is silly and wrong.

Both positions were build on top of aether, quintesence and Celestial Spheres. The result was silly and wrong no matter which one you picked.

Does it actually use voxels? I thought it was just a low poly, "voxel like" art style.

I actually wasn't aware of that language. It was more a reference to the overblown claims Pike made in the early days of Go, where he presented it as the c++ replacement for everything Google.

I heard they once created an entire language that would replace C++ in all their projects. Obviously they never rewrote Chrome in Go.

> 10s of billions are spent to try to get Chromium to not have these vulnerabilities, using those tools. And here we are.

Shouldn't pages run in isolated and sandboxed processes anyway? If that exploit gets you anywhere it would be a failure of multiple layers.

> A good example of that for arm would I guess be something like fingerprint or face id.

So operations that are not performance critical and are needed once or twice every hour? Are you sure you don't want to include a dedicated cluster of RTX 6090 Ti GPUs to speed them up?

You leave out that they can keep it in a warehouse at the other side of the country for pickup and there is no law saying that it cannot be further away than the point of origin. Fun times.

Sadly I rarely see an option for "place it with a neon sign on my front porch" when I order things online, because the chance of having things stolen would often be preferable to a daytrip to the middle of nowhere.

It is 2026, people still use cheat software on public servers. It works about as well as DRM.

> Vendors couldn't care less.

There are more than enough games that are designed around microtransactions that use grind and gambling mechanics to encourage spending. Throw bots and cheats at that and the entire thing breaks down.

Shipping GPL headers that explicitly state that they are part of GCC with a creative commons licensed compiler would probably make a lot of people rather unhappy, possibly even lawyers.

I prefer the question about CPU pipelines that gets explained using a railroad switch as example. That one does a decent job of answering the question instead of going of on a, how to best put it, mentally deranged one page rant about regexes with the lazy throw away line at the end being the only thing that makes it qualify as an answer at all.

RFC822 explicitly says it is for readability on systems with simple display software. Given that the protocol is from 1982 and systems back then had between 4 and 16kb RAM in total it might have made sense to give the lower end thin client systems of the day something preprocessed.

I think it will be quite some time before you can prompt Genie for the next GTA, Skyrim or Call of Duty.

Money from Google internally might be subject to internal power dynamics and come with strings attached. Having reliable outside funding from people who don't get a say in things might be a better alternative for a project that doesn't want to end up as Stadia 2.0 .

> You can easily trade gold if ww3 starts

If you want something you can trade post ww3 also stockpile alcohol, tobacco, coffee, etc. . Small luxuries everyone will be willing to trade for in a post war country.

> it's the compositor doing an internal optimzation to avoid a copy when it's not necessary.

Yeah, it avoids doing the compositing part of being a compositor. It bypasses the entire pipeline.

They are citing a blog post from the German magazine Auto Bild, which talks about the Auto Bild special "TÜV Report" edition. They are probably three or four layers of indirection removed from the original report produced by the TÜV itself.

I found a mention of the report on this page from the ADAC: https://www.adac.de/news/tuev-report-2026/

I think they mention suspension, brake and light related issues.

> I don't think Wayland ever supported

Isn't that true for even the most basic features you expect from a windowing system? X11 may have come with everything and the kitchen sink, Wayland drops all that fun on the implementations.

GNOME does unredirect on Wayland since 2019: https://www.reddit.com/r/linux/comments/g2g99z/wayland_surfa...

> Windows killed it

They replaced it with "Fullscreen Optimisations", which is mostly the same, but more flexible as leaves detection of fullscreen exclusive windows to the window manager.

https://devblogs.microsoft.com/directx/demystifying-full-scr...

As far as I can find the update removed the option to turn this of.

It isn't always pure overhead, but also jitter, additional delays and other issues caused by the indirection. Most systems have a way to mostly override the compositor for fullscreen windows and for games and other applications where visible jitter and delays are an issue you want that even on modern hardware.

Security certifications are one reason. OpenSSL maintains a module for FIPS compliance, which includes an entire boatload of weak and broken algorithms nobody else bothers with.

> Conan and vcpkg exist now and are actively maintained

I am not sure if it is just me, but I seem to constantly run into broken vcpkg packages with bad security patches that keep them from compiling, cmake scripts that can't find the binaries, missing headers and other fun issues.

It is pretty consistent. It is part of the C Standard and a feature meant to make string handling better, it would be crazy if it wasn't a complete clusterfuck.

> Even if a machine generates them.

Why? If it is a purely machine generated report there is no need to have dozens of third parties that throw them around blindly. A project could run it internally without having to deal with the kind of complications third parties introduce, like duplicates, copy paste errors or nonsensical assertions that they deserve money for unrelated bugfixes.

A purely machine generated report without any meaningfull contribution by the submitter seems to be the first thing you would want to exclude from a bug bounty program.

Aren't all Microsoft products OpenAI based? OpenAI has always been burning money.

> one, unnecessary destructor calls on moved out objects

That issue predates move semantics by ages. The language always had very simple object life times, if you create Foo foo; it will call foo.~Foo() for you, even if you called ~Foo() before. Anything with more complex lifetimes either uses new or placement new behind the scenes.

> Another one is std::shared_ptr.

From what I understand shared_ptr doesn't care that much about performance because anyone using it to manage individual allocations already decided to take performance behind the shed to be shot, so they focused more on making it flexible.