Leaflet @ that_leaflet @lemmy.world

[Mastodon](https://fosstodon.org/@that_leaflet)

---

Read more

Posts

264

Comments

376

Joined

2 yr. ago

OS 8 should hopefully be out in September. I'm looking forward to trying it out with the Wayland session.

My guess is his abrasive behavior. For example, this comment: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/269#note_2233724.

It should be noted that he does not have the privilege to NACK things. He can only give his opinion on matters.

It should also be noted that he is not banned from Gnome, just the FreeDesktop Gitlab.

No way it's Microsoft neofetch

I'm not 100% on the details, it's hard to find good documentation on this, but here's my understanding.

Every machine with snap install has an ID associated with it. Whenever snap refresh is run, a list of installed apps is sent back to Canonical so that Canonical can fetch updates. But they also use that list is also used for generating metrics. Users aren't double counted because of the unique ID associated with the install. So Canonical just needs to keep track of all the IDs in the last week who've checked for updates and count them up. That final number is then shown to maintainers of the snap.

Snap isn't checking if you actually open the snap though. It's just counting people who have the app installed.

Even if Valve pushed their own Steam machine back then, it would have failed miserably. It simply had terrible game support because Proton didn't exist (or integration with wine). Only the few native linux games out there would work.

But now Valve has Proton. I doubt the Steam Deck would have taken off if it wasn't for that.

Edit: it they're counting updates, then this number probably is accurate, so the bit questioning the number can probably be disregarded

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.

Why would they start providing their own kernels?

All this change is that instead of choosing the latest stable release at the time of Ubuntu's kernel freeze, they may choose to use the in-development kernel if it's expected to release before the next Ubuntu release.

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

Why not? Mozilla already fixed the biggest issue plaguing MV3 by continuing to allow MV2 ad blockers.

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.

Integrals. I can have an area function, integrate it, and then have a volume.

And if you look at it from the Rieman sum angle, you are pretty much adding up an infinite amount of tiny volumes (the area * width of slice) to get the full volume.

They do understand, they're just saying that OpenSUSE doesn't have this problem since you can choose your DE in the installer.

The issue is worked around in newer kernel versions. But it's better to just update your BIOS to fix the issue.