yeah as nice as it is what you can achieve with trait-bounds there are definitely trade-offs, being compile time and error messages, and sometimes mental complexity, understanding what the trait-bounds exactly mean... I really hope, that this area gets improvement on at least the error-messages and compile time (incremental cached type-checking via something like salsa)
Yeah absolutely I quickly get bored playing a computer game or something, but I just love coding (in Rust obviously ^^), creating new things etc.
I agree with the other comment. It's Open source after all, they could've just crawled the web otherwise.
Private repos on the other hand is a different story.
Like to see so many fellow nix(os)ers here, I think the amount/ratio of nixers here is quite a bit higher than previously on reddit.
// This enters the if branch if "myVar" == true
while otherVar == 42 {
// do something
}
literally...
Yeah I have the feeling that sign-up should probably default to be manually moderated, to avoid a bot-swarm taking over accounts (and well probably a lot of bot instances need to be blacklisted then as well).
I'm not sure how dirty the game of big social media is/will be, but if they really feel threatened, they may start something like that (might make sense to be legally secured in that case...).
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").
I can think of maybe 1 or 2 places where inheritance makes sense, and I haven't encountered these in the last 5 years... (not counting implementing interfaces of course, which definitely makes sense). In all other cases inheritance is IMHO a bad decision (why I think it should not be a thing in programming languages, because it leads someone to write bad code, as it seemed to be the right thing to do...).
Either start applying, it's not that seniors aren't in demand.
Or (additionally) what I personally have found interest in, is just diving more and more into open source. I think this actually improves my abilities (and fun/interest) most (writing and exploring open source). I kinda "feel" that in my workplace as often my opinion is asked and I have something new/innovative to offer (that I've learned from a good open source codebase), that ends up being adapted.
I would probably suggest Rust for that exact reason, you'll have to fight the language a little bit at the beginning (at least if you'll have a very "interior mutable" experience instead of a functional background), but it teaches you how to write your code in a nicely relatively uniform compositional safe style, that IMHO can be read quite well between different people (team) and I think is easier to review (as long as it's not some super magic trait-heavy/proc-macro code of course, but I think for actual applications (vs libraries) that part will be rather low)
Also I think nowadays the barrier into the language is much lower than it was a few years ago. The tooling, specifically rust-analyzer (and probably Intellij Rust too, never tried it though) and the compiler itself got really good in the meantime (I actually think Rust-analyzer is by now the best LSP for any language I know of), so that getting into Rust is likely not that hard anymore (you'll have to learn/understand a few concepts though, like heap/stack and the lifetime system, but I think that it's not that hard to learn).
Go just often feels very hacky to write with a lot of quirky things like handling errors, and a lot of missing features like pattern matching or a relatively good type system, I don't think it really promotes that nice architectures (or limits the programmer kinda).