@fiore @max @snacks
I agree! The main point: it's hard to move away from — that is indeed so and it's very important when you're using it commercially, as for other disadvantages — they have their counterparts in other languages, the article even gives a few examples of those.
One other thing that strikes me: indeed, it has very opinionated defaults and your code is to be error-prone if you're writing it just by looking at others' code, which is important for junior devs…
@fiore @max @snacks
Indeed, the compiler doesn't warn you about shit… But in case with Rust you're in some cases doing things in a very inefficient way just to make the compiler SHUT THE FUCK UP — because you feel that re-writing it in an idiomatic way for Rust might make your head explode 🤯
All in all, nothing is perfect, the article is absolutely right about that.
@fiore @max @snacks
You have to learn how to write *idiomatic* Go code (at least read The Go Programming Language), then a lot of mistakes are easy to avoid — and a lot of things start making sense, those that don't — never do 😂