Rookie numbers, it's probably 15% on my screen, There's space for a lot more rainbows
philm
joined 1 year ago
"easily" solve it.
FTFY
I mean if you have a super nice working environment (team etc.), I don't see an issue with staying at the company.
But yeah as you say, if the new company is better in every single way, of course you should move.
And we're about to enter the fourth rainbow dimension in the next comment...
Until the competition isn't as shitty and doubles the salary ¯\_(ツ)_/¯
We're in the third rainbow, keep building more stripes lol
True, Python has a very big userbase and a lot of cool libraries and is nice to quickly hack something together.
Though the title of the post is
If you had to choose one programming language that you had to use for the rest of your life, what would it be?
So TMU I want to predict the future in a way that it positively affects me, and find a language that fulfills this role best (throughout the stack, so that I'm not limited). And honestly I wouldn't want to touch Python with a long stick, if the project is moderately complex (and isn't easily off-loadable to native libraries that Python builds upon) and say > 5000 LOC, the super dynamic nature of python is a curse in this regard.
Zig > Rust because actually writing safe Rust code
Start thinking more functional, I rarely have issues with the borrow-checker, or even have to write unsafe. But it obviously depends on the context, when the issue at hand really requires a lot of interior mutability or unsafe can be pain.
I'm also super fast nowadays with Rust, probably faster than with any other language (thanks to great tooling?).
Behold, Rust is blazingly fast in approaching the most popular language :)
Also, in comparison to Python you can do pretty much everything throughout the stack, which would be the reason I would go for Rust (not mentioning all the other niceties it has to offer).
Also learning Rust nowadays is much more approachable compared to say 7+ years back (ecosystem got way better)
Depends on what trait bound error messages you have had yet, I had 1000 lines long already, where it's not obvious at all what is meant (and is often a very simple fix). But I'm sure this will get better over time, there's already a bigger ongoing redesign of the type system solver, so maybe it will be integrated into stable rust soon.
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.
Plenty of space for me still (browser version on desktop)