Nope!

Those companies and firms back Rust because it’s memory safe without a garbage collector, and great for general purpose programming or systems programming. That’s super important for everyone, but especially large companies working on high performance or mission critical software.

Zig is not memory safe so it’s a non-starter for these things, and has not proven itself in the industry anywhere near what Rust has.

This has nothing to do with Rust being “corporate” or anything wrong with Rust.

There’s almost zero reason to choose C for any greenfield project. C / C++ have been plagued with extremely serious problems throughout history because they are not memory safe. The world needs to move on from memory unsafe languages whenever it can.

Choosing C for something like this would be idiotic.

You can disable all AI stuff in Zed with a single disable_ai: true setting. Still an awesome editor without any of the AI.

We really need a VaultWarden service run by a non-profit.

They said VaultWarden, not BitWarden. This shouldn’t affect them.

That amount of money is one developer full time maybe

$564,000 / year??? I’d think definitely two, maybe three.

https://fprijate.github.io/tlborm/mbe-macro-rules.html#%3A~%3Atext=macro_rules!+With%2Cfollowing+form%3A

1. Macro syntax technically isn’t even Rust
2. This is definitely not average Rust code.

Hard disagree. Super beautiful.

Thunderbird is going hard on Rust all of a sudden. Recently they started using it in Thunderbird and now they’re starting a whole service in Stalwart (written in Rust).

Super awesome.

Yep, we disagree. The world and technology especially is an extremely complicated place. IMO any complex system that is built upon “humans should just know all this complexity and keep it in mind all the time” is fundamentally broken.

I think you’re saying the same thing as what I am. If it’s more complex than what you may think, the language should guard against it. If not, it should make it simple.

Rust, for example, is the only mainstream language where it isn’t possible to read from a file handle after it’s been closed. Doing so is a compilation failure. This is just a general invariant of “how to use files”.

But you also don’t need to think about allocating or deallocating memory in Rust. It does that fke you automatically, even though it’s not GC.

JS can also be complicated when it tries to hide realities about the world. E.g. is a const array or object immutable? No, the pointer is. But pointers don’t exist! /s

I mean, this is correct in many cases, unironically.

It should be one of the core purposes of a programming language to help humans to write the code they intend. If a language doesnt do that then it’s bad.

Just like Google

I use Bitwarden for passwords and notes

Isn’t that assuming you have access to doing arbitrary SQL queries on the database? Then you’d by definition have access to records you shouldn’t.

Just curious, but if SSNs were not recycled after death, would there be any reason not to use them as a primary key?

Take a look at Rust. It’s what I’d call an exceptionally well defined language.

Posteo + Addy.io + Thunderbird