Debian used to just require old school Unix stuff plus Perl, which is pretty old school really.

Then they started requiring Python for some tools.

They just keep adding more requirements which bloat the base install. This is the opposite of the right direction.

The source code is the most important documentation about the source code.

Clearly this not even even being done by an automated tool, let alone a human. An LLM which is given access to a database of actual cases could reasonably be successful at checking whether the cased cited even exist which isn't being checked now!

Using non-local AI in any way in court filings which are supposed to be confidential until filed is glaring lack of professional conduct right up front. Allowing AI hallucinations to get in to your court paperwork even once is the same. They should lose their license for one year the first time, five years the second time, and permanently the third.

Slashdot is such a shithole

Or if it's even still readable. Intel when retrieving the 486 tape-in for the Edison project had to bake the tapes in an oven to remove moisture, and then had ONE CHANCE at imaging the tape as it crumbled to dust going through the reader.

The most prolific poster on my Mastodon feed is a retrocomputing enthusiast who uses a decades-old (pre-Intel) Macintosh PowerBook G4 as their daily driver.

GCC has tended to support more historic instruction sets than LLVM. If a device's instruction set is supported by GCC and not by LLVM, it can run programs written in C, C++, Fortran, and other languages supported by GCC. It can also run programs in an interpreted language whose interpreter is implemented in a language supported by GCC, such as Python and PHP last I checked. It cannot build programs written in languages supported only by LLVM and not by GCC, such as latest stable Rust. What keeps gccrs (the Rust front end of GCC) from entering production is that the Rust language is still a rapidly moving target, with popular programs routinely requiring features added to the language or the standard library less than six months ago.

The service worker API is explicitly designed to avoid downasaurs in "offline-first" use cases. It acts as a proxy to serve the shell document, style sheet, scripts, and stale data, even without an Internet connection. That's why I asked what obstacles there are other than a downasaur.

I have not presented my ideas to Grab because I am not a user of Grab. I would imagine that most readers of Slashdot are likewise not users of Grab.

I want them to fix the JavaScript related memory leaks in Mobile so I don't have to kill it several times a day. I guess that's too much to ask since this has been going on for literally years.

I was expecting someone who has used the product to help others in this discussion understand why Grab probably chose and continues to choose to develop iOS apps instead of PWAs. The answers might have taken the form:

A. PWAs weren't capable enough 12 years ago for X, Y, and Z reasons, are now, and the engineering resources to port the native app to a web app would exceed the cost of acquiring and maintaining Macs capable of running the latest macOS
B. PWAs still aren't capable for X, Y, and Z reasons

I was thinking the same thing. It must have a whole raft of licensing fees on it. If the price keeps enough people out of the market for it then these will turn out to be some of the most valuable minifigs of all time. I wonder what it costs if you buy the same pieces (less the figures) via parts orders.

And the right decision would be for phone operating system publishers to provide functionality in the included web browser to let a website act as a progressive web application. Safari for iOS has a history of lagging behind other platforms' browsers in PWA features.[1] This is particularly evident with respect to what the browser allows websites to do in the background. For example, Apple implemented Push API seven years after Mozilla did, and it requires the user to add the website to the home screen to enable PWA features.[2] Do you want Nintendo Music to pause when you switch to another application? Or if you've chosen to let Nintendo's website notify you when something becomes available, do you want to miss the notification if Safari suddenly decides that your domain's notifications shall be silent (without vibration, without sound, and at the bottom of the list)?

[1] "Progress Delayed Is Progress Denied" by Alex Russell
[2] "Push API" on Can I use...

"Roblox is a shit hole of creeps and wannabe child rapists. My teen has been on it for years"

Awesome self own there

With two exceptions I can think of. Correct me if I'm wrong, but as I understand it:

1. For lightweight web hosting, a low-end VPS from a company like DigitalOcean is likely to be less expensive than upgrading a home office from home-class home Internet to business-class home Internet to unblock inbound ports 80 and 443.
2. SMTP is still an old boys' club, with major mailbox providers (such as Gmail and Outlook) blocking connections on port 25 from on-premise IP addresses as likely sources of spam.