I don’t think anyone’s against the idea of it getting delayed, rather they’re making fun of the fact that Boeing has a pretty bad history with safety (and the whole “multiple whistleblowers dying” part) and every time they are about to launch some other critical problem shows up.

Personally I’d love to see Boeing have a safe, successful launch but as things are right now it looks increasingly like NASA’s contract with them won’t show expected results. I’m not going to pretend to be a safety expert so I obviously trust the people doing launch inspections over my own judgement, but I’m not exaggerating when I trust Boeing’s rocket to be safe about as much as I would trust the next OceanGate submarine.

I know I’m late to this but here’s my (probably insane?) take. We use Subject-Verb-Object in English right? So, hear me out:

dialog_create_tab(...)
dialog_open_file(...)
dialog_close_file(...)

Software optimization is mostly not a language-level problem. I’ll be dailying my 3-year-old OnePlus 9 Pro until it starts missing out on security updates, but it will probably still be “usable” long after that. Support/updates aside, my 6-year-old galaxy s9 can still run most normal apps. Hell, I got the most recent lineageOS running on a pixel 2 XL from the year before that and it straight up felt fast as long as I wasn’t playing some super intensive game or something. This isn’t an android vs. iOS problem, it’s a “developers of [insert flashy new app here] either not bothering to put effort in to optimize their code or being forced to push out a minimum viable product ASAP” problem.

Edit: fixed my hyphen use

This has to be bait

That’s fair but you’re also phrasing it like the Zelda games are objectively worse than God of War or Horizon Zero Dawn. I played and enjoyed HZD (hoping to pick up forbidden west soon as well) but imo I had a much better time with tears of the kingdom and breath of the wild.

(and people in this comments don’t seem to accept that someone actually hates a game they like lmao). If you compare God of war and horizon zero dawn to Zelda and all Nintendos games, there is just no comparison at all. Sorry, but they suck.

You are criticizing people for not accepting differences in opinion, and then immediately after you claim those opinions are objectively wrong (“just no comparison”).

Just leaving a comment with “they suck” with no extra detail doesn’t really add anything to a discussion, especially when it isn’t exactly as one-sided as you claimed. After playing HZD, I can definitely say Breath of the Wild and Tears of the Kingdom’s environment felt better (to me) even if the story was half-baked in some aspects and the graphics were worse. The physics and world engine in BotW (and even moreso in ToTK) felt way more freeing because it is way more flexible. The building system in ToTK and the way the same rules applied any elemental effect (weapons, arrows, physical items in the map, etc.) made doing literally anything feel more fun because there is almost never just one solution to a problem. It really leans into the open-world aspect in ways that HZD never did. There’s something to be said about the way I could launch BotW/TotK, raid an enemy camp, do a shrine, and blowing either link or the enemies up spectacularly with a poorly-made contraption in the span of 15 minutes, while I would always feel like I got nothing done if I spent less than an hour in HZD.

Spoken like someone who’s never played a Zelda game. That being said, probably just play it on an emulator unless you like the portability aspect

Edit: But seriously, Nintendo is one of the only publishers that hasn’t ruined their games with live service micro transactions and battle passes, and one of the only publishers that hasn’t ruined their long standing IPs yet (Pokémon excluded, but that technically isn’t owned completely by Nintendo). I don’t exactly like Nintendo as a company but I have to respect that they haven’t been cash grabbing in the same way other publishers have.

That’s partially my point. You can never be 100% safe, but there’s a lot you can do to increase your safety besides just relying on intuition (edit: because intuition is usually the weakest link, see social engineering/phishing tactics). Anti viruses (when they aren’t just bloatware) are part of that.

Your second point about not meaningfully defending against backdoors and vulnerabilities is kind of against the point. You can totally defend against backdoors by not giving apps admin privileges, limiting network access, etc. so that damage can be limited even if an exploit happens. Then, if some backdoor or exploit is discovered, it’s only as dangerous as the permissions you give that app.

Linux gets viruses too (see recent xz-utils vulnerability that almost got into production environments) and its kind of a shame that corporate antivirus software like Norton and McAfee end up ruining the reputation of antiviruses. In theory the idea of having a software that can scan for common viruses is a great way to increase security, even if it shouldn’t replace common sense. I’m not too sure if there are any good FOSS antiviruses, but if there aren’t there should be.

What makes you think so?

The devs said so. Check r/Suyu, that seems to be where a majority of the updates are being posted. I think there was a link to a pastebin post somewhere there as well.

The SDK mentioned was first party, presumably leaked but I’m not completely sure. And yes, that means it would be present in every other fork as well.

Edit: here are some of the links I’m talking about:

https://www.reddit.com/r/suyu/s/TqSWDlnsGs

https://pastebin.com/6FYdz9Sr

Edit 2: worth noting that the “founder” (as they call themself) still wants to continue on the project but I believe a majority of the devs left.

Edit 3: I found the archive link from someone on the Yuzu team showing they had access to a leaked switch SDK: https://web.archive.org/web/20210114104638/https://twitter.com/Slashiee_/status/1349557173970341890

I don’t know how much of this evidence is real but if any of it is they’re going to have a much harder time finding devs willing to contribute to Suyu, even if development does continue.

Suyu died though. Right now the only actively maintained Yuzu fork is Sudachi, which is only maintained by a single person.

