I guess you had to be there, he has some very fun videos. His garbage time videos are a lot of fun if you like watching people mess around with shit boxes. And if you’re into drums, he has the drum thing too.
I guess if you’re boring and like watching others play games you could just play yourself. There’s hello, I’m gaming. He tries to make it more interesting but it’s gaming so.
You really should check this guy out tho. He’s heaps fun to watch!
I’m bad at naming things too🖐️
Thin clients, neat!
Greek algebra, a truth is only true if all other examples of the truth are proven true. Or one can be a part of the whole but the whole isn’t exactly the same as one.
Besides it might spoil the relationship with your local NSA agent.
This whole argument ignores xwayland and the fact that new features are added as a standard of Wayland literally every day.
For as long as xwayland is supported you can use your old apps. Wayland actually supports different window icons for multi window apps. But Wayland has always supported window icons, kde just had an annoying bug they finally fixed. Chromium and electron apps kinda just didn’t support window icons very well in wayland for a while.
For accessibility, it’s been broken on Linux for literally years but there’s an active effort to make it better and more universal than it ever could have been on x11. The effort of building a fully featured accessibility stack is being led by the gnome team with help from the free desktop organization and kde.
This is my last response, this conversation isn’t going anywhere anyway. I’m not the one transitioning the Linux world to Wayland, I don’t see why you could blame me for it anyhow.
Your arguments kinda weak, no offense. I do have a solution for you though. If you want to stick with a version of Linux that’s guaranteed to support xorg for eight years, I’d recommend Rocky linux! When that reaches EOL I guess you could just stay on it.
Enterprise plans on being fully switched over to Wayland by the next major version. You won’t be able to install xorg on redhat for example. The biggest contributors to xorg(Enterprise) are going to shift focus to xwayland to support legacy software on wayland.
Besides it’s exciting finally catching up to truly hardware accelerated desktops like Mac OS 10.0 and windows vista. At its heart xorg is a purely single threaded software accelerated bitmap based windowing system from 84. They’ve had to rewrite small but incredibly complex chunks of the code just to try to keep up with the modern world. Just look at the history of 3D acceleration in x11.
Your free to give it a good go though! The very same team that actively maintained xorg threw in the towel ten years ago when they diverted resources towards a new windowing protocol and they’re not going back.
If developers drop off there’s not much we can do. It’ll eventually have to be removed or become a bigger security risk than developers say it is already.
Support on the x server itself has dropped off precipitously since Wayland hit the mainstream and most small x11 DEs are trying to build off of WM like wayfire or wlroots.
I don’t think kde plasma was the only one. Anyway, it just feels natural for xwayland to stop pushing for feature parody and for focus to switch over to Wayland after a while.
The biggest target for developers is the Ubuntu/Debian platform so their switch to Wayland should motivate other projects and paid applications to at least take notice.
New projects will try to support both but typically will focus more on Wayland. There’s already an unintentional incentive to partially support xdg protocols Wayland relies on thanks to flatpak.
They’re already starting to go that way, in a couple years Linux mint is even going to support Wayland. Ubuntu and fedora has already defaulted to Wayland. Fedora is actually deprecating xorg in a few releases. Budgie wants to have full support next year.
There isn’t much more than the testing they already have to do every release. Infact not having to support legacy code will free up resources for the whole Linux community as well as cutting the time in half for validating packages on distros. Every package that runs on xorg also runs on wayland, they have to test both.
Granted some have custom tools they’ll be working on but it’s going to be a while before every major DE supports Wayland. I’m curious, you think the distros have to implement their own version of Wayland?
Once the desktops switch to Wayland and all distros ship with Wayland by default, support should slow.
Ideally, developers stop improving xwayland over time and go into maintenance mode for a bit. Once it goes into maintenance mode, developers should naturally fall off as it winds down.
If every desktop makes a very public announcement about the xwayland protocol being put into maintenance mode, actively supported apps should switch over. It’s up to the public how long they want to keep maintaining xwayland (open source etc).
Still learning, they just covered compiler flags in cs. They didn’t go into detail yet though.
Edit: I’ve used python for years and they have something equally dumb. You can have a function in a massive application that is broken and the moment it’s called, the application crashes.
At any other point the application will just run as if nothing is wrong even though python evaluates everything at runtime. I’m sure they can’t do much because the initial launch would be slow.
For a second there I thought you were hating on the guy.
sudo pacman -Syu --needed cups system-config-printer avahi nss-mdns foomatic-{db,db-{engine, nonfree}}
sudo systemctl enable --now cups.socket avahi-daemon.service
Rebooting after helps if it doesn’t find the printer right away.
Yeah, they could puppet the chrome company if the courts don’t keep a close eye on it. Basically there’s a good chance it would be another Firefox but with way more influence.
Isn’t it already licensed under permissive Apache v2? Anyone can fork and carry on the project without the permission of Google, every manufacturer already does as a result of the license.
Machine code would be a better example of what he’s talking about imo. Not an expert or anything of course.
It wouldn’t be that much processing compared to the rest of the app. It would lot more efficient than running an effectively infinite loop or arithmetic on an arbitrarily large number as a result of an unsigned variables.
What are you talking about? Microsoft is charging for HEIF, HEIC, and looking to do it with AV1 and AVIF. Intel started development of EFI in the titanium days as a new standard for servers running unix before it became an open standard. Microsoft wasn’t the only one involved in the standard but apple, redhat, hp, Intel, amd, and a laundry list of hardware/software manufacturers.
Most all the innovation happens in enterprise space with servers running unix/Linux. User operating systems are an afterthought when these features are initially conceived.