higher dpi/4k screens.
oled pixel layouts already have fewer subpixels than they should for say a claimed “1080p”, leading to weird blur or aliasing in places.
My high dpi phone has made my eink reader redundant; the sharpness simply makes it way more comfortable to read, for me enough to be on par with print.

And now I can only await how long my phone will remain usable, knowing no new phones with higher dpi (600ppi+) are being made.

The rewrite seems to be in the original project, so a fork of the old codebase would have to be done that everyone switches to, for that to be possible

The utility? Or it being a rust program?

This seems to be about junctions not shortcuts (which are at a higher level of abstraction)

That sounds a lot more justified then, thanks for the info.

For that extra certainty, was it consecutive comments and posts?
Could you have feasibly come across all of them organically if you used lemmy an unhealthy amount?

Angels in most renditions have bird wings (i.e. arms) growing from their backs in addition to normal arms and legs.

May be this (emphasis mine):

Removed Comment
Me: “Oh look, the ghost said something stupid again. I wonder what they’ve been up to.” [clicks profile] [sure enough, more stupid things are said, including blatant misinformation] Sorry that you say stupid things and break the rules, I guess? > I recall a few weeks back he said that because I don’t call out .ml that much (funny how he ignores me calling out Hexbear) I somehow must mass downvote his posts across lemmy. lol I’m sure you can quote me. It would be awful if your memory was as poor as your ability to construct coherent arguments. AND a place of honor in your bio? That’s unironically great. Thanks for helping spread me all over the Fediverse!

Maybe the admin misread? Or they read that and then actually checked the data and found PJ did downvote all that other users stuff or smthn.

I tried to take a short look at the data but PJ has over 150k votes which probably breaks the page I use. (Admins can natively see this info in lemmy)

Thanks, it’s beautiful (and so small)

As one of the parties involved, Here is my attempt at a writeup:
https://lemmy.dbzer0.com/post/48968557

I wrote it as a reply for here but ended up posting it standalone.

Is it possible to get an uncompressed or far less compressed version?

Not only almost, I got the real deal too, however quickly deleted.

That’s so new! My stuff still requires version 1.8
/s

Name the prime a “none”, the octave a sept.
Now, 2 “septaves”, c1 to c3, are a 14th. 2*7 = 14.

You can make off-by-one intervals work, but you have to constantly juggle some +1s or -1s compared to what we usually use.

If you counted distance in steps, then moving from your front door to your front door would be 0 steps, not one, and moving by 6 steps is twice the distance of 3 steps.

A piano with 5 septaves has 5*7 = 60 keys, wait.

So anyway mathematically one dodecave, one 12th, c1 to c2, has 12 segments, the frequency diffefence is 2. So a second, 2 notes, has 2/12 of that interval, the ratio is 2^2/12.
A first, a halftone, has 2^1/12 as its frequency ratio, and a none has 2^0/12 = 1, the same frequency.

No matter if you count physical keys, distance on a keyboard to change a note by, or mathematical frequency in the air, starting at 1 goes against our intuition, and when you try to add or multiply it is easy to get completely wrong results.

PS: You might want to go C to C on your 5 dodecave keyboard, in which case the concept of “started hour” etc. is familiar, you know to add one arriving at 61 keys, and you know that means an assymetry where one C doesn’t have 11 other keys to itself.
The other way around you’d have to subtract 4, so probably subtract 5 and add 1 since you were dealing with 5 tredecaves in your head not 1 base tredecave followed by 4 extension tredecaves.

Insert payed-paid bot here telling you payed is for boats and paid for transactions.

You need a few new tabs in the same instance, until it tries to start a new process. I can usually keep using ff for half an hour before running into it.

alias l='ls -lahv --time-style +%Y-%m-%d\ %H:%M:%S'

wayland is the norm at this point. The distros still on X11 are mostly the slow moving ones, but I would say we are on the trailing end of adoption now overall.

Wayland is still lacking features, and due to its newness also lacking documentation and tools available for X11.
But those are looking like more of a specialty application for X11. The main painpoints are gone.

The hardware (gpu) situation is fine to my knowledge, drivers have caught up. 10+ year old Nvidia cards (like a gtx 780) may need nouveau, but not sure if even that is still the case.
Some workflow stuff is just now appearing (like restoring the window positions when a program restarts) or still missing (like some custom input scripting functionality), this also impacts accessibility.
As an example I used to have a script that would input ctrl+pgup/pgdn into the window under my cursor without changing focus, so I could change pages the same way I can scroll in unfocused windows. That was done with some x tools for setting focus and sending keyinputs. It’s possible to input keys with root permission under wayland, but changing focus from a script is not possible to my knowledge.

This is all important stuff, but something most people won’t run into, and many more (like me) will accept as a tradeoff for the many advantages of wayland. Doubtless the protocol side will eventually implement apis for all of those missing features, and the tools making use of them will become widely known same as X11 used to be.

could you hold this “s” for a while? I need the / it was leaning on for some webdev.

According to AcronymFinder, the leading search result for “acronym finder”, dwl means “dying with laughter”. In combination with a questionmark it would form an exclamation of disbelief.

None ever, yes.
Not sure what you mean to ask there, but I gotta say hyprland would make a sick name for a tiling dwm.

Hey, there is an entire wayland bad x11 good article hidden in the last 4/5ths of the article!

Anyway, the article seems to argue that “toxic elements within Xorg projects, moles from BigTech, are boycotting any substantial work on Xorg”.
It seems to me that now that wayland has become the clear focus of development, most devs sinply want X11 to remain as a legacy element, not causing unnecessary issues elsewhere, just remaining on lts.
The train has sailed, wayland is the norm and everyone is working on implementing the last leftovers the article is parading in its weird latter half, rather than through much greater efforts achieving worse results in patching up X11.
They should have forked X 10 years ago, when people were still interested in improving it.

It being left behind is a logical and fully adequate explanation, arguing eee makes little sense when wayland is clearly a simpler protocol. If you wanted to harm linux or foss, and your plan was the transition to wayland and freezing of X11 development, I would call you stupid.

I don’t see why this fork, and this article, have to get conspiritorial about something this easily explained.

Now that we have the conspiracy crap addressed: wayland defense time

The Reg FOSS desk is nearing 60, […] He doesn’t care about […] high and variable refresh rates, tear-free video,

My fancy new monitor I got in '22 doesn’t work on X11. I’d have to replace my other monitors with matching new ones for a few grand, or keep watching videos and all else at 15fps, getting a headache. If you wanna keep your crt, why not keep an ancient X11, why this fork?
X11 doesn’t support normal modern hardware, my monitor wasn’t even special, it’s just higher fps than my other monitors and 4k.

Wayland does not currently allow controlling window position. This means that when you open KiCad, it cannot remember where you last placed your windows.

The window pos remembering api (name made up by me, I forgot the real one) has been finalized, and will be in this or the next KDE version, etc… The wayland people are fixing the criticism faster than the critics can shorten their list of remaining issues.

.

uhhhh… ok that’s all the wayland criticism, 'cause surprise, the last 2/5ths of the article are actually a rant about … gnome? I think?
Something about no more shortcut support or how removing title bars is bad and the gnome disk manager has bad ui.
Idk my shortcuts are better than ever and my title bars were still there last time I checked.
But maybe this “big no-accessibility” is why absolutely no tiling dwms have ever been seen for wayland ever. If you switch to wayland you will have to tile by mouse exclusively, you heard it here first!