If they have an expedition then play that mode. I really do not understand why they do not keep an Expedition or two running at all times. They add exactly the amount of depth folks find missing and normally I can run one and then I still play and have fun for another 20 hours before the game gets repetitive and I quit for a bit again.

Switch 2 to me is something I’m okay with from the perspective of, I think these consoles need to update more often. Nintendo didn’t have anything revolutionary to add this time around, but wanted to update the Switch because it had been 8 years. It’s nearly 100% backwards compatible. This is a better choice than the WiiU which basically was Wii without the fun.

I’m curious what Sony and Microsoft do because there isn’t any new improved tech for those devices that would really drive a better experience for people. Microsoft seems to be toying with the Xbox isn’t a single device it’s an experience concept. Sony made the Pro and no one cared.

Why is your hobby more important than their hobby?

Yea but if someone uses those bindings then you can’t just not support it.

By the time this code gets into a large scale production system it will be 2029. That is when the bugs will come in if someone leveraged the Rust bindings.

You can ask the big company users at that time to contribute their fixes upstream, but if they get resistance because they have relatively junior Rust devs trying to push up changes that only a handful of maintainers understand, the company will just stop upstreaming their changes.

The primary concern that a major open source project like this will have is that the major contributors will decide that interacting with it is more trouble than it is worth. That is how open source projects move to being passion projects and then die when the passion dies.

Yea and if the Rust developers don’t show up to the show? Rust is a baby and it has done so little on its own. This isn’t a neat little side project, this is code that a major vendor will want to take up and will demand be maintained. There are implications on a global scale.

It’s mostly in that linked thread. The high level of it is a guy wanted to push Rust code. The maintainer said no it would mean the API for this would be tied to Rust and that is unacceptable. It cause another big contributer to throw a fit and Linus said he can’t be everyone’s mom. They kept fighting for like 2 months apparently? Now Linus stepped in, looked at the code and said the Rust code clearly doesn’t impact the API in the way the maintainer was saying it just breaks itself if the maintainers allow changes to the API.

I kinda dislike the idea that it’s cool for people to contribute code that is so easy to break. I have a feeling after it happens a few times they are going to claim that it is being done intentionally and that the slap fights will carry on.

Linus shouldn’t have to get involved at all. Each part of the Kernel should be handled independently by the maintainers. Linus responding publicly to outside forces is fine but once he has to step in to handle public fights between individuals who are supposed to work together it is a problem.

Linux staying C focused is a valid thing to do. It is very hard to get folks to contribute to the kernel and if you cut out anyone who doesn’t know Rust, a language with at best 5% the adoption rate of C, you will run into spots where sections of the kernel are unmaintained due to no willing and qualified person covering it.

Adding Rust based functionality and support is great. Changing APIs to require maintainers to learn Rust to continue to maintain the code they are experts in is unacceptable.