

Prodigy has holoemitters on every deck and is able to reconfigure the bridge using them. It is possible but they just need a reason.
Prodigy has holoemitters on every deck and is able to reconfigure the bridge using them. It is possible but they just need a reason.
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.
We have like three entirely reasonable shows all setup that they keep not even touching. All of them episodic, all of them able to both speak to new generations and old.
Upper Decks: Live action show with the characters from Lower Decks. Primary focus is the main characters coming to terms with the fact that they are good enough to be senior members of a crew. Continue the idea that they are the little ship that could and their missions focus around support rather than flagship or the biggest of the bads.
Prodigy 2.0: Again live action, with Ella Purnell as a captain who is super in demand and capable and would be fantastic in the role. Focus here is again episodic, when the rest of the Federation has abandoned exploration due to all the BS at the start of Picard, they are the only crew left with the charter to seek out new life and new civilizations. You have an incredibly young but capable cast and easily could bring in some heavy hitters to support them.
Legacy: This idea has floated around a ton since Picard S3, honestly its the least developed of the ideas and I’d rather see a way to roll it into one of the much better and more fleshed out ideas above. I feel like the final scene in Picard was an afterthought while both Lower Decks and Progidy it was a true capstone.
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.
The new 20 episode season is a 10 episode season with 5 webisodes and a cheaper side project like a cartoon or anthology.
Honestly this is better to me because it enables the good plots of the smaller episodes to get all the focus without forcing some awful secondary plot to fill run time.
You haven’t played 1999 I take it?
I see this a lot which is wild to me because I feel like S4 felt like it finally was real Star Trek but just rushed and some of the damage to some characters couldn’t be fixed. All the major plot points that make Enterprise relevant to Star Trek happen in S4.
I’m curious where you put Discovery? That is the one I struggle the most with. My primary issue there is that for me I have to actually like and want to be invested in a character but as far as I’m concerned 10 episodes in to Discovery if the ship blew up all hands lost the Federation I can’t think of anyone I’d feel sad for. Enterprise though has Trip and Phlox who are S tier, a few fantastic guest stars, and no character that is bottom bin material to me no matter how much fanfic quality writing they tried to force on T’Pol.
How is different from Crazy Frog or Billy Bass? Dumb memes turning into toys or dumb meme toys have been around for forever.
For the US the pretty well known policy bangers are The New Deal and The Interstate Highway System both which are not just socialism but Federal level socialism.
All state run armed forces are by definition socialist in nature. Mercenary armed forces have been used many times to great effect but the backbone of most armed conflicts are the most socialist structure you could create.
Every large modern religion (abrahamic, hindu, buddhist) is socialist in nature and got to the level they are now due to socialist policy.
Why is your hobby more important than their hobby?