FizzyOrange

Pretty huge. Going to have to give this another try. I wonder if this will become as successful as Blender.

Also they need to cut the Apple-style quips for every item ("It's written in bold", "Dock your heart out" etc.). It even says "teamwork makes the dream work" at the end. 100% cringe.

Ah that's way more progress than I thought! Last I heard they were still in "you're wrong for wanting this" territory.

How are those namespaces getting on?

Using a function is strictly worse than figuring out the formatting at compile time (something Zig also does).

The derives are just shortcuts. You can write everything out long-hand like you would in C++ or Python too if you really want.

Honestly both of these complaints are essentially "why does Rust use macros to make writing code better/easier?".

Honestly this looks like it sits in the useless middle ground between "proper CI that has all the features you expect" and "just write a Python/Deno script or whatever". I can't see what you gain.

Also you say "no painful YAML pipelines" but it uses YAML??

TCL & CMake are fully stringly typed. Both pretty terrible languages (though TCL can at least claim to be a clever hack that was taken far too seriously).

It is INT_MIN. Seems like a much more sensible value than 0 IMO.

Try interacting with anything that uses u64 and you'll be a lot less happy!

Anyway JavaScript does have BigInt so technically you are choosing.

that insanity is how C and Intel handle NaN conversions.

It's not actually quite as bad as the article says. While it's UB for C, and it can return garbage. The actual x86 conversion instruction will never return garbage. Unfortunately the value it returns is 0x8000... whereas JS apparently wants 0. And it sets a floating point exception flag, so you still need extra instructions to handle it. Probably not many though.

Also in practice on a modern JS engine it won't actually need to do this operation very often anyway.

Yeah. I think the smallest number of number types you can reasonably have is two - f64 and arbitrary precision integers types. One of the few good decisions Python made.

That's not a network effect.

Maybe slightly, but it's still way on the helping side.

They're clearly not going to be able to afford $100m/year in free CI.