Finally got me to unsubscribe. I'm surprised that the whole crew of them were cool with reposting the snippet of DHH calling linux maintainers "clowns and goblins" amongst other things.
I'm not really against such special symbols, only if they are too much, like in Perl.
~ and @ weren't replaced by anything with ::, though, ~Foo is Box<Foo> and @Foo is Rc<Foo> (or is it Arc<Foo>?). :: to access a member of a module already existed when ~ and @ was in Rust.
Out of the things you mentioned I think the following make totally sense to be included in a language runtime like this:
JavaScript runtime (obviously), package manager, test runner for unit tests, bundler, JSX, SQLite bindings, formatter, linter, YAML and TOML parsers. Maaaaybe even a Markdown parser and HTML5 parser. Definitely JSON, CSV and XML parsers.
I.e. similar to Python. Though Python is a bit of an incoherent mess. If you have all these you need them to be coherent.
None of that matters if you don't have a HDR monitor, only have one monitor, and when absolute basics of window management are somehow broken under KDE Wayland. Why that even has anything to do with Wayland I don't know. I just know that it all works perfectly when I use KDE X11. Maybe other DEs/WMs have better Wayland implementations, I don't know.
I use KDE and have for 10+ years. In my experience, kwin is the most stable and performant it's ever been. I don't notice anything at all, ever. Under X, it was common to get stuttering, tears, and dropped frames. Not anymore. I mean I run 2 204hz 1440p monitors. And it's perfect, always.
I'm not saying you're wrong, but it's clear that basics of window management are not universally broken under Wayland. It works well for me and has for a couple of years.
> None of that matters if you don't have a HDR monitor, only have one monitor, and when absolute basics of window management are somehow broken under KDE Wayland
So you think we should have one protocol for people who have HDR etc and another for those that don't?
Yeah, but it works under KDE+X11. Wayland it the thing that changes. I think KDE has it's own Wayland implementation? kwin_wayland is what is broken, probably. Why they broke it when porting it from X11 I don't know. But the effect is the same: Can't use it as of now.
I don't condemn the protocol. I specifically mention the buggy implementation. I say that I use X11 because KDE's Wayland implementation is so buggy.
I want to use KDE. KDE was perfect for me before Wayland. I don't criticize Wayland here, I criticize KDE Wayland. And I'm worried because very soon KDE will delete X11 support.
But you can condemn the organization and people pushing for the deprecation and abandonment of another protocol, when the alternative one (Wayland) has nowhere near the level and quality of support and breadth of capabilities as the existing one. GP puts the blame on KDE - and it would be partially their responsibility if they were to drop X11, for sure, but the underlying initiative is RedHat/IBM's.
Yeah, I still use KDE with X11 because they somehow messed up their window management with Wayland. My problems aren't even about rendering or any those features, but for some reason kwin_wayland's window management is very buggy. I'm still on 6.6 on the distribution that I use, so I don't know if it's fixed in 6.7, but I doubt it since it is here for a long time. Reported it here: https://bugs.kde.org/show_bug.cgi?id=524083
My main WM is Window Maker but i use KDE Plasma for secondary accounts when i want to try stuff without 'polluting' my main user account.
I can only use X11 with KDE Plasma because, for some unfathomable reason, if i launch `startplasma-wayland` pressing ANY key on my keyboard causes it to crash.
No (scripting) language with 2 parameter lists, the second all Var (to use the Pascal syntax). I could have included a Var keyword instead to differentiate, but a) that would complicate the variadic nature of scScript parameter lists and b) didn't quite look C-like to my eyes. (Then again I also have two Map functions in there for arrays and dicts.... so I should not claim purity.) (Yes, I stole them from LISP :-)
reply