palordrolap

Sounds a bit like the S&M methodology. SpaceX & Musk

JavaScript, like some other languages of the time, was designed with the Robustness Principle in mind. Arguably the wrong end of the Robustness Principle, but still.

That is, it was designed to accept anything that wasn’t a syntax error (if not a few other things besides) and not generate run-time errors unless absolutely necessary. The thinking was that the last thing the user of something written in JavaScript wants is for their browser to crash or lock up because something divided by zero or couldn’t find an object property.

Also it was originally written in about five minutes by one guy who hadn’t had enough sleep. (I may have misremembered this part, but I get the feeling I’m not too far off.)

I’d say it’s more like setting up a handler for a callback, signal, interrupt or something along those lines.

Function declarations by themselves don’t usually do that. Something else has to tell the system to run that function whenever the correct state occurs.

That doesn’t account for unconditional come-froms.¸but I expect there’d have to be a label at the end of some code somewhere that would give a hint about shenanigans yet to occur. Frankly that’d be worse than a goto, but then, we knew that already.

perl -le 'use bignum;print+pack"H22",(61966753*385408813*916167677<<2)->to_hex()'

Alas, Perl doesn’t bignum by default

The first one is clearly wrong because no-one (oh alright, almost no-one, Toe-Jeans Georg) wears leg-wear on our toes.

Third option: The top layers are covered by a poncho and only the eight pairs at the bottom have leg-wear. This works when considering each subtree as a separate tree in its own right, up to arguing about how many ponchos are then required.

Fourth option: The top two branches wear leg-wear and those below go in footwear of some sort.

Chances are that many large entities are in too deep. It’s what Microsoft were counting on before the backlash, and now they’re probably going to do it by stealth instead.

If I have to use Windows, I want the configuration of Windows that will run on the computers at a country’s top intelligence agencies.

Because sure as hell those places will have it locked down and not sending one solitary thing back to Microsoft, whether they have to configure it themselves or put the fear of the unholy into Microsoft to get that to happen.

And if not that, the configuration that Bill Gates or Mark “I put tape over my webcam and deactivate my mic for no particular reason” Zuckerberg will use.

Lawful good is asking for trouble. Before they know it, they’ll be inundated with e-mails to their personal company address with poorly worded help requests. They’ll spend half their time making and updating tickets on the user’s behalf that would have been mostly automatic if they’d gone the Lawful Neutral route. They need to insist requests are sent to the main support address. I’m assuming that’s tied directly to the ticketing system.

When I was being Lawful slightly-better-than-neutral, I’d create the ticket and then put a paragraph in the reply telling them to please not e-mail me directly in future, because one day I might be unavailable and their e-mail could go unseen for hours or even days.

Repeat offenders would eventually do it at a time when things were busy too, so I’d be concentrating on the tickets and not things to my personal address, so that slight delay often helped it sink in.

There are probably pre-written awk scripts out there that already do what you want, not that I know where they’d be.

That said, you might be better off using one of the bigger but still fairly commonly installed languages. There’s bound to be things on PyPI (for Python) or CPAN (for Perl) that could be bolted together for example.

If you’re really lucky there might even be something that covers your whole use-case, but I haven’t checked.

Better than a 200 JSON reply containing the 4xx. “Aay it worked!” “oh.”

Duplication of resources mainly. Bloat upon bloat. Worse, a Flatpak can ignore things that it probably should use on the system, and I’m not sure that’s a good thing.

Don’t get me wrong, there are supposed “bare metal” installs that duplicate all sorts of things too, and I don’t like it when that happens either. Steam, for example, keeps at least one extra copy of itself as well as a bunch of other things.

And there’s that Flatpaks an entirely different ecosystem that require their own set of updates.

I get it. I understand there are benefits. Doesn’t mean I like it.

Listen, I don’t even like Flatpaks, but at least they’re multi-platform and non-proprietary.

But the original poster is probably of the opinion that “pro-consumer” means something that “just works”, and if it’s a walled garden, so what?

“Why is there barbed wire at the top of that wall?” “Don’t worry about it.”