It’s more that you can avoid many mistakes by programming defensively and having good discipline. For example, you can avoid many memory allocation if you follow RAII and use smart pointers.
Null references can be avoided by avoiding using null (and prefer using optional where it makes sense).
There’s no shortage of developers with lots of experience in writing Java backends. People know what to do and what to avoid. The pool of available contributors should be larger.
Backends in Rust is relatively uncommon.
This thread chain started with:
Meh. Java feels like a downgrade.
Sublinks using Java is not about Rust hate. They just thought it was the better choice for them.
Writing backends in Java is super common. Rust for backend is almost unheard of (yet).
Or that other language do you propose?
The good thing about Python is that it’s widely used. Easier to find people who can contribute in Python than Rust, which Lemmy is using.
Downside is that Python isn’t ideal for large scale systems. Other languages like Java is better at protecting the programmer against common pitfalls that come when building larger applications. Python is more ideal for smaller scripts.
DK64 is sometimes accused of killing the collectathon genre. While I’m not sure if the accusations are deserved, DK64 was too ambitious with the amount of collectibles and the size of levels for its own good.
It’s still a great game. I think I prefer DK64 over Tooie overall.
I played both in my childhood, and I don’t think I’ve ever returned to Tooie after I beat it first time. It’s a good game, but doesn’t have that same lasting appeal as the first game.
You touched a bit on the why: the game is too ambitious. The levels are too massive and too intertwined. Smaller isolated levels fit the collectathon format better.
I remember having lots of fun with the multiplayer though, so that’s a bonus.
If you want to continue the collectathon journey you should try out Donkey Kong 64. It’s also a game that falls under its own ambitions, but in different ways. Still a good game, but nothing beats Kazooie.
100 player survival mode could be fun. It worked for Tetris and Mario, and I can imagine something similar would work for Crazy Taxi.
As long they manage to maintain a steady player base and stay away from predatory monetary practices - which probably is just wishful thinking.
Could be like Mario 35, which was pretty fun
Thanks. I’m content with my own solitude, but I can admit the affirmation I got from this event felt nice, even though it was all stimulated.
I’m at least happy head hunters stopped spamming my LinkedIn
deleted by creator
Not too bad, but could be better.
A funny story about my not so great love life: just matched with a girl on Tinder which I managed to have engaging text discussions with and it felt quite genuine. This is rare for me, so I was happy about it.
Well, in the end it became obvious to me it was just a pig butchering romance scam when she started to talk about how she can help me invest in cryptocurrency.
I guess I’m going to be a failure in love life for a bit longer lol.
Teardown is a really solid game under the technical gimmick. It plays more like a puzzle game, but way more open ended.
Hopefully they won’t come up with some kind of a Rust/CLI, a version of Rust with GC support.
My guess to why the ads are so different:
The firms making the ads are probably completely separate from the developers. Could be just random people from fiverr making the ads. They get barely any gameplay footage, so they just come up with some random gameplay that looks fun in an ad.
I guess the game developers might be some random people from fiverr as well.
As to why it works: no idea. I guess some people just don’t care, and given how cheap these games are to make they probably just need a few people to break even.
Often I use Python for exploratory purposes. Like, I got a bunch of data, and I want to know if a particular algorithm might work or not. I implement the algorithm, but realize the results don’t look good enough. So I tweak the algorithm, maybe even do major refactoring. Or maybe I realize my visualizations or metrics don’t capture what I need to see. Or maybe I must settle for some compromise?
I iterate on this repeatedly until I find something I’m happy about (or until I give up). Sometimes I end up with something completely different from my initial idea.
TDD won’t help me much here because the end result is unknown. For each iteration of this idea process I might even need to rewrite all the tests because none of them are valid anymore.
TDD only works well if the problem is clearly specified before the first line of code has been written, which is rarely the case when I need Python for something.
Mostly number crunching and data exploration tasks. Just so I can make informed decisions about the data I got. I do this rarely enough so it hasn’t been worth for me to install all these extra third party support wheels.
As you said, the difference is in the ecosystem of libraries. This is where Java has the edge. It has a more mature ecosystem when it comes to web server backends. This includes the number of frameworks, programmers and information sources.
Unless Rust clearly solves common problems people currently have with Java backends, Java will remain the dominant alternative. I believe this is unlikely, because Rust is mainly designed to overcome common memory problems people have with low level C systems without the overhead of garbage collectors.