Difficult pronunciation and it also sounds like a lame “cool” name that a super nerd would think of.

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.

you can say that without a spec as well but what does “wrong” mean then? It just means you personally disagree with its behavior.

Nope. Specs can have bugs. Here are the bugs in the C++ spec for example:

https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_toc.html

As I said, specifications are useful and desirable, but the SIL’s dogmatic “no spec = unsafe” is clearly not based in reality.

It’s not because we have tested this program extensively on every C++ compiler, but because the language rules of C++ say so.

Debatable. Saying things in a prose specification doesn’t magically make them happen. Tests and reference models can though.

I also don’t really agree with the SIL requirements that languages need to have rigorous specifications to be safe. Clearly it’s better if they do, but would your rather fly on a rocket controlled by C code or Rust code?

IMO a specification would be really nice to have, but it main purpose is to tick a certification checkbox, which is why the only one that exists was written specifically for that purpose.

Dunno why you’re being downvoted. It’s very obviously deliberately chosen to make 12 year olds giggle.

Krita is quite far ahead of GIMP at this point. I’m not a pro Photoshop user but if you are and you’re looking at alternatives, that’s the place to look.

I think there are some crates that wrap the unsafe code for you, e.g. https://github.com/rodrimati1992/abi_stable_crates/ (I haven’t ever tried it).

He is. By using statically linked binaries.

Technically this is conflating two things: bundling dependencies and static/dynamic linking. But since you have to bundle your dependencies to use static linking, and there’s little point dynamic linking if you bundle your dependencies… most of the time they are synonymous.

Exceptions are things like plugins, but that’s pretty rare.

I don’t know why you’re being downvoted. It literally starts with the word OPINION in bold red caps.

asking the maintainers to lock down APIs which the C devs purposefully leave malleable, in part, to avoid binary blob drivers being feasible.

No, they were asking them to define the semantics of the filesystem APIs. Those semantics are not encoded in the C API but the Rust devs wanted to encode them in the Rust API to avoid making mistakes.

The C devs didn’t want to, not because of concerns about binary drivers, but because the semantics are already broken. Apparently different filesystem drivers assume different semantics for the same functions and it’s a whole mess. They don’t want to face up to this and certainly don’t want anyone pointing it out, so clearly it must be the Rust devs’ fault for wanting APIs to have consistent semantics.

The rest of your comment is nonsense.

Any from reputable manufacturers?

Even that’s ok. I couldn’t find anything at all when I looked about a year ago. Only one model that the Thread people were still recommending despite it being discontinued.

I had another look and still couldn’t find anything vendor neutral and cheap. Can you post some links?

Freeing home energy gear from vendor lock-in. Matter 1.4 adds some big, expensive gear to its list of device types and control powers, and not a moment too soon. Solar inverters and arrays, battery storage systems, heat pumps, and water heaters join the list.

Yeah I seriously doubt solar inverter providers will sign up to this. Here’s what QCells said when I asked them about an API:

I’m sure it is possible and we’re in discussions with some providers over opening up to their requirements, but it’s not something we’d offer to individuals unfortunately.

They view control of their “virtual power plants” as a commercial asset and they don’t want to give it away for free.

Don’t buy a QCells solar inverter btw. I should have done more research! I believe GivEnergy are less stuck in the 80s but don’t quote me on that.

Ugh, I was working on a DIY smart lock. “I’ll use Matter!” I naively thought.

Ok you need a border router for Thread support. No problem, I’ll buy one. Should be cheap right since an ESP32 can handle it. Nope! You pretty much can’t buy a standalone border router. All the articles are “don’t worry, you might have one already if you have a Nest Hub or a Home Hub or…”. Well I don’t have one.

Pretty lame. I guarantee if they make a vendor neutral border router dongle you can just plug into your router’s ethernet port and sell it at cost price (like £5) they’ll see triple the uptake.

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.

Eh, it practice it works extremely well. I can’t remember a single instance where a PDF document rendered incorrectly.

The format is very old so it’s not surprising it has picked up a few WTFs. I’m happy to keep those hidden below the abstraction.

Totally depends what you end up working on as a programmer. If it’s web apps, you’ll be totally fine. All you need is basic arithmetic. Writing a game engine? You’ll need to know some basic to moderate matrix maths…

If you’re doing formal verification using unbounded model checking… good fucking luck.

On average I would say most programming tasks need very little maths. If you can add and multiply you’ll be fine. Definitely sounds like you’ll be ok.

Nice work. Aren’t wasm proc macros already prototyped in Watt though?

Why do you say it needs more time in the oven? I’ve had zero issues with it as a drop-in replacement for Pip in a large commercial project, which is an extremely impressive achievement. (And it was 10x faster.)

I tried Poetry once and it failed to resolve dependencies on the first thing I tried it on. If anything Poetry needs more time in the oven. It also wasn’t 10x faster.

Is there any reason to use this now that Krita exists, sane name and all?