

0·
3 months agoWhen is the last time you tried a Wayland DE? I can’t speak to them all, but Plasma for one has been in really good shape for basically everything a typical user might want to do with it for around a year now.
When is the last time you tried a Wayland DE? I can’t speak to them all, but Plasma for one has been in really good shape for basically everything a typical user might want to do with it for around a year now.
X11 versus Wayland isn’t some kind of holy war; Wayland was specifically designed as a successor protocol to the largely cobbled-together X and is objectively superior to it in most ways outside of accessibility.
I mean, technically there’s nothing preventing that, but in practice it’s a fairly uncommon mistake to make and it’s immediately obvious that there’s an issue the first time that path is taken. If something like that makes it to production, it clearly points to an issue with test coverage rather than code paradigm.
Have you actually worked in a programming role before? Googling things is absolutely the norm. Most people don’t know every single in and out of every library/framework they’re using, especially when learning new ones. This goes double for more complex or sprawling frameworks where it may be less than obvious how to perform a particular task from the documentation alone or when running into undocumented limitations or bugs (although admittedly an in-IDE assistant won’t be too useful for that anyway).