Features are deprecated and removed. It's uncommon but it happens when a new feature makes all use of the old feature unnecessary. Usually it's deprecated for a few versions and then removed some years later. You can always compile old code against an old standard.

C++ does have many ways to do anything. Most of that is historical, or due to features and library facilities with overlapping capabilities, or inherent to multi-paradigm programming languages.

Every C++ project is written in its own language. Its own "house flavor." This is true of all languages, but is particularly stark for a language as old, complicated, and powerful as C++.

There is std::valarray, but a google search said that only Intel's implementation uses SIMD. See [cppreference][1].

[1]: https://en.cppreference.com/cpp/numeric/valarray#Notes

It's shear complexity because it's about cross-cutting concerns, or because it's a difficult yak to shave.

You returned a pointer to a temporary. It's nasty but easy to spot.

Would you return `input.c_str()`? You might think twice about that, but it's the same thing. My favorite fix is to take a `std::string_view` as the parameter.

    string_view remove_leading_spaces(string_view input) {
        auto new_start = find_if(input.begin(), input.end(), [](char ch) { return ch != ' '; });
        return string_view(new_start, input.end());
    }

The result of the undefined behavior in your program is surprising, though. As it usually is.

I remember reading a blog post or something about VPN providers complying with law enforcement requests. The author said "Those companies can't afford a lawyer. They can't afford a lawyer's _coffee_." I don't know if that's the case here, but I don't expect any network-tech-as-a-service company to put up a fight for anything.

Passing allocator pointers around has the advantage of allowing you to customize the allocator when you want, and to ignore it when you want (which is most of the time), i.e. just use the allocator you were given and pass it around like some piece of syntax or ctx in Go.

The trouble comes when you have data structures that manage memory, and you want to associate the allocation strategy with the particular instance of the data structure. Or, worse, you don't store the allocator pointer with the data and you require that all functions operating on the data structure happen to use compatible allocators.

At its simplest, though, passing allocators around is just removing an implicit global variable that is sometimes helpful to customize locally, but nearly impossible to customize locally if left as a global.

Cars are different nowadays (hopefully even more reliable), but the '95 Toyota Camry that my parents bought new in 1995 or 1996 lasted until I was done using it in college in 2011. Then my dad sold it for a chunk of cash. The only thing wrong with it was that the roof paint was gone to shit from the Florida sun. You could probably paint it, redo the ceiling fabric, and run it for another 10 years. They sunk a fair amount into it over the years, but nothing catastrophic -- no powertrain issues, no "fixing this AC will cost more than the car" issues. In the six years I drove it I think it needed about $300 of work (something about the steering or suspension).

There are lots of Camry from 2008 to 2017 which has paint delamination issue. Ours is from 2012 but it only started getting noticeably worse near the end of the warranty period and I never heard about it because it was during the pandemic and our dealer went out of business. Toyota didn't publicize the issue till the end.

There's also the scene with the baby in Children of Men, and the synthesized long single shot in 1917.

If you enjoy good action movies, Extraction 2 has long single shot action scenes too.

I like the writing in this article. The author did warn us, but the punchline takes a while to get to:

> I’d like to be clear that there are legitimate uses of remote attestation. By using a website that requires attested passkeys you can be sure you stay safe from accidentally installing a scammer’s fake passkey application that steals your data – the website will reject such a passkey. You might want an attested Passkey even if the website doesn’t require it, since you can use attestation to verify that your software has not been tampered with by a hacker while you weren’t looking.

> As for reasons to not want attestation: you might want to be able to use software that Twitter (formally X) doesn’t specifically approve of, such as Linux. Or a phone with a refurbished operating system.

So the bad timeline is the one in which the industry gradually transitions to "you can't log on unless everything about your system is exactly as we want." Figures.

> such as Linux

Before anybody thinks "surely they can't ban all linux users", they don't need to. The systemd folks are also working on a startup that is building verifiable computing into Linux via systemd. So, we have no choice on the matter anyway. It could become of choice of approved distro vs non approved distro.

> So the bad timeline is the one in which the industry gradually transitions to

We have been on that timeline for every other tech transgression. There are no signs that this will be a different timeline.

They would have to start by banning Apple users. Apple does not support attestations from consumer devices. Apple has said multiple times they see it as a consumer privacy violation.

I wish.

https://news.ycombinator.com/item?id=46784572

Private window is called out in the article as creating a second entity