I AM UNDOUBTEDLY FIZZED8%
kiwifarms.net
- Joined
- Jul 14, 2025
Jody plans to fight back against the big tech pushed enforcement of Rust with his new project named "Jofito".
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Good. Fuck Rust and fuck any project using it.Jody plans to fight back against the big tech pushed enforcement of Rust with his new project named "Jofito".
Good. Fuck Rust and fuck any project using it.
Many of the new rust rewrites are MIT-licensed. Which means they move to being proprietary at a later date without consequence.I’m not baiting - this is a genuine question. What’s the arguments against Rust besides some icky troons like it?
Many of the new rust rewrites are MIT-licensed. Which means they move to being proprietary at a later date without consequence.
Right, it isn't a rust-specific complaint. But low-level languages don't have any of the same safety features, which is the purported reason the rewrites are happening to begin with. So if it weren't for the memory safety itself, the rewrites would not be happening.Isn’t that something that could be addressed regardless of what language something is being written in?
Basically it's a canary.I’m not baiting - this is a genuine question. What’s the arguments against Rust besides some icky troons like it?
I haven't used it in some time, but I like it. How is digiKam for grouping photos based on image recognition? I hate to say it, as I use very little proprietary software, but I continue to use Google's discontinued Picasa program for Linux (not a true port though, they used WINE) for finding and grouping photos based on its skillful image recognition scanning. I'd gladly switch to something that is FOSS.
I notice you use HexChat. Have they found a new maintainer?
It takes a lot of RAM to compile Rust projects. That’s about it.I’m not baiting - this is a genuine question. What’s the arguments against Rust besides some icky troons like it?
Spinnan cubez!
from my experience, it causes splintering of codebases and higher resource usage vs the same c/c++ code, plus staticly linking everything doesn't let you take advantage of only needing one copy of a library in memory. Rust does have potential to be a good choice of programming language, but it comes with even more baggage than possibly c or c++.I’m not baiting - this is a genuine question. What’s the arguments against Rust besides some icky troons like it?
Had the same thought earlier today about MIT and adjacent cuck licenses, insofar that I don't think its really possible for them to grow into a popular proprietary product simply by virtue of their two main developer bases (sans employees): trannies and soy devs. Both groups develop for reasons of ego and ass pats. Turning something big and MIT, for instance Wayland into the Red Hat Proprietary Display Server or whatever would instantly kill off those two developer bases and likely estrange many more. With the advent of infinity jeets and Actually Indians, I can see a future where it happens, but not one that's very likely. I give it a 90% vs 10% chance of happening, at least in the way I'm envisioning it.Many of the new rust rewrites are MIT-licensed. Which means they move to being proprietary at a later date without consequence.
It wasn't that long ago that 32MB was considered insanely OP. Okay, looked it up, the Voodoo 4 was 2000.Remember back when gaming systems had 4GB, and 8 was considered greedy, or opulent?
god i hope not, please use a modern init that at the minimum can handle dynamic systems and at the best has daemon supervisionAt least this will push people to the SysV init distros.
More specifically, some retard decided to completely rewrite the library that GNOME apps use for doing HTTP/HTTPS, libsoup, and did it in an incompatible way. The excuse was that Google's pet 'HTTP 2.0' project was not supported... so they just broke everything for libsoup 3 rather than just adding HTTP 2.0 to libsoup 2. Then, the Gnome retards mandated that the existing, secure, working libsoup 2 must be abandoned.GNOME 50 killed Google Drive integration because nobody wanted to maintain it
Have you tried running service software that doesn't crash several times a minute?god i hope not, please use a modern init that at the minimum can handle dynamic systems and at the best has daemon supervision
defending sysvinit as the optimal init over runit openrc s6 or dinit is not something i expected anyone to doHave you tried running service software that doesn't crash several times a minute?
It's simple and it's traditional and I know how to use it and I don't want to learn literally anything else. I just use sleep mode or hibernation if I need to save power, so I don't worry about saving one or two seconds on startup.defending sysvinit as the optimal init over runit openrc s6 or dinit is not something i expected anyone to do
now im curious as to why you prefer sysvinit over literally anything else
Or just a cron job.I could always set up supervisor to manqge those broken ass daemons and restart them when they crash out.