News for hackers. Stuff that matters.
[dead]
Re:X.org on NetBSD – The State of Things by arp242 on Sunday May 05, 2024 @11:31PM (#40270892)
You've been ranting about this for about 9 years now.

bitwize on Aug 31, 2015 - https://news.ycombinator.com/item?id=10149015

> It's written against an obsolete windowing model for a deprecated window system.

bitwize on Jan 9, 2016 - https://news.ycombinator.com/item?id=10869618

> Since X is now deprecated tech

And tons more: https://hn.algolia.com/?dateRange=all&page=3&prefix=true&que...

Maybe give it a rest and let others have their toys without flying off the handle with comments that say or contribute nothing.

And it's not even applicable here; there's literally a linked post about how Wayland is being worked on in this article's first sentence.

Re:X.org on NetBSD – The State of Things by bandrami on Sunday May 05, 2024 @10:44PM (#40270678)
What an odd comment to make on a story that was literally about NetBSD's maintenance work on X.org
Re:X.org on NetBSD – The State of Things by chungy on Sunday May 05, 2024 @09:37PM (#40270321)
> Without a Wayland story, the BSDs will really end up dying, at least as desktop systems.

Good news then, FreeBSD already has working Wayland and NetBSD is working on it. Granted, I think OpenBSD stands out without a Wayland plan, but maybe I'm wrong there.

Re:X.org on NetBSD – The State of Things by alpn on Sunday May 05, 2024 @09:46PM (#40270378)
> I think OpenBSD stands out without a Wayland plan, but maybe I'm wrong there.

check this out - https://www.openbsd.org/papers/eurobsdcon2023-matthieu-wayla...

Re:X.org on NetBSD – The State of Things by johnny22 on Sunday May 05, 2024 @09:57PM (#40270430)
I found this a bit more enlightening than that slide deck, although it's a bit old https://xenocara.org/Wayland_on_OpenBSD.html
Re:X.org on NetBSD – The State of Things by wkat4242 on Monday May 06, 2024 @03:32AM (#40272136)
FreeBSD's Wayland technically works but you can't start a KDE session on it. So it's not all that useful.

Not sure about other desktop environments as I don't use them.

Re:X.org on NetBSD – The State of Things by rabbits77 on Sunday May 05, 2024 @09:32PM (#40270292)
The article begins by explaining that it’s a follow-up to an earlier article on Wayland!
Re:X.org on NetBSD – The State of Things by bitwize on Sunday May 05, 2024 @09:43PM (#40270359)
Indeed; and if you read that article it says that current Wayland compositors depend heavily on Linux infrastructure, and have not yet accepted patches to support NetBSD. Everything Wayland on the BSDs is in the "one guy faffing about to see if he can get it working" stage. Unless/until the Wayland project starts mainlining BSD support, or the BSD projects have robust parallel maintenance of the core Wayland packages and compositors, BSD as a desktop system is dead in the water.
Re:X.org on NetBSD – The State of Things by asveikau on Sunday May 05, 2024 @10:14PM (#40270513)
People not having the same priorities as you does not equate to death. You are being rude and overly dramatic.
Re:X.org on NetBSD – The State of Things by llm_trw on Sunday May 05, 2024 @10:21PM (#40270557)
Ah, what a delightful opportunity to delve into the nuances of the English language and its wonderfully intricate idioms! Let's embark on an enlightening exploration of why the phrase "dead in the water" is certainly not the same as simply being "dead." For anyone less familiar with the idiomatic expressions and metaphors of English, this can be a fascinating journey.

To begin with, when we hear the word "dead," one's mind might instinctively leap to its most literal and unfortunate meaning—devoid of life. In biology, this means the cessation of all vital functions: no heartbeat, no brain activity, no breath. The ultimate and irreversible state that all living things, sadly, will eventually meet. It's quite final, isn't it? The end of the line. Kaput. There's no ambiguity here; dead means dead.

However, the wonders of language allow us to use words in metaphorical or idiomatic expressions to convey more complex or nuanced situations or states. And that's where "dead in the water" swims into the scene. This phrase, you see, has nothing to do with the literal cessation of life. Oh, no. It's far more colorful and applicable in a variety of non-lethal scenarios.

Originally, this idiom comes from the nautical world—a domain rich with metaphorical language, given the myriad challenges and adventures faced at sea. Imagine a ship, if you will, its sails billowing as it cuts through the waves. Now, picture it suddenly unable to move; the wind has died down to nothing, the sails slump, and the ship is merely adrift, going nowhere. It is, quite poetically, "dead in the water." The ship isn't literally dead, of course—it's just temporarily incapacitated, unable to proceed along its intended course until the wind decides to grace it with its presence once again.

Transposed into everyday usage beyond the high seas, "dead in the water" is a vivid metaphor for projects, plans, or initiatives that have come to a halt—stymied, unable to progress, much like that becalmed ship. It's used to describe something that has little hope of success or revival in its current state. For instance, if a business venture runs out of funding or a new policy is halted by regulatory issues, they might be described as "dead in the water." Not literally deceased, but stuck, with no forward momentum.

In essence, while "dead" is the cessation of life, "dead in the water" is about cessation of progress or movement—figuratively speaking, of course. The latter suggests a temporary state, a problem potentially fixable, perhaps with effort, change in strategy, or a shift in external conditions, unlike the permanence and finality of being literally dead.

Isn't it simply marvelous how language lets us draw such specific shades of meaning with just a tweak of phraseology? Through this exploration, we can appreciate not only the richness of English idioms but also the joy of explaining something so deceptively simple yet profoundly different. Here we stand—or float, if you will—at the junction of literal and metaphorical, grasping the beauty of expression. And isn't that what language is all about?

Re:X.org on NetBSD – The State of Things by dgfitz on Sunday May 05, 2024 @11:03PM (#40270768)
I had to go through your post history to see if you were some kind of gpt bot. That was quite impressive.
Re:X.org on NetBSD – The State of Things by beepbooptheory on Sunday May 05, 2024 @11:08PM (#40270797)
Language is great and rich and all that but you forget too quickly that it's a two way street. Nothing gp said implied that they didn't know the idiom. Indeed, it seems obvious to me they were just being concise, which is perhaps a virtue of prose you could benefit from.
Re:X.org on NetBSD – The State of Things by KAMSPioneer on Monday May 06, 2024 @03:26AM (#40272096)
As an outside observer, it seems reasonable to assume asveikau missed the figurative language. The original phrase used was "dead in the water," which as noted does not imply death; however the response alleged that death was (rudely?) what the original commenter was talking about.

Seems blown out of proportion, at least partially because of missing figurative language. The above wall of text seems a long-winded, somewhat tongue-in-cheek way to say "yeah I didn't say that."

Re:X.org on NetBSD – The State of Things by necovek on Monday May 06, 2024 @05:15AM (#40272730)
I think one should allow others to look at the entirety of the thread started by bitwize, where they claim:

> ...the BSDs will really end up dying,...

That wasn't very figurative, even if "dead in the water" was. For all it's worth, bitwize might have been using that figure of speech inappropriately when they really meant "dead".

All this to say that even as an outside observer, one can read exactly the same things differently, so perhaps we should all get off our high horses and start riding ponies or bicycles (what? :)) — I mean, back to the discussion at hand.

Re:X.org on NetBSD – The State of Things by hasmanean on Monday May 06, 2024 @05:18AM (#40272741)
Not everybody understands English 100%.

The guy in the old west who drew his gun and said “them’s fightin’ words?” He probably didn’t enough English to understand the whole sentence but picked out a few words which meant to him “fight.”

Re:X.org on NetBSD – The State of Things by KAMSPioneer on Monday May 06, 2024 @07:04AM (#40273255)
Of course not everyone understands English perfectly. Even among native speakers it's easy to misunderstand (especially on a web forum). I wasn't making a judgement.

Anyway, it was pointed out that the same user that said "dead in the water" did indeed comment upthread that BSDs will "end up dying," so goes to show that I wasn't paying attention.

Re:X.org on NetBSD – The State of Things by asveikau on Monday May 06, 2024 @12:12PM (#40276276)
I am a native English speaker raised in Washington DC.

I am literally pointing out that Wayland enthusiasts love to gang on X11 as "dead" as a put-down and anybody who still uses it is evil or something. It's a toxic attitude that I've seen a lot here. It should ... pardon the metaphor .... die.

Re:X.org on NetBSD – The State of Things by asveikau on Monday May 06, 2024 @12:05PM (#40276181)
> As an outside observer, it seems reasonable to assume asveikau missed the figurative language.

No, I didn't miss it at all, and this is a weird take.

However, its appropriateness as a metaphor does have to do with the literal meaning. Even a less maintained software project with a longer-term deprecation roadmap that still has millions relying on it is not "dead". This very article is talking about how the *BSDs are putting more maintenance into that tree than upstream, and those are actually signs it isn't a total dead-end; they've done that maintenance over the years because it's valuable to them. But bitwize was calling it dead in an attempt to put it down. I've found this particular brand of negativity is very common in Wayland enthusiasts. It is like ad hominem in software maintenance discussion. The source is available for anyone to hack on and use, or not, as they please. There's no sense in ad hominem attacks, exactly as bitwize engages in above, for that.

To be honest, the attacks like this remind me of the XZ backdoor. The sock puppets in those mailing list threads complaining, I would say whining, about "dead", "unmaintained" libzma were channeling the exact same energy. Cool it down. It's not necessary.

Re:X.org on NetBSD – The State of Things by golem14 on Monday May 06, 2024 @04:30AM (#40272454)
... It's run down the curtain and joined the choir invisible. This is an X11-parrot ...
Re:X.org on NetBSD – The State of Things by exe34 on Monday May 06, 2024 @04:45AM (#40272548)
Thank you Sheldon!
Re:X.org on NetBSD – The State of Things by doublerabbit on Sunday May 05, 2024 @10:05PM (#40270474)
And that's what Wayland wants.

"We will only develop for Linux if you want it do it yourself" is the vibe I get from the Wayland team.

Why should FreeBSD be the ones who have to develop? The stubbornness of Linux users.

Re:X.org on NetBSD – The State of Things by asveikau on Sunday May 05, 2024 @10:20PM (#40270553)
I think it's more the detail they lost (or do not agree with) is that working successfully in multiple environments can valide the strength of the design. Some people will look at a slightly different structure underneath and see it as noise and hassle instead, where you or I may see their action as taking unnecessary or questionable dependencies.
Re:X.org on NetBSD – The State of Things by bandrami on Sunday May 05, 2024 @11:27PM (#40270875)
The short version is that the Linux ecosystem has for whatever reason spent a decade or so resolving the already-solved problem of "who is logged in to this TTY?" and came up with a new way to solve that that the BSDs don't in general implement and Wayland relies on.
Re:X.org on NetBSD – The State of Things by vundercind on Sunday May 05, 2024 @11:35PM (#40270906)
Red Hat wants it to be really hard to remain compatible with Mainstream Linux (whatever Red Hat does) while also differentiating your distro from theirs in meaningful ways, and wants some good old “fire and motion” against competitor distros.

At least, I think everything they’ve been up to and these projects they heavily influence have been doing makes a ton more sense if that’s the plan. It’s that or a lot of weirdly-hostile and disorganized stuff has been happening by chance in a way that achieves that effect by accident.

The BSDs are just collateral damage, I reckon.

Re:X.org on NetBSD – The State of Things by llm_trw on Monday May 06, 2024 @07:22PM (#40280615)
Jokes on them, the BSDs are more usable than Linux now if you care about productivity.
Re:X.org on NetBSD – The State of Things by armitron on Sunday May 05, 2024 @10:49PM (#40270703)
I predict Wayland will be dead long before we stop using X.
Re:X.org on NetBSD – The State of Things by vundercind on Sunday May 05, 2024 @10:56PM (#40270731)
When you look at how long it’s been around versus where Xf86/x.org were on a similar timeline… yeah, we’re almost halfway through the life of the project, if history repeats itself. Its replacement may be expected to start designating it “legacy” and its boosters sneering at out-of-touch Wayland users well inside a decade.

(It fares better compared against x11 instead, but not as much-better as one might guess—either way, it’s been a sloooow moving project)

Re:X.org on NetBSD – The State of Things by bandrami on Sunday May 05, 2024 @11:29PM (#40270884)
"Fractional scaling? Seat management? What is all this cruft? Let's start over from scratch and This Time We'll Get It Right!"
Re:X.org on NetBSD – The State of Things by sweetjuly on Monday May 06, 2024 @01:30AM (#40271408)
it's good for the economy!
Re:X.org on NetBSD – The State of Things by p_l on Monday May 06, 2024 @03:08AM (#40271983)
All of that things that weren't truly handler right by wayland anyway, thanks to pushing everyone and their pet hamster into implementing complete display servers :P

I find especially funny how Wayland attempted to have "tear free done right"... and the expected display path (GPU accelerated) turned out to either involve 1 or more frame delay, or tearing because Wayland protocol didn't support explicit sync on render finish.

Re:X.org on NetBSD – The State of Things by simoncion on Sunday May 05, 2024 @10:26PM (#40270580)
> What about the fact that X.org itself is ... falling apart

Works for me, and has for literal decades.

> ...without active maintenance...

This update to xorg-server was stabilized on April 14th, and it looks like library changes required me to rebuild and reinstall it like two days ago:

  $ eix -I xorg-server
  [I] x11-base/xorg-server
       Available versions:  21.1.13(0/21.1.13)^t **9999(0/9999)*l^t {debug +elogind minimal selinux suid systemd test +udev unwind xcsecurity xephyr xnest xorg xvfb}
       Installed versions:  21.1.13(0/21.1.13)^t(03:15:55 PM 05/03/2024)(elogind udev xorg -debug -minimal -selinux -suid -systemd -test -unwind -xcsecurity -xephyr -xnest -xvfb)
       Homepage:            https://www.x.org/wiki/ https://gitlab.freedesktop.org/xorg/xserver/xorg-server
       Description:         X.Org X servers
> ...and governance the writing is on the wall for X.org.

Weird. Looks like they're running Board of Directors elections. [0]

[0] <https://lists.x.org/archives/xorg-devel/2024-March/thread.ht...>

Re:X.org on NetBSD – The State of Things by NekkoDroid on Monday May 06, 2024 @12:47AM (#40271206)
> Weird. Looks like they're running Board of Directors elections. [0]

Just so you know: The X.Org Foundation also oversees Wayland.

Re:X.org on NetBSD – The State of Things by bitwize on Monday May 06, 2024 @01:27AM (#40271393)
There's X.org the software and X.org the foundation.

X.org the foundation is electing a board of directors. They're also all-in on Wayland.

Re:X.org on NetBSD – The State of Things by ori_b on Monday May 06, 2024 @06:58AM (#40273213)
And regularly releasing new x server versions. It seems like there's a new release every couple of months.

For example, in January this year, xrandr got code to allow for multiple virtual monitors on a physical display. In April, there were 2 bugfix releases.

Re:X.org on NetBSD – The State of Things by simoncion on Tuesday May 07, 2024 @07:51PM (#40292857)
Yep.

If they were all-in on Wayland, they wouldn't be making regular xorg-server releases, and definitely wouldn't be adding new features to xorg components. (Because, yanno, they wouldn't have any staff available to do those things.)

Re:X.org on NetBSD – The State of Things by hapless on Monday May 06, 2024 @01:32AM (#40271419)
X11 has been unmaintained not once, not twice, but THREE times and it's still the dominant system on UNIX-type things. Xorg is, itself, the thrice-disowned descendant of the o.g. X project.

That is what it is! It's fine! if Wayland is the future, so be it, but it won't be because X11 got deprecated again. X11 has been deprecated plenty of times before!

Wayland may very well take over the unix and most especially linux desktop story, but that is not a done deal, yet. My last two? three? jobs all explicitly required X11 as a thing, so if giant enterprises are not picking up wayland, the deal ain't done, yet, you read me?

Re:X.org on NetBSD – The State of Things by nrabulinski on Monday May 06, 2024 @02:25AM (#40271737)
If we’re going by giant enterprise standards then Windows XP is the latest version of windows
Re:X.org on NetBSD – The State of Things by exe34 on Monday May 06, 2024 @04:44AM (#40272540)
That's a really good comparison actually - windows after xp has been a shit show.
Re:X.org on NetBSD – The State of Things by mst on Monday May 06, 2024 @05:44AM (#40272867)
Eventually somebody will find X11's phylactery.

As an fvwm2 addict, I do not relish that day.

Re:X.org on NetBSD – The State of Things by dmitrygr on Monday May 06, 2024 @01:52AM (#40271523)
> What about the fact that X.org itself is unmaintained and falling apart?

Is it? Seems to work just fine. Not all that is new is good. Not all that is old is bad.

Re:X.org on NetBSD – The State of Things by noirscape on Monday May 06, 2024 @05:04AM (#40272680)
It won't be replacing XOrg anytime soon, because XOrg is a walking example of "worse is better". Yes, it's ancient, bizarre in some ways, cluttered with feature bloat and a security nightmare. Nobody denies that.

The problem is that said feature bloat is also exactly what makes it attractive to desktop users. I'm not saying that Wayland has no use; it can reliably cover ~90% of all computer tasks and if you're just setting up some sort of kiosk/server with one application, I think it's hard to not pick Wayland since you can just grab a thin renderer and avoid all the extra crap that comes with XOrg.

But for desktop, the weird/random things XOrg allows you to do are what makes it the undisputed king to this date.

It's not what's best that wins. It's that what covers the widest amount of usecases that does, regardless of any amount of bizarre rituals that you need to do to get it working (and only if you have feature parity does less weird rituals take over in priority). Wayland already lost that race before it even started since feature parity with XOrg is a non-goal.

Other examples of this concept in action: Any old-school Microsoft project (really, just all of MS Office), the entire HTTP frontend stack, SQL, PDF.