would not be considered bugs but maybe change requests.

That's just playing with semantics. They are clearly bugs. They are literally called "defect reports".

Without a spec how would you argue that a system/product is safe?

1. Lots of testing, including randomised testing and ideally formal verification.
2. Comprehensive test coverage - both code coverage (lines, branches) and functional coverage (hand written properties).
3. Functional safety features (ECC, redundancy, error reporting & recovery, etc.)
4. Engineering practices known to reduce the chance of bugs (strong static types, version control, CI & nightly tests, rigorous engineering processes - requirement tracking and so on, and yes ideally well written specifications for all the tools you are using).

There are many aspects to safety and it's definitely a good idea to have a spec for a language, but it doesn't automatically mean safety is impossible without it.

Software in itself cannot be safe or unsafe because without hardware it cannot do anything.

The nice thing about abstraction is that you can talk about software without considering the hardware, more or less. If one says "this software is safe", it means it's safe assuming it's running on working hardware.

It doesn't always hold up - sometimes the abstraction leaks, e.g. for things like spectre and rowhammer. And there are sometimes performance concerns. But it's pretty good.

PDF writing isn't too bad IMO, since you don't need to understand the whole spec. I've written a PDF writer for maps from scratch and it was fairly easy and not too much code.

PDF reading though... Yeah I'm happy to leave that to people with more time and use their libraries.

A modern format would be nice, but I don't think it would be anywhere near nice enough to give up how universal PDF is.

Interop between Rust and C++ is pretty bad actually - I can understand wanting to avoid that.

However I still agree. I can't see opt-in mechanisms like this moving the needle.

Kind of worthless video. Just speculates about how it works. They don't ever even show the app working!

These glasses aren't even AR so the idea that they can overlay details as shown in the mockups is impossible.

Isn't Elixer dynamically typed?

Yeah but this one is actually good. So hopefully it will displace all the others.

The biggest problems with gRPC are:

1. Very complicated. Way more complexity than you want in most cases.
2. Depends on HTTP 2. I've seen people who weren't even doing web stuff reach for gRPC, and now boom you have a web server in your stack for now reason. Compare to Thrift which properly separates out encodings, transports, etc.
3. Doesn't work from the web. There are actually two modifications to gRPC to make it work on the web which means you have three different incompatible versions of gRPC with different feature sets. IIRC some of them require setting up complex proxies, some don't support streaming calls, ugh. Total mess.

Plain HTTP can be type safe. Just publish JSON schema or Typespec files or even use Protobuf.

Make a post on StackOverflow claiming that no such project exists.

Haha, seriously though, ChatGPT is a solid bet. Lots of Googling. Maybe try https://grep.app/ if you have some very domain specific words to try.

I'm not sure hardware-based full disk encryption counts as a "highly specialized requirement". It's enabled by default on Android, iOS, Mac and even Windows usually. It's a basic requirement for businesses.

OMG they finally noticed how bad the REPL is. It's it going to let you paste indented code now?

It was shit and GitHub is good. It's not a mystery. It's still shit compared to GitHub, you can go and look now.

There was also an incident where they started adding malware to downloads... But really it was already dead by that point.

You should use python3 anyway not python. The latter is sometimes Python 3, sometimes Python 2 and sometimes doesn't exist. python3 works reliably, assuming you have it installed.

(And assuming you aren't using the official Windows Python installer, but that doesn't seem like the case here!)