I mean at least the jobs that interest me often are also (full) remote, but I’m mostly interested in start-ups, they seem to be more open with it (and the job descriptions sound more interesting). I think Covid did its job there, unlike it seems for big tech?

I mean I can just take a job in the states, they pay quite a bit more there compared to Europe, and it can be even more targeted in the area of my interest (low-level stuff in Rust which pays even better than what I can find here)… Locally the jobs are pretty limited (at least those that interest me)… Everyone wants Java/C# or JS devs here (all languages I’ll try to avoid, and I suspect it has to do with maintaining old (tech-debt) code-bases which I try to avoid even more)… But I’m quite happy with my team currently and just have rant about JS everyday, but at least don’t have to maintain tech-debt (at least not something that I haven’t produced myself^^)… And I get great food for free… Hmm trade-offs.

I think it’s just to avoid explaining why, and how they harvest your data. That said, I also hate how a lot of errors of the big corpo are just like “This site has an error” no error-code, no further feedback what to do etc.

I guess ublock origin is doing wonders then, for me it’s still the same…

My fear of working full-remote. I mean I got enough friends, but still that’s significant less social time, when not being in something like a coworking space… Although other benefits are really tempting (like 2 to 3 times the salary)

I’m happy when it just takes that amount of time, because everything else is just a waste of time…

You may also want to checkout xilem

True, Fyrox often gets less love than e.g. Bevy (probably because the data-driven ECS pattern feels more idiomatic in Rust than OOP, and probably because it’s mostly a one-man-show as well)

Rust has exactly the same problems with depreciation as many Frameworks rely on experimental features which are subject to change.

Rust has actually quite a good record with depreciation and backwards-compatibilty etc. They are changing the language in non-backwards compatible way over editions, but the changes are mostly very manageable.

But to not end up being another C++ (syntax-wise it’s a disaster IMHO), a few non-backwards-compatible changes every few years are the way to go, when it’s manageable.

Learning curve is steep in the beginning, I agree (I wouldn’t argue painful though, maybe if you have to unlearn bad practices, like interior mutability though etc.).

But I think it pays off after some time. I’m now faster in Rust than in C# with similar experience, and the quality of the code is definitely higher as well (which can be credited to the strict kinda opinionated design of Rust IMO).

It composes really well, better than most (non-functional) popular languages. I think this is probably the Sell for Rust, as it additionally works remarkably well over the entire stack (kernel -> frontend) (in each abstraction level might be better/easier to use languages to be fair though).

There are of course security flaws, we’re humans after all. Unless the compiler and the language can be proven mathematically correct at least.

But as described above, in practice the security flaws are easier to isolate in Rust compared to C# IME. The current story of security flaws in Rust is quite good so far.

I’m not speaking for Rust level performance. I’m using Rust nowadays, because it’s generally doing a lot right, that other popular languages struggle with IMO.

Think about error handling. I think even Java is better here than C#. I think it’s quite a mistake, not being required to add all possible exception types that a function can throw to the function signature.

Then the next thing, I really hate about almost every popular language is implicit null. To be really safe, you have to check every (non-primitive) variable for null before using it, otherwise you have a potential NullPointerException.

Then take pattern matching, this is a baked in feature of Rust from the beginning and it does this really well (exhaustive matching etc.). There’s “basic” pattern matching in C#, but it just doesn’t really feel right in the language, and is not even close in capability compared to Rusts.

All of this (and more) makes Rust the less error-prone language, which I can say with confidence after long experience with both of these languages (both > 5 years).

I’m honestly not sure why exactly C# was chosen for most of the games, but it’s probably because it’s relatively good to embed, is relatively strong-typed, while being somewhat performant (compared to something like python or other scripting languages).

Yeah me too, but I think it’s not there yet, when you think out of a less programmer focused perspective, as most of the stuff in games is of artistic nature (which takes time to make, even with all the AI stuff) and otherwise simple game logic for most of these indie games. So something like an interactive GUI editor to “debug” is a must have for artists.

I mean why else would you want to use C# when there’s Rust 🦀 and all the awesome tooling and libraries around it…