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.
Zangoose
joined 2 years ago
Me during my exams this week
An unprompted steins;gate reference in the wild? Amazing
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
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.
I don't have any Citra successors installed yet because I still have my modded 3ds (I was only ever using it for specific game mods that don't work on native consoles).
That being said, I doubt It's still pretty early and developers have to get familiarized with a complex multi-thousand-line codebase they've never worked on before, so actual progress is going to be minimal.
It may not have been dark out but it was still pretty cool seeing shadows get messed up and seeing the sun get covered through eclipse glasses.
Definitely hoping to travel to one of the total eclipses in the later 20s/30s tho
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 don't actually think eclipse is completely terrible (just saw the opportunity for a meme). My main problem with it is that unlike intelliJ, the UI buttons don't scale with the font size, making it pretty unusable on my HiDPI laptop.
For now I'll just stick with IntelliJ/idea IDEs (I have access to an education license for ultimate) and then if/when Idea ruins it I'll probably just try to integrate my Java workflow into either VS Code or an nvim setup
There's also lemonade, which is prioritizing android compatibility but also looking to get desktop working at some point.
Lime3ds seemed a bit off-putting to me since the owner of the repo didn't actually have any experience with software/emulation development (I think they were a Linux/FOSS YouTuber), but idk how that has changed/if there are other people maintaining it now
You've fallen into my trap card, I really just wanted everyone else's eclipse photos here
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.