- 0 Posts
- 33 Comments
122·3 months agoThe main reason is that Dbus is not available during early stages of boot. There are many others.
Varlink seems to be better or the same compared to dbus in all except two things:
- json doesn’t handle 64bit integers, it handles 52bit (or 54bit?) (size of mantissa for floats)
- you cannot (yet) list all things connected to the bus
Details here:
There are some really nice designs here. I really hope that KDE finally gets to pay attention to this. I love simplification of it.
One thing I don’t like here is the login screen. There is too much stuff on it. I think gnome’s login screen, as it is now, is fantastic.
And one more thing, proposal for mindset change: not everything has to be a widget. Some things (like shell) could have layouts: layout as current plasma/windows, layout as gnome, layout as Mac, layout as Win8… If things get well thought out, you can integrate this and switch layouts and not di*k around with widgets. Less moving parts, less problems.
4·3 months agoDidn’t they discover them years ago at the garbage dump in Japan?
171·3 months agoOne Real As*hole Called Larry Ellison
It’s probably a discussion for allowing Ukraine to do what they want with long range weapons.
Russia has made pretty direct statements about what happens then - they will consider NATO to be in direct war with Russia.
I think this number is overblown. Production useful doesn’t have to mean 1:1.
Running it without all graphics drivers would be fine for server use. Also, not all filesystems need to be ported: basic ones should be enough for start. But not only servers, home routers run Linux kernel…
If every OEM starts contributing their drivers in rust, this could move quickly…
Who was the guy that had a lot of pauses with mmmmmm when talking?
Why would they put effort into changing something which works for them with the risk of breaking things?
The sentiment is similar to climate change deniers. Why would we stop with fossil fuels when they work, people have jobs, etc. And why would we risk breaking the power grid?
And as long as that works for them, they won’t actively change anything.
Wayland on gnome and Ubuntu is already the default. It seems to me you have to actively change the default to x.
It would be interesting to see in which scenario x is better than wayland. The only reason I can think of is an (old) Nvidia card. With new Nvidia’s I guess the statement would otherwise be ‘i will not use it until they fix Wayland’
Depends on the timeline.
X crashed way more for me on kde than Wayland on gnome. ‘Never’ is quite the statement.
Right. And I’m interested if there are some legitimate needs for you to run x until it stops working.
Or is this just a revolt?
Why would someone stay with x even though it’s deprecated, architecturally broken and unmaintainable
Until I cannot run software on X11, I won’t switch over knowingly.
Please explain
Interesting, thanks
What about quad9? Do they log queries?
16·6 months agoPeople don’t really love chrome, but they do love meat. Go vegan suggests we get rid of something we love.
Oh, so it basically displays a remote window manager in the browser? For a moment, I thought it was running the compositor directly inside the browser with extensions or something like that, hahaha.
I saw it basically months ago, so don’t remember 100%. To not say the wrong thing, you can read about the architecture here: https://greenfield.app/pages/design/
Also, here is a video. The dev demonstrated it’s fast enough for gaming https://fosdem.org/2024/schedule/event/fosdem-2024-3219-greenfield-wayland-in-the-browser-an-update/
I agree, all the apps I use run natively on Wayland, but I think there will always be some legacy X11 apps that won’t get ported. So, I think I’ll implement it, but it is definitely not a priority.
While I understand the need for legacy, I also think at some point legacy should be left alone. If it is really needed for some old app to run, VM should do fine. I don’t think missing xorg is ever going to be an issue in 2025+ (well, Electron apps maybe). Yet added and not used features (or seldom used features) is offset with future maintenance burden and/or security issues for no good reason.
This also applies to OpenGL comment. Every code path introduces a maintenance burden. While support of more devices is good, supported devices are super old in this case and the question is - is it worth it? Vulkan drivers should either way be in a better state.
Looks very interesting! I wonder how it works, so I definitely will check it out.
Is super cool, there is a presentation in one of the conferences about it. Architecture is explained somewhere in the docs. Anyway, if you do implement it - this would be a good alternative to https://guacamole.apache.org
Who knows, maybe it would be a money opportunity.
Why?
It’s not Microsoft, but actually an open source community running open source forge. Also, it’s way faster to use in browser.
HP: you are not going to get fired. You will quit.