As a non-american, I would have enjoyed the precedent that the logical conclusion had to be that I would not be subject to the laws of the US, when visiting.

The Thomas interpretation must logically have given diplomatic immunity to anyone on an ESTA too.

The very first thing I read now on that site when looking for a good example of this was "Which Linux distribution do you like, and why". You know, it REALLY matters if that discussion is from 1995 or 2025.

Nowadays I tend to close articles if they don't have a year listed. Without the context of knowing if it's from last century, it's often less informative than not reading it at all. It could still be relevant, but the context is very important.

To add insult to injury, some unhelpful people write month and day, but not year.

You want it graphical: Make a webapp.

You don't: Make a TUI.

What exactly is the use case for native apps? Even lots of legacy code can build to WASM now.

(yes, I'm exaggerating a bit, but not much)

They're fast, efficient, work across SSH, in a tmux, and survive the almost daily browser upgrades.

And they are easy to run as separate users without VNC or sandbox hell.

Like do you want to think about X/Wayland isolation, or do you just want to get shit done?

It's very likely that proper punctuation and capital letters help the reader, then it doesn't matter than not using them is faster to type.

I'm sure we've all gotten that big stream of consciousness email that's a 15 line blob of lower case text, with no punctuation or line breaks.

I don't mean every ephemeral message needs to be perfect, of course. Just, you know, readable.

Was that a sharp turn, or was it related in some way?

... At least last I checked.

Because if it's an exact match, then it doesn't help at all with ABI compat, and arguably doesn't add anything. Well, aside from compile time, but that's maybe better solved with modules?

So you're only trying to solve compile time issues (incremental and not)? Maybe the right long term solution is C++ modules, instead? And maybe "just" a matter of having your build environment support modules?

[1] https://news.ycombinator.com/item?id=49034842

I would love to proved wrong, but everything I can think of still leaves a footgun that's easy to trigger by accident, and thus negates the point of the solution.

I think the can't-reference-after-moved-from and objects-are-not-Copy-by-default are key to creating these types (at least enforced at compile time). And that would require major language changes, at least as big as the C++11 changes.

GNURadio consistently uses pimpl for blocks, as I understand it mainly for ABI.

> willing to stop improving.

I think that dismissing it like that shows a naive understanding of execution environments, binary interface design, and in general systems software engineering.

And before it grows too big, it wastes memory. For your use cases it may not matter, and the saved pointer indirection may be more important, but maybe the person who has a million item vector of objects doesn't appreciate a 300% "just in case" memory overhead. The overhead may also hurt cache hits.

If you're doing this to save the pointer indirection, you should benchmark it for every use case, since negative cache effects may dwarf that gain.

Then again, extra padding can also help performance, for some workloads (especially multi threaded read/write against a vector of objects).

So without further context, there's no way to say if your way hurts or helps. It's certainly not a general solution.

So Amazon did not understand FIDO, but J random webmaster is supposed to understand passkeys?

When they eventually remove the old reddit, they'll lose this 18 year reddit veteran. No way in hell am I using that infinite scroll abomination.