nexussapphire @ nexussapphire @lemm.ee

Posts

2

Comments

823

Joined

2 yr. ago

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).

Lucky, my dog is gluten intolerant. It's not fun cleaning out his fur.

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.

It was the only way I could tell how much time is left, I didn't have a phone till highschool. In school counting down the second till school was over was so crucial.

You never watched the braindead slop TV in GTA IV and GTA V. The satire in GTA games is just so funny, especially for an American that deal with dumb politics and social intercourse.

For a second there I thought you were hating on the guy.

His profile name makes me think of something you'd see on GTA TV.

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

Edit nss-mdns

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.

If it's going to compile without any warnings I'd rather the app crash rather than continue execution with rogue values as it does now.

There is so much room for things like corrupted files or undocumented behavior until it crashes. Without the compiler babysitting you it's a lot easier to find broken variables when they don't point to garbage.

I forgot to assign a variable, now it crashes %5 of the time. It's wild how c doesn't default variables to null or something.

How do you pay for car insurance or renters insurance? It's not too dissimilar to that.

Though, I've moved to a state that has deemed me poor enough to give me Medicaid so the taxpayers pay for mine weather I want it or not. It beats paying almost $800 because living with my mother disqualifies me from the affordable care act subsidy.

I do appreciate it, I know I'm no idiot.

To be honest, I kinda wish some projects came with API manuals. I understand it's not a priority in an open source project with limited resources.

It would be nice to use a python based ml tool without passing commands through it via shell. People do it, I just don't have the time or experience to analyze a complex project like ML voice synthesis.

So you're saying it should wick the water from the cup to the table like an oil lantern. That seems like a good way to have half of your cup on the table.😂

If you get it to travel up the string, gravity will definitely do the rest. It seems like such a passive aggressive way to design a product and I'm all for it.