Comments by "Anony Mousse" (@anon_y_mousse) on "I'm Gonna Try Zed Now (RIP VSCode)" video.

  1.  @oblivikun  On top of that, I'll say it again, end users should not need to care about X versus Wayland because the developers should just use a toolkit. In this case the toolkit has to care, and the WM or DE is the toolkit, but any program that you use which isn't a WM or DE shouldn't cause problems and the fact that they do shows a lack of capability on the part of the application developer.
    2
  2. I'm sure that 99% of developers will never get what I mean by this, but this is why you use toolkits. No one should care, or even need to care, about X or Wayland or low level primitives of the GPU, unless you're writing a game. A text editor, no matter how complex it is, shouldn't require this level of optimization, and if they weren't writing everything from scratch and doing the GPU acceleration by hand, they wouldn't have to worry about these issues. This has been, and will continue to be, my biggest complaint with regards to the rewrite everything crowd. Of course, if they were writing the toolkit, then this behavior could be overlooked because they'd need to deal with the complexity, but game developers have already solved these optimizations and if they knew anything about game development then they'd not be looking at it and going, "what is happening here". Maybe you think this is too harsh. After all, it has taken years of learning for me to understand everything that I do and they're probably in their 20's, but it goes along with what I've been saying over and over again about not reinventing the wheel. DRY code is better than WET code.
    2
  3.  @Bvngee  The WM and DE are finishing the work of the toolkit. You can't just use Qt or GTK and then have no WM/DE, because there's more work that they do which neither Qt or GTK handle. And again, you shouldn't need to care how the toolkit is implemented at a basic level. It may double the workload for them to target two protocols and/or compositors, but that's the reason they exist in the first place, to solve the common problems so the majority don't need to worry about them. If they're making a user choose between X or Wayland, then they're doing it wrong. It's like the age old argument about just using assembly versus a higher level language. Or to phrase it in a catchy way: the problem is already solved, so stop trying to solve it.
    1
  4.  @beedeeuniko  I've seen far too many projects in the last 10 years that would contradict that assertion, unfortunately.
    1