Larry was pretty much checked out by that point. Jon was the one who wanted Perl 6. Larry wrote the specs for it but he wasn't leading the project.
I stand corrected, thank you.
I think it was "only perl can parse Perl" (sic). And yeah, it's got context-dependent grammar.
I could never understand it but I knew a few perl wizards and they were like if you asked them hey how do I do this, they'd sit there, stare autistically for a minute or so, then type a single line of completely incomprehensible voodoo runes and suddenly exactly that would get done.
It's something similar to that called "Rename Master". Holy shit! I just found out that it is STILL being updated. The version I have been using I got back in 2004 or so and never looked for an update until now because it "just worked."
I mean, the JS ecosystem is notorious for using 3rd party packages with 0 research or vetting. Capitalizing on it by selling it as a service is a pretty good idea. The target audience for this is probably writing code on a MacBook with little understanding of the underlying tech aside from what they were explicitly taught in their college classes.
I think opinions on Wayland likely correlate with distro choice. Wayland is for the Arch and Fedora crowd. It's a shiny new toy that isn't quite ready for everyday normal users, but if you want to be the beta tester it's available and it's clear that it's here to stay. If you're the type who runs a Debian based distro it's probably frustrating because you value stability more. Moving everyone over will be frustrating because until it has market dominance there will be some compatibility issues. It's pretty usable now, but it's a transition period that necessarily entails forcing people over who don't care and don't want to deal with it. Hopefully once it's the defacto standard these issues will be ironed out. For now you're in between a rock and a hard place where you either put it off and will eventually be left behind, or you adopt a less stable system for now in hopes that it increases markets hare and expedites the development of fixes for it's issues.
That sounds like the arguments I used to hear about GNOME 2 vs GNOME 3.
I personally use Wayland, with hyprland specifically. I really haven't had any issues with it aside from XWayland rendering for electron apps, and that is easily fixed with a couple cli flags or config files. It might be more annoying in a traditional desktop environment, but since I'm already binding most of my main applications to keyboard shortcuts in the hyprland config, it's a non-issue for me. I store all of my critical data on my servers, so I enjoy being a little more bleeding edge on my laptop as well.
It's for some of them. I use Arch (btw) and have stuck with X11. I used Wayland for a bit and found it to be exceedingly okay. It worked fine, no better than X11, until I got my second monitor. After that, it was constant issues, mostly stemming from the fact that my two monitors are different resolutions. X11 may forget that my secondary monitor is supposed to be vertical, but it's never fucked the resolution to the point that my computer was unusable and had to be restarted.
Huh really? Wasn't Wayland supposed to handle multi-monitor setups better? Guess you learn something new every day.
I think it does if you're a reasonable person with two of the same monitor. I, however, am not reasonable, so I have one nice monitor, and the secondary is literally the cheapest one I could get from my local electronics shop. The second monitor is also in portrait mode, which even X11 struggles with.
I've honestly never had much of an issue with this on X. Landscape, portrait, stacked every which way, it just works. The different resolutions has caused issues (using xrandr to set scales didn't work as well as I'd hoped, probably because I didn't do it right), but if I just accept that any lower res monitor will have everything scaled stupidly large, I can live with it. I only used one to hold messenger apps and a music player anyway.
I meant it more in the "I'm willing to accept a few kinks here and there, I want the newest packages" way. There's probably an element of works on my machine going on, though I use a fairly unconventional setup myself.
I'll also freely admit that I'm an atypical Arch user. I do a fresh install, add the shit I need, and then leave it alone. I update maybe twice a week. Having bleeding-edge software isn't all that important to me, but I use Arch because I know Arch and don't care enough to learn anything else.
Now do you mean 'kink' in the technical use of the word...
DaVinci Resolve is a multi-platform program, and those almost entirely support Gnome better then KDE. Generally only programs made specifically for KDE (like all the programs that put a K at the beginning of their name) will have less support for Gnome. You sure it's not a Wayland issue?
It's both GNOME *and* Gayland issue. GNOME-tards, for whatever reason, don't want to support server-side decorations, and instead want you to add decorations "manually", which has been a problem for a while now. And, in true Gayland fashion, SSD is an "extension", so technically you don't need to implement it, so here we are.
So you basically run an X server embedded in wayland and while I'm sure that works just fine, this doesn't strike you as slightly odd? Wayland has been in the making for 15 years. A lot of the "bugs" it has are just shortcomings of the protocol that can never be solved without either turning wayland into something else or shoving some very customized solutions into the compositor or other window managing layers, making that solution only valid for whatever (stack of) windowing system you run. The "mess" of X is not going away, it is only going somewhere else. Of course the gnome people would embrace this, because red hat wants a monoply on the Linux ecosystem and red hat is the largest corporate contributor to gnome (when you wonder about some decisions in open source software projects like this, always follow the money). The technical merits of the wayland protocol have been discussed a lot here though so I won't repeat it all.
