Thanks, I’ve save your comment. I haven’t heard of any of these.

It also has real type safety and thread safety.

Do tell.

Here’s some of my personal complaints. I don’t in general know how to fix them.

1. proc_macros need their own crate

2. generics cause problems. Many useful macros can’t handle them. Try using a generic that’s a complex async function, then pass a closure to it.

3. There’s this kind of weird mismatch where sometimes you want an enum wrapping various types, and in others generics. I find my data flows switching back and forth.

4. async in rust is actually really good, but go does it better. I don’t think rust could match go without becoming a different language.

5. Traits are just a big mess. Trait implementations with generics have to be mutually exclusive, but there aren’t any good tools to make them so. The orphaned trait rule is necessary to keep the language sane but is incredibly restricting. Just today I find certain a attribute macros for impls that doesn’t work on trait impls. I guess I have to write wrappers for every trait method.

6. The “new type” pattern. Ugh. Just make something like a type alias that creates a distinct type. This one’s probably easy to fix.

7. Cargo is truly great, but it’s a mystery to me right now how I’m going to get it to work with certain packaging systems.

To me, Rust is a bunch of great pieces that don’t fit together well.

Rust. It’s a qualitative improvement over the old ways.

The future won’t belong to Rust itself, but one of its descendants. Rust is too clunky to be the ultimate expression of its best ideas.

Rust crates have the second and third problems.

Rust at least has type annotation.

The type has private fields. There’s no constructor. There’s no implementation of the From trait except on itself. You can’t find a function anywhere that returns the type.

They don’t think you have disposable income. They don’t care about you if you don’t.

It’s just easier to get old windows games running on Linux.

There’s a point where you can’t separate reading comprehension from transmission of thought.

Maybe AI will boost open source development more than commercial development since open source devs don’t have the privacy concerns.

but why would you want to?

I visited a company that outsourced its IT to India. We were delayed 24 hours because the guy who could whitelist our computer on their network was asleep. It was the middle of the night where he lived.

They finally got Sopwith.

Me: <starts a heredoc>

jetbrains: This heredoc goes on FOREVER!

Me: I’m going to close it…

jetbrains: <dies>

If you work at the same place long enough, you’re forced to remember over and over again.

The black market is only incredibly profitable if it’s selling at a high price

What’s the meaning of a fractional “Degree of Kevin Bacon”?

Anthropogenic Global Mourning

Good article, but I’d guess the reality is more like 25-50x as much work as non-technical people assume, and a good interface takes about 5x the work of everything else.

They don’t merely underestimate the non-interface work, they greatly underestimate the interface work as well.

This is exactly the kind of inane rule that feels good, doesn’t do any good, but needlessly complicates a system that should be simple, and only will work well for the poor if it’s simple.