Sorry to hear you have a terminal prognosis.

I'm not sure there are enough terminally ill but still fairly healthy people who also have the right skills and mindset though. When you think how few people manage to become astronauts... And they would want to be extremely sure that your condition is stable and you won't deteriorate during launch g-forces, in zero-g, en-route, or shortly after arriving. A lot of the work is quite physical. Even in Mars' lower gravity, those suits are heavy and bulky and stiffer than normal clothing.

Then there are the legal aspects of it. Countries that allow assisted dying only tend to do so in fairly narrow circumstances, so the legal landscape for suicide missions is, at best, unclear.

Then you end up with vague tickets you can't act on. You can't win, and I say that from bitter experience.

While AI is unreliable, I have to point out that human summaries aren't all that reliable either. I've read more than a few textbooks that were full of obvious nonsense and terrible advice.

I tried AI for a web app I made for personal use. It couldn't build a working app, but it did at least get me the keywords I needed to google to build my own. Some of the tech it suggested was outdated and deprecated, so basically about as reliable as the Reddit posts it was trained on.

Typically we don't destroy an entire firm for the misconduct of one employee, unless it's so extreme that it justifies screwing all their other clients. Imagine if your case was headed to court and your lawyer said their firm had been wiped out by another employee using AI, so you need to find another lawyer and hope the court is willing to accommodate the delay. Even if the court is, re-doing much of the process, document exchange, and so on will take a lot of time and create more expense, that you might end up being liable for if you lose.

To be fair, lawyers do use external services that in theory leak a lot of information about their cases all the time, and have done for decades. Databases of case law are the obvious example. The searches give an insight into what the lawyer is thinking, what their likely arguments will be, things they may have overlooked.

Naturally those services offer confidentiality, the same as the phone company promises not to listen to the lawyer's call to their client, unless legally compelled to.

The question is, are there any AI legal research services offering that?

They believe they are superior humans, proven by the fact that they are rich or at the forefront of the latest tech bubble. Never mind dad's emerald mine...

Even apart from costs associated with proprietary software, the other reason to avoid vendor lock-in is to avoid self-propagating backdoors in the compiler. Ken Thompson described how to make such a backdoor with C in his 1983 "Reflections on Trusting Trust" speech. David A. Wheeler described "diverse double-compiling", a defense against compiler backdoors that relies on the existence of independent implementations of a language. Stable Rust doesn't have that because it's such a moving target, with widely used programs relying on language and library features less than half a year old.

See also "Reflections on Rusting Trust" by Manish Goregaokar

They knew this and decided to maintain Perl 5 alongside Raku (formerly known as Perl 6) for what is looking to be noticeably longer than the 11-year transition from Python 2 to Python 3.

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.

People expect to be paid for commute time too, at least in the sense that they will want more money if the commute is longer. Work from home made just coming to the office at all something which people want more money for.

$6 billion could do a lot to end hunger in many parts of the world. Instead, Musk bought Twitter and turned it into a hellsite, and told people to have more kids.

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