Snake case.
- Starts with a lowercase, good for shell autocompletion
- No spaces, so no worrying about spaces in shell commands
- '_' is better than '-' because it shows the spaces between words more clearly
that_leaflet
joined 1 year ago
2
Tumbleweed – Review of the week 2024/35 – Dominique a.k.a. DimStar (Dim*)
(dominique.leuenberger.net)
On the kernel side, there are disagreements between long term C maintainers (who may not know Rust or may actively dislike it) and the new Rust community trying to build in Rust support. To make the Rust parts work, there needs to be good communication and cooperation between them to ensure that the Rust stuff doesn't break.
On the Debian side, they have strict policies that conflict with how Rust development works. Rust has a dependency system called Cargo which hosts dependencies for Rust projects. This is different from C, C++ where there really isn't a centralized build system or dependency hoster, you actually install a lot of dependencies for these languages from your distro's repos. So if your Rust app is built against up to date libraries in Cargo, it's going to be difficult to package those apps in Debian when they ship stable, out of date libraries since Debian's policies don't like the idea of using outside dependencies from Cargo.
Yup. I like their just in December approach too. I have a problem with distrohopping so I'm often re-setting up my system. Every time I do, Thunderbird pops up donation prompts both in the app and in my browser. I get why they do it, but it's annoying when that happens. KDE's approach avoids this pitfall.
I wonder how inflated that 4 million active user number is. They say it's measured by "count[ing] the number of updates to that runtime we've served between two releases". But that method doesn't account for people distrohopping/reinstalling or QA testing by distros.
I maintain a snap package and something I really like about the Snap Store is the metrics they give. Note that this data is aggregated, I can't see anything specific about a user. I am able to see:
- weekly active users
- distro and version
- CPU architecture
- country
- which version of app
- which channel (stable, beta, edge, etc)
But Flathub only measures total downloads. An app could get a thousand downloads and those thousand people could immediately uninstall the app and you would have no way of knowing that. With snap, you would see a week later a drop off of a thousand users.
My experience differs. I used a Chromebook that had a Celeron and it worked pretty well, not much worse than my Ryzen 5 4000x laptop on Windows or Linux.
Not sure if Linux would run better or worse than ChromeOS on that Chromebook.
A reminder that the Linux Foundation does what its members want. The members may not care about the Linux desktop, but more server oriented things and running LLMs on those servers.
fixes introduced regressions
Software development in a nut shell
I've seen the thing about 'mixed refresh rate monitors' couple of times and I also don't get it. What issues are people having?
If you use multiple monitors, X treats them as one big monitor. And it will refresh that one big monitor at only one refresh rate, usually the slower one.
Say you have a 144hz monitor and a 60hz monitor. X will choose to refresh that one big monitor at only 60hz. So if you drag windows around on your 144hz, it will visually look like 60hz.
There are some exceptions to this. The cursor will move at the highest refresh rate if it's operating in hardware cursor mode. In software cursor mode, it will look laggy. Games will usually operate at the higher refresh rate.
fractional scales are an issue for them?
This is a whole other issue. Not everything implements fractional scaling nicely. For example, currently GTK handles fractional scaling by rendering at 200% scaling, then resizing the output. This uses more more processing power and uses more battery. And things are fuzzy. As for why, imagine you have a 15 pixel wide element at 100%. With fractional scaling at 125%, that element is then supposed to be 18.75 pixels wide, which is impossible. So what do you do? Round up? Round down? Same question for a 17 pixel wide element, at 125%, it would be 21.25 pixels wide. Round down? Round up?
Some toolkits don't do the render at 200% then resizes method, but still suffer from other issues.
As for focus and positioning both Gnome and Awesome have settings for this and I never had issues with any of it.
Most stuff follows the rules, but not everything. Discord, Steam, and Bitwarden ignore my settings under X. But I can force Discord and Bitwarden to run using Wayland, which fixes the issue.
Wayland is more secure, better at handling mixed refresh rate monitors, and much more modern. Another thing that I like is that apps don't have as much control over the positioning and focus of their apps, so apps open in more consistent locations and are less likely to steal focus.
Their website is down
The reason snap reinstalls is just due to basic dependency management, nothing sinister. Apt has a feature to stop a package, such as snap, from reinstalling if you don't want it.
Although I don't see the point in removing snap. Just uninstall the snap version of Firefox and use flatpak for whatever you want. Or if you don't like that, have fun dealing with third party packages and apt funkiness.
With an encrypted disk, you only need to enter the encryption password when you shutdown or restart. Suspending and ~~sleep~~ lock screen don't need your encryption password.