Yeah this was my initial reaction way back when I first heard of Rust as well (sometime around 2015 or so I think). TBF it’s definitely not on the same level as e.g. Haskell. But it’s generally I would say less verbose than go (or at least has verboseness where it makes sense compared to go IMHO).

A good article about this: https://matklad.github.io/2023/01/26/rusts-ugly-syntax.html

The generic system is also (way) less powerful compared to Rusts (The trait type system/type-classes is really a nice Haskell-inspired thing, that I don’t want to miss anymore). Also the lack of sum types and proper pattern matching makes go more verbose IMHO.

That’s actually where the title is coming from…

I guess I have to start calling function invocation with generic parameters, fancy names (like “dependency injection” ^^)

… until you’ve heard of Rust :)

(I think Go takes all mediocre language features together and makes an even more mediocre language TBH, take error handling for example, or generic programming (which I agree should be used sparingly, but is super useful if you need it))

Thanks for the write up, but as I said, I know and I’ve read all about that already. I still cannot see, why a simple function argument and an interface isn’t enough (you can probably already call that “dependency injection” if you want to get fancy)

I guess I have just divorced with OOP and the “necessary” “design patterns”…

Things are more simple and less boilerplaty now for me :).

I couldn’t believe it, tried it out, what the actual heck? I mean I get all these weird string vs number comparison but sorting actual numbers and this comes out? What kind of drugs were the designers of javascript (or at least this function) on… Who thought it was a good idea to sort numbers lexicographically??

I still haven’t really understood the use (and use case) of “dependency injection” (and it feels to me I read now everything about dependency injection I could find), to me it seems to be yet another ProblemFactory.

Realizing that workers do not get compensated based on merit.

Yeah I’m also much happier writing quality open source code, I think I’m learning way more, have more fun coding and everything feels more “arty” (in terms of code quality/innovation) compared to what I’m doing in my day-to-day job, where the priority always seems to be to minimize costs, instead of promoting “advancing the state of the art” in whatever area that is (which often obviously takes quite a bit more time, but in the long run would just be better in most cases). (not even starting that a quality open source library helps probably way more people than the one “quality” library down the stack in the corporate app)