Not a mint user myself, but I have helped a friend install it. The install script at the time would silently crash if it had issues with the network card name. Researching it I found that this had been reported 8 months before my friend ran into it, and a PR submitted, but was not even looked at for a month after. Sure, these are all (largely) unpaid volunteers, but if your objective is to be beginner friendly, stuff like that really shouldn’t be left sitting for so long.
It’s probably uwsm. A faulty update got pushed. Start Hyprland without uwsm or downgrade to the prior version until the fix is rolled out. Ran into that today too.
Arch, everything it does provide works extremely well, I can configure everything how I want it without having to fight a distro maintainer trying to be clever, I get new features and bugfixes whenever they go in without having to worry about a distro maintainer deciding whether it’s relevant or whether I should just live with crashes and security issues for another two years because they figured it wasn’t important or critical enough.
Luckily I wasn’t even using the UI in the first place, still, not a good sign and probably something to look into.
I was wondering the same when I came across it a few hours ago and decided to look into it, apparently it’s because it was decided to use an atomic distribution as a base and Suses is apparently not considered stable enough by them. (I can not argue the validity of these statements given either way, that’s just what I found in one of their gitlab issues . if someone wants to look at it for themselves, searching for Fedora on the issue tracker should bring it up)
Tbh, that’s pretty much what it looks like, the only “innovation “ there appears to be also glueing vmware on top.
The very same, yes.
Honestly if you want the best chance of brand new hardware working, a rolling release distro running the newest release kernel as soon as possible is pretty much your best bet.
For people who like a concept more than practicality. There’s maybe a handful use cases that this specific device fits in that isn’t covered better by existing tech, but I guarantee if that thing actually gets kickstarted and arrives severely delayed in several years, it’ll show up in a couple YouTube videos with people sort of uncertain what to use it for, and in the vast majority of cases it’ll end up in some drawers after having been used a few hours tops.
Yet more cryptotrash.
While I like the idea, it’ll be incredibly tough to overcome Microsofts lobbying, one just needs to look on the history of the LiMux project.
Was considering bcachefs at some point but after seeing this, definitely a no for the foreseeable future. I don’t like surprises in my file systems.
Benchmarks mean nothing. These aren’t the results of code written by an average programmer. Edit: and as a general note I would also like to point out the relative inconsistency of the results in terms of factor, only further reinforcing my point. I like Rust and all but we do need to admit it doesn’t magically solve all our problems.
“More performant” citation needed. Very well written Rust might be extremely fast, yes, but Rust is also a hard language to get right. Swift is far from a slow language and I would not be surprised if the average rust programmer barely if at all manages to beat out the average swift programmer in terms of speed. As for the amount of programmers interested, hard to tell, but given the sheer amount of Swift devs I’d not be surprised if there were quite a few interested ones and I am unconvinced Rust programmers are statistically more likely to be interested in Browser development.
Not particularly. The exploit requires ring 0 access, if an attacker managed to get that, you are screwed already.
Yup, Arch is by far the distro I have had the fewest amounts of technical issues with. Yes, you need to know what you are doing or be willing to read docs, but there’s no magical bullshit, maintainer capriciousness and lack of planning happening like I have unfortunately witnessed all too often while using other distros.
Another thing you could check out is Caddy, comes with a lot of stuff onboard and has an optional crowdsec module (though I should point out that I never used that module myself so I can’t make guarantees how well it works) https://caddyserver.com/
The section about stability vs “bleeding edge” gives me the strong impression that the author doesn’t really know what they’re talking about and only parroting something they heard someone else say.
Because it’s not overly popular as a desktop os, you are far more likely to see it in certain appliances and server applications etc, none of which will show up in a pagevisits based statistic.
I get to set up a system precisely how I want it to work, when an update releases for something, I get that update and I am not at the behest of a maintainer to decide for me if I need that feature or bugfix at the moment. There’s no preconfigured “opinions” on how stuff should work that differ from the defaults in most cases, which means everything usually actually just works, vs some distros where the maintainers felt they were smarter than upstream and consequently broke shit.