Pulseaudio was introduced in 2004. How come it took almost 20y for it to be replaced if it was that bad?

Implementation, being what it is, improved the situation compared to alsa and other things before it. Again, while not perfect it made things better for everyone.

It’s funny that this is a thing attributed to poettering as bad since things before were way worse… why not throw Sticks and stones at those people?

I really don’t get it.

And all of these things are optional. The fact that distro people and companies select them is because they solve real world problems.

People are idiots.

Poettering got death threats for systemd.

Is it really breaking it? As far as I’m aware, it’s more like gnu. It has components and you can select what you use (here meaning distros and packagers).

People mistake this for a monolith because it’s all named systemd-thing. Integration, like you said, was and is needed. But what if all those separate utilities and services are actually disconnected and speak some protocol different to pipe? Does it make it less unixy?

And poettering is an absolute good guy here. Pulseaudio wasn’t perfect, but did it improve things compared to what was there before? Sure it did. Even now, pulesaudio protocol is used within pipewire and it works just fine.

Perfect is the enemy of good. And while all these tools might not be perfect, they are the best in the Linux world.

This is the key to a painless transition.

1. Dual boot should be ok. If and when you decide to fully switch, I’d say it’s better to do a reinstall. Messing with partitions always comes with disclaimers. A bit advanced topic if you are interested: when you resize partition usually data needs to be moved, depending what you do with it, so it will wear your ssd; also you should be aware that you must install windows first, Linux second because windows doesn’t really play well with others and be sure NOT to format EFI partition when installing Linux.

You have alternatives to dual boot: VMs. Run Linux on bare metal, then boot up a VM if you need something only windows can provide. Gnome has a new VM tool incoming.

2. No idea for audio, but Photoshop has alternative, gimp. Wether you like it or not, it’s another story (people I know really really hate that one). For digital art there is a tool called Krita that runs on kde. People really enjoy using it.

3. NTFS has one thing that Linux doesn’t really like - it is case insensitive. Linux normally works with case sensitive filesystems. There was recently a rant by the Linux overlord about case insensitive filesystems, so you might want to stay clear of it. It’s ok to use it on a thumb drive though.

Edit: minor typing fixes

Just one: Bing wallpaper

The question is if they will close that 15-20y gap in 3-5y

Not that I’m using them, but what about these two?

https://www.truenas.com/truenas-scale/

https://www.proxmox.com/en/

Look for an error in the journal as soon as the error you mentioned happens. Maybe some details get saved in the journal. Post it somewhere online like pastebin, then we can maybe tell you what to check next

Like others have said, what you are experiencing is super unusual

Like @wildbus8979@sh.itjust.works just said, run memory test.

What hw do you have in that laptop?

something went wrong, but we’re not sure what it is.

Check the system journal with

sudo journalctl -e

HP: you are not going to get fired. You will quit.

The 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:

https://media.ccc.de/v/all-systems-go-2024-276-varlink-now-

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

Maybe check how long it is already going, so it can give you some confidence. Forgejo is a fork of gitea, which is a fork of gogs.

Also, codeberg, a nonprofit from Germany, is supporting development.

https://docs.codeberg.org/getting-started/what-is-codeberg/

The codebase history of Forgejo and its predecessors predates Codeberg. However, since 2022, Codeberg is backing the development of Forgejo as an umbrella organization.