Good Lord. I get that the EGLStream vs GBM thing is controversial, but this is childish. How are you supposed to discuss anything with someone who thinks like this.
To be honest I've never heard of this guy nor his project before, and I'm certainly not interested in trying it after his tantrum. There will be other tiling window managers out there (and I just use a normal window manager anyway). It's NVIDIA, they have a >80% share of the discrete GPU market. Someone will fill the gap. /shrugs
Hint: Linus Torvalds' tantrums are not a positive character trait worthy of emulation. Maybe they are a necessary evil when herding a dozen teams of a dozen dozen cats each, but I'm guessing that's not the situation with this guy. It looks a lot like a fanboy ranting.
Sway is a WM, and wlroots is a new library that should help in creating Wayland WMs (similar to wlc). SirCmpwn has to maintain all of that, and it turns out it's a fairly big task. Realistically, his WM will run on hardware running Intel for the most part, with AMD or Nvidia way behind. Optimizing for Intel is fairly simple, and it turns out it gives AMD support for free, since they use the agreed-upon APIs. His choice makes sense.
The thing is, people are going to always ask why that choice have been made. And I can understand this being super-frustrating, hence the post being so harsh on nvidia. But really, nvidia deserves it. Wayland wasn't designed in a vacuum, and nvidia took the wait and see approach. Once every bit were put in place, Nvidia came up with the EGLStream proposal. Not during discussion. After everything was said and done. Adding a codepath for EGLStream is really non-trivial, and I hope nobody does it because it really adds additional complexity.
Really, that AMD is getting more competitive is going to help the GPU world a lot. Nvidia has always been a bad citizen there, and oh boy if AMD ever gets in a position where they can compete on compute, that'd be great.
Well it's not. He's the one who has to do the work, and if I were in his position, I wouldn't do it either. Like if you ordered a coca cola machine compatible syrup pack, and instead received a pepsi co. one, and the manufacturer tells the court that they fulfilled your order even though you are left to accommodate something other than what they claimed to provide.
What NVIDIA has done is claim to support something, while in reality supporting something entirely different and ancillary which everyone else has to do work to accommodate. SirCmpwn isn't "fanboy ranting", he is talking about how ridiculous it is that NVIDIA has pushed the onus for supporting something which is effectively their own proprietary API on the rest of the ecosystem, for apparently no technical reason, and with either no consideration, or malice of intent.
I had this exchange with him: https://news.ycombinator.com/item?id=15511570
