Don't get me wrong comments != documentation (e.g. doc-comments above function/method).

I probably was a bit unprecise, as others here summed up well, it's the why that should be commented.

Until the competition isn't as shitty and doubles the salary ¯\_(ツ)_/¯

but effectively it's bash, I think /bin/sh is a symlink to bash on every system I know of...

Edit: I feel corrected, thanks for the information, all the systems I used, had a symlink to bash. Also it was not intended to recommend using bash functionality when having a shebang !#/bin/sh. As someone other pointed out, recommendation would be #!/usr/bin/env bash, or !#/bin/sh if you know that you're not using bash specific functionality.

At this point, I think it's almost mainstream, and it's still growing fast (and it's getting better, rust-analyzer is really awesome these days, I was there at the beginning, no comparison to today...))

I may be biased, but I think it'll be the next big main language probably leaving other very popular ones behind it in the coming decade (Entry barrier and ease of use got much better over the last couple years, and the future sounds exciting with stuff like this)

despite what Rust cultists will undoubtedly soon come to tell me

And here I am :)

There's a lot of reasons to go with Rust (and least of all performance), especially as web-backend. Top-notch libraries/ecosystem (I work extensively with all kinds of programming languages and most others suck in one way or the other). At this point I dare to say that it has the best ecosystem in this regards. Also a static type-system only being exceeded by Haskell (when talking about general purpose languages, that are actually in use), which makes projects maintainable by a lot of people, especially relevant for an open source project. There's a reason why a lot of high quality projects are either rewriting or starting in Rust or are thinking to switch to... Etc. don't want to throw more Rust evangalism at you, since there's a lot to just google and learn...

Anyway, there were a few changes lately that made federated lemmy better (with the last release especially), the initial bugs I accept. But I agree, they aren't veterans from the valley with multiple years of experience, just a bunch of idealists that had an idea and were persistent enough for years to implement it, I certainly have respect for that. What I don't like, is that they are moderating a little bit too much, not being mostly community focused (among others, to avoid forks). But bringing a federated link aggregator like lemmy to the place where it currently is, at least takes quite a bit of time... So a fork (if really necessary) sounds like the most likely way forward...

I guess you have to almost thank John Riccitiello for that, haha

I mean yeah, dynamic libraries are great if used correctly (via something like Nix), but the unfortunate truth is, that they are not used correctly most of the time (the majority of the Unix and Windows landscape is just a mess with dynamic libraries).

With modern systems programming (Rust) the disadvantages of static compilation slowly fade away though via e.g. incremental compilation.

That said dynamic libraries are still a lot faster to link and can e.g. be hot-swapped.

Calckey/Firefish

Much more beautiful than mastodon IMHO

Thanks for the info about the other projects.

Every language is fast, as long as it can be somehow (at least) jit compiled, and you're not allocating much.

Haha yeah, I really avoid "stepping" up career wise, I rather like to code (and guide the "managers" (and other team members) in technical "questions").

Wow I pretty much disagree with everything you said haha. E.g. packaging/venv in python is absolute hell compared to something like cargo/crates in Rust. Try to manage a large project in python and you'll likely revise your answer (if you actually know all the nice alternatives out there...)

I mean I'm being honest I'm a little bit in love with Rust haha, so I can recommend learning that if you haven't yet, it has teached me the most of how to design nice programs/libs (in an efficient manner) and generally just feels nice to write. And a very relevant side-effect: it seems like it has a rapid growth also on the job-market. I really feel that growth in terms of improving library quality and tooling (rust-analyzer is I think really the best language server by now), not the least seeing ever more often something like this: https://opensource.googleblog.com/2023/06/rust-fact-vs-fiction-5-insights-from-googles-rust-journey-2022.html)