Apparently there was some drama about the Yuzu devs using code which came from a switch SDK as a basis for emulator code, which kind of poisons the whole codebase.

That’s the thing though, because it’s kind of a paradox. If you had a single team working on it, then sure, it might be easier to just learn Rust. However, on an open source project, especially a volunteer driven one, that isn’t necessarylily the case. Your average enterprise dev probably isn’t even considering rust as an option yet, because it’s still in early stages in terms of tooling and support infrastructure.

I made another comment in this post, but as it is right now languages like Java and C# make up significantly more projects/job positions than rust. If you want to get more contribution from volunteer devs, it needs to be in a language that devs are comfortable with. Most people won’t want to learn a whole new programming language for a volunteer project when they’re already working a full-time job in a different language. I explained this in the other post, but that’s why I think having both projects is still beneficial. Sublinks and Lemmy can (hopefully) continue to exist at the same time and benefit from each other’s development, especially if they stay API compatible. Sublinks will have a lower barrier to entry (thus maybe a quicker development cycle with more people involved), while Lemmy will help contribute to the validation of rust as a language for production code.

Also “rust is the future” implies that’s the only programming language that is worth learning, which is simply not the case. Different languages are better at different things. There will never be a single language that’s best at everything. Even for a specific task, multiple languages are good at doing the same thing. For example, Go, Rust, C#/any .NET, and Java/any JRE can all do REST services like Lemmy pretty well. Of those, I wouldn’t even say Rust is the best choice, because its frameworks are all still pretty new.

Other languages are growing and evolving as well. Even old languages like Java and C++ have had significant improvements in their modern standards (Java records, C++ smart pointers, etc.). Hell, even COBOL got a new standard version as of 2023 (if I had to guess, this didn’t do much for it though). Just because certain languages are bad right now doesn’t mean they will stay bad forever.

I love not having downvotes federated 😎

Thanks for the explanation! I didn’t realize it was mostly a maintenance limitation, I thought maybe 32-bit instructions could be an extra attack vector on a physical CPU instruction level or something like that.

Isn’t supporting 32-bit apps on a 64-bit OS a security concern though? I thought that’s why some linux distros were disabling 32-bit repositories by default on their 64-bit versions

Sorry for being unclear, I wasn’t trying to say language doesn’t make a difference (e.g. static vs. dynamic typing would make a big difference). I also personally like the error handling of rust a lot more, even if it does take a bit getting used to when my education has mostly been in languages with Java-style exception handling.

I mostly meant that the language-level performance and features aren’t necessarily holding the codebase back in a debate between Java and Rust for a lemmy-like REST API. As long as the developers are aware of the pitfalls of Java (null, mutation, error-handling, etc.), it’s possible to have good code.

I just think that from a maintainability standpoint, a Java-style codebase is much easier for most people to read, understand, and maintain because that’s what most people are familiar with. Especially when many of the developers are volunteer contributors, that type of thing could make a big difference.

The main problem with Rust is that it’s only starting to get adoption now, it isn’t taught in most education curriculums, and it’s industry use is pretty small at the moment. It’s kind of a catch-22, because rust adoption won’t increase unless large projects like lemmy exist. But that’s also why I think having more options is also fine. Sublinks might get more developers short term because of its language, but that also doesn’t mean it’ll completely replace Lemmy. Both projects can exist at the same time, and hopefully benefit from each other’s development.

A lot of people here seem to think that Java code is awful and disgusting and no projects should ever use it. The thing about popular languages is that more code existing in a language inevitably means a lot of it ends up being bad. The same thing will likely happen to rust as it gets popular, but that isn’t exactly a problem. It’s possible to have a well-maintained Java codebase.

Debate between functionality of the actual programming languages at this point is pretty meaningless, if they have good development standards then a Java program could end up just as well maintained as rust. Any time saved by compiler enforcement of specific standards (like no using null) would be lost by the fact that the devs don’t know rust tooling. You could just have a requirement in PRs that null isn’t used. Both Java and Rust have usable frameworks for REST API development, so using one or the other comes down to familiarity.

The idea that programming languages make code suddenly good or bad is pretty silly. Different languages have different language-level guarantees which can help produce good or working code. That being said, it’s not like it’s impossible to write good Java code, just like it’s not impossible to write bad rust code. Most people seem to be conflating guaranteed functionality and safety with maintainability, stability, and readability. Rust is still a new language, so although it’s great, Java will probably be the better choice for the latter 3 qualities.

That being said, something like Kotlin would probably have been a better starting point since it can interact with Java (and works like Java in most cases) but also has some nice improvements like stricter null checking (Kotlin nulls are treated similarly to rust’s Option<T>, it’s just described as T? instead and the syntax is generally a lot more concise). There’s also the benefit of being able to write some code in Kotlin and some in Java since they are mostly cross-compatible.

I think they mentioned in another comment, but sublinks is developed in Java, so the .world team would be able to contribute more to the actual development/testing process (edit: since they aren’t familiar with rust).

I feel like squash and merge on GitHub/GitLab is nicer for that anyway though, it makes the main branch so much cleaner automatically

Pretty sure the dev mentioned they were going to release the source code as well, so it won’t really be proprietary anymore. Either way I still prefer melonDS but at least there are options

You’ll have to settle for naming your child after one of their public keys, but then your child will only be able to talk to them.