It’s not just a percentage thing. 1 person yesterday to 2 people today is a 100% increase. Not much of a surge, at least in terms of news worthiness. Going from 6% to 10% sounds more news worthy than going from 1% to 2% despite the latter being a much larger percentage increase.
That’s why we’re talking about relative percentages.
In your example we would need to know how many trees existed on your road/city before. If there were less than 3 or 4 trees in your city before this, saying there was a surge is likely fine.
I gave you that information, I said “from 1 to 2” and added context of “a tree” (singular)
My terribly made point is that although technically correct when talking about relative increase it’s dumb as fuck to say trees “surged in population” after adding just one more on one street. It’s a drop on the ocean.
I feel like the term surge respects the final total relative to what its maximum could be as well as the relative increase. But obviously language is regional and up for interpretation
I still have a Rage 128 hanging around as a ‘temporary head’ for installing headless servers. Many happy nights playing Thief: The Dark Project with it, and now it’s only good for rendering a TTY at a barely acceptable resolution. And soon, not even that. Goodbye, little e-waste :-(
One of the specific issues from those who've worked with Wayland and is echoed here in Nate's other post that you mentioned.
Wayland has not been without its problems, it’s true. Because it was invented by shell-shocked X developers, in my opinion it went too far in the other direction.
I tend to disagree. Had say the XDG stuff been specified in protocol, implementation of handlers for some of that XDG stuff would have been required in things that honestly wouldn't have needed them. I don't think infotainment systems need a concept of copy/paste but having to write:
Is really missing the point of starting fresh, is bytes in the binary that didn't need to be there, and while my example is pretty minimal for shits and giggles IRL would have been a great way to introduce "randomness" and "breakage" for those just wanting to ignore this entire aspect.
But one of those agree to disagree. I think the level of hands off Wayland went was the correct amount. And now that we have things like wlroots even better, because if want to start there you can now start there and add what you need. XDG is XDG and if that's what you want, you can have it. But if you want your own way (because eff working nicely with GNOME and KDE, if that's your cup of tea) you've got all the rope in the world you will ever need.
I get what Nate is saying, but things like XDG are just what happened with ICCCM. And when Wayland came in super lightweight, it allowed the inevitably of XDG to have lots of room to specify. ICCCM had to contort to fit around X. I don't know, but the way I like to think about it is like unsalted butter. Yes, my potato is likely going to need salt and butter. But I like unsalted butter because then if I want a pretty light salt potato, I'm not stuck with starting from salted butter's level of salt.
I don’t think infotainment systems need a concept of copy/paste but having to write:
Having lived through the whole “phones don’t need copy and paste debate”, which fortunately got solved by now having it everywhere I’m in the camp “just stick that everywhere, just in case somebody might use it one day”
I love this! Not only for the comedic value, but throwing kernel oopses on-screen when they can’t be easily captured when unprepared would be of great help in solving system problems. Unlike the cryptic messages Windows displays, Linux kernel messages are quite useful.
Wayland has fixed so many head-scratching issues I would get running 6 monitors on 2 GPUs under X11. I’d often end up with missing monitors, placed in wrong spots that I’d have to rearrange every reboot until an update would come through that would fix it again for a few months, then all over again.
Since I moved to wayland, everything just works. When it doesn’t, it’s not a display server issue, it’s something physical. I just had a couple monitors fail to show up and thought “oh hell, it’s back to this, eh”. But I open the tower, seat the offending GPU better, and everything comes up like normal, and all the screens are in the right position, it just remembers.
Anyone that thinks X11 is still superior probably runs on a laptop with a single screen.
I mean I’m fully with you on the fact screen autodetect isn’t stellar on X but there’s no need to exaggerate with “2 or 3 scripts”. It’s one xrandr command.
Ive seen several devs do that, and also some of my gaming friends have 3 monitors.
I barely know anyone who only has a single display. Most people I know have one high refresh rate monitor, and one office monitor for discord and the likes.
I have 2 75hz and a 240hz. It’s been alright for me on kde and x11. Although, I do want to give this Wayland thing a shot after hearing it being brought up so many times
Nothing would make me more happy. I really wish it weren’t such a pain to deal with the telephony. You check devices on postmarketOS & while some devices can boot, it’s usually the actual phone part that isn’t working–which is kind of an important part. The open hardware phones work fine, but their specs are ancient while being as expensive as flagships. I still have eventual hope tho as device needs have started to plateau.
I'm guessing this is because of more sales of the Steam Deck, haven't got myself one yet but I'd love to as everyone that has gotten ones has said it's worth the money as well as is a great way to get through your games on the go.
6 of the top 10 are verified or playable or 43% of the top 1000 games. But verified and playable is only a subset of the games that work, quite a few unsupported games do as well. If you go by medals the 7 of the top 10 are silver ranked or better (minor issues but generally playable) and 88% of the top 1000. So there are a lot of games that are playable that are still listed as unsupported on the deck.
You can see the numbers for various different things at www.protondb.com as well as different reports for all the games (including some tips on how to get things to work or work better).
TBH I’ve yet to come across any game I haven’t been able to play (aside from the obvious VR/occasional anti-cheat), most unsupported games just haven’t been tested for most cases
Edit: out of curiosity I actually went through my library to see just how many unsupported games I could download and try (again, not the VR ones lol).
I ended up getting caught up playing Revita all day and it says unsupported but it definitely works! For anyone else interested in that game, it is having some development quirks but there’s a public beta branch of it that seems to be the “definitive” version of the game.
Uploaded a control scheme template for the beta since there wasn’t one I liked :D
Then I tried an old DOS game Litil Divil which also worked just fine. I’d have tried some others but like I said, addicting game be addicting
Same, I’m not a big multiplayer person so most of the time it works out. My latest has been Lethal Company, my first new multiplayer game this year 😂. Been a blast.
You may be right in that people are seeing how viable Linux is for gaming due to the success of the Steam Deck.
I’m not sure if steam deck is counted under Arch, but it’s definitely not Ubuntu, Mint, or Manjaro. It looks like the increase in Linux desktop is traditional desktop gaming.
Add the article says, the surge is entirely thanks to the Deck. There was a 35% surge in overall use but 43% of that use is the Deck so PC/laptop use has actually dropped.
It’s great to see that Pipewire has reached this milestone. Personally I’ve been using it since 0.3.35 for very basic audio needs and it’s been a very smooth transition. After installation I never had to tinker with it anymore. “It just works”^TM^
A new component “systemd-bsod” has been added to show logged error messages full-screen if they have a “LOG_EMERG” log level. This is intended as a tool for displaying emergency log messages full-screen on boot failures. Yes, BSOD in this case short for “Blue Screen of Death”. This was worked on as part of Outreachy 2023. The systemd-bsod will also display a QR code for getting more information on the error causing the boot failure.
Hibernation into swap files backed by Btrfs are now supported.
Actually looking forward to the btrfs swapfile hibernation; I have tried setting it up on my machine before but the documentation was never clear on whether it would work (or why mine wasn’t).
phoronix.com
Top