barsoap

Ha! If only. They at most had WAP browsers and noone was using them because you paid like five bucks per transferred byte.

I think most of it is just confusion inherent in the term "antisemitism", which TBH is a bad term because it singles out a single Semitic people among many as the oppressed ones. That false focus then in turn causes a knee-jerk pendulum swing towards another extreme.

And who's to blame? Again, Germans: The term was introduced to replace "Judenhass" (jew hatred) with something "more scientific sounding", as recently as 1879. Damn that's a lot of citations there. Maybe we should switch to "Jewphobia" or something.

It could only fit 10 messages before it’d run out of space, and once full no messages would be received at all.

You often hear programmers cite zero, one, infinity but fact of the matter is... while most if not all of your code should be capable of that, be blissfully ignorant about any imposed limit because it's going to work whatever you set it to, the application often still should have a limit:

Even if you're not as ludicrously storage-constrained as those old Nokia bricks the data structure you're storing it in is going to have some kind of assumptions about up to what number of elements it's going to be efficient, so in e.g. game programming you write your code, document your assumption in the form of an error or warning thrown if that limit is exceeded, and when the level designers break it you have a look together at the thing and decide whether the limit needs increasing, or the level designers should reign in their use of whatever thingummy is breaking the limit.

Not to mention that just storing an index for an arbitrarily large data structure can take up arbitrary amounts of RAM. Do you really expect me to use variable-sized numbers just so that you can have more than 2^64^ (~1.84×10^19^) messages. Or columns in your spreadsheet, or whatnot.

If you're in a country where GSM is native it's quite likely that 2G is still available. 3G probably got shut down in the meantime but 2G doesn't need much spectrum and is kept as a baseline compatibility protocol, possibly even mandated by law (because emergency services). It's also perfectly sufficient for voice calls. Internet is... tolerable if all you're doing is browsing wikipedia and doing email. It's easily twice as fast as a 56k modem what are you complaining about.

I presume you regard what you just did to be "holding a conservation"?

Giving users access to PID1 running binaries, giving users access to the kernel running binaries as root, I don't see much difference. SUID was notorious in the past for being leaky, it only ended when distros got serious about fencing use of it in, giving it only to programs actually needing it, making sure that they drop privilege properly, etc.

If anything I'm in the PID1 camp because it's more microkernely. But in any case broader userspace shouldn't really care about the mechanism, only have an API to do it and that API being a bit in the file permissions is soooo 1960s.

Terminal multiplexers are terminal emulators.

L4. HURD never panned out, and L4 is where the microkernel research settled: Memory protection, scheduling, IPC in the kernel the rest outside and there's also important insights as to the APIs to do that with. In particular the IPC mechanism is opaque, the kernel doesn't actually read the messages which was the main innovation over Mach.

Literally billions of devices run OKL4, seL4 systems are also in mass production. Think broadband processors, automotive, that kind of stuff.

The kernel being watertight doesn't mean that your system is, though, you generally don't need kernel privileges to exfiltrate any data or generally mess around, root suffices.

If you want to see this happening -- I guess port AMDGPU to an L4?

It feels like the car has finally had as much love poured into it as they do their 911s. People should watch Engineering Explained’s technical overview of it, it’s staggering how much they’ve improved it.

This one?

But Porsche is somewhat niche anyway, they’re not enough to make the overall German car market look better.

I wouldn't mind the dominant VAG-internal top-down trickle moving from Audi->VW to Porsche->VW.

Also for the record Porsches are about as common in Germany as Teslas. More common than Mazda or Mitsubishi. Granted, about 50% of those are Cayennes and Macans so that Bildungsbürger mums can drive Anne-Luisa to the farmer's market.

Look at how long people thought Skoda was a crappy brand for!

Because it was, until the Czech moved from "VW but with less fuss, a proper Slav doesn't need no fancy stuff but a workhorse" to "Eh the Wolfsburg guys are getting too crappy let's get Bohemian". It's all VAG in the end but the brands do have their pride and independence.

Eh, I doubt that. Bin packing is a very well-researched problem. It's one of those nasty NP ones but we already have very good algorithms giving very good approximations in very short amounts of time the chance that throwing machine learning at the problem helps is not zero, but close to it. What that kind of approach certainly won't get you is guarantees, those approximation algorithms can be configured to spit out solutions that are at most 1% or whatever you want worse than the optimal solution.

I doubt this actually has anything to do with Amazon's logistics operations it's just their marketing team wanting to hype up Amazon for AI.

Operating in environments made for humans, as well as alongside humans.

Say you have a remote hydroelectric dam that needs inspecting. You might need to walk stairs, climb ladders, open doors. We're neither going to re-build all the dams we already built, nor build new ones to be wheelchair-accessible.

Eight is still the default tab width and will be as long as VT100 continues to be a thing, i.e. forever. Haskell could've chosen another static value but that would have caused even more trouble.

With Haskell's syntax you really want to align at single-space resolution, not necessarily just on the left but also further to the right, within the lines. The gold standard is pretty much lhs2tex "poly" style (section 8, page 19), and not just because it allows lhs2tex to spit out beautiful code, it's also highly readable in ASCII form. In that style 2+ spaces mean "align this with the 2+ space stuff above and below".

So there's no way around spaces and as tabs+spaces are a bad idea tabs get the boot. That argument is specific to Haskell but in general I'd argue that tabs are more trouble than they're worth -- if you have trouble editing space-only indentation, get a proper editor. If I want my Rust indented by a different amount I can just tell rustfmt to change everything, no biggie.