LeFantome

joined 1 year ago
[–] LeFantome@programming.dev 25 points 7 months ago (11 children)

History tells us that 85% of these people will move to Windows 11 despite what they say.

There is a real opportunity here for companies though.

  1. Move employees to Office 365 online today ( see how many truly need the desktop apps )

  2. Start moving early adopters to Linux ( still using Office 365 online )

  3. Work to identify and replace any other software that is Windows only

  4. When Windows 10 goes end-of-support, move everybody else to Linux

The few that really need Excel desktop could probably run it in a VM or via a virtual desktop ( thin client ).

You could probably stop there. Honestly, I doubt it would even bother Microsoft that much. Office and Azure is the business now.

From there, you could try to advance further if you want.

  1. Move early adopters off Office 365

  2. Drop Office 365

Honestly though, for many companies, you could almost get Office 365 for free just be combining it with your Azure spend and getting a discount.

[–] LeFantome@programming.dev 4 points 7 months ago

Wrinkly Waterbear

[–] LeFantome@programming.dev 5 points 7 months ago* (last edited 7 months ago)

24.04 is an LTS release.

This is a beta of 24.04.

The “name” of the release is “24.04 LTS” ( a perfectly reasonable name that communicates its intent ).

Therefore, this is the “24.04 LTS” beta.

Pretty clear to anybody familiar with the Ubuntu product line.

[–] LeFantome@programming.dev 4 points 7 months ago* (last edited 7 months ago)

I totally agree. They have taken one of the best features of Ubuntu ( the meaningful and easy to understand versioning ) and thrown it in the garbage ).

I have no idea what the code name is for Ubuntu 18.04 or 26.04 but I can tell you when both of them were released.

Using the code names in sources.list is insanity.

[–] LeFantome@programming.dev 6 points 7 months ago

Those are different steps in the Ubuntu release process.

[–] LeFantome@programming.dev 1 points 7 months ago* (last edited 7 months ago)

It is complex to build a Wayland compositor. When none existed, you had to build your own. So it took quite a while for even big projects like GNOME and KDE to work through it.

At this stage, there are already options to build a compositor using a library where most of the hard stuff is done for you.

https://github.com/swaywm/wlroots

https://github.com/CuarzoSoftware/Louvre

There will be more. It will not be long before creating Wayland compositors is easy, even for small projects.

As more and more compositors appear, it will also become more common just to fork an existing compositor and innovate on top.

One of the longer term benefits of the Wayland approach is that the truly ambitious projects have the freedom to take on more of the stack and innovate more completely. There will almost certainly be more innovation under Wayland.

All of this ecosystem stuff takes time. We are getting there. Wayland will be the daily desktop for pretty much all Linux users ( by percentage ) by the end of this year. In terms of new and exciting stuff, things should be getting pretty interesting in the next two years.

[–] LeFantome@programming.dev 1 points 7 months ago

Cool. So Hurd-NG is moving a bit faster than the original!

[–] LeFantome@programming.dev 3 points 7 months ago

If you want a browser truly written “from scratch”, you need to check-out Ladybird:

https://ladybird.dev/

[–] LeFantome@programming.dev 2 points 7 months ago* (last edited 7 months ago)

NUKE

https://www.foundry.com/products/nuke-family/nuke

Also, while a bit of a surprise, FLTK is migrating to Wayland.

[–] LeFantome@programming.dev 1 points 7 months ago (1 children)

Are you aware of macOS? Because it is still built with the same UI tools that you mention.

[–] LeFantome@programming.dev 17 points 7 months ago (1 children)

I do not want to fight and say you misunderstood. Let’s just say you have been very influenced by one perspective.

Wayland has taken a while to fully flesh out. Part of that has been delay by the original designers not wanting to compromise their vision. Most of it is just the time it takes to replace something mature ( X11 is 40 years old ). A lot of what feels like Wayland problems actually stem from applications not migrating yet.

While there are things yet to do, the design of Wayland is proving itself to be better fundamentally. There are already things Wayland can do that X11 likely never will ( like HDR ). Wayland is significantly more secure.

At this point, Wayland is either good enough or even superior for many people. It does not yet work perfectly for NVIDIA users which has more to do with NVIDIA’s choices than Wayland. Thankfully, it seems the biggest issues have been addressed and will come together around May.

The desktop environments and toolkits used in the most popular distros default to Wayland anlready and will be Wayland only soon. Pretty much all the second tier desktop environments have plans to get to Wayland.

We will exit 2024 with almost all distros using Wayland and the majority of users enjoying Wayland without issue.

X11 is going to be around for a long time but, on Linux, almost nobody will run it directly by 2026.

Wayland is hardly the Hubble.

[–] LeFantome@programming.dev 39 points 7 months ago (2 children)

Linux does this all the time.

ALSA -> Pulse -> Pipewire

Xorg -> Wayland

GNOME 2 -> GNOME 3

Every window manager, compositor, and DE

GIMP 2 -> GIMP 3

SysV init -> SystemD

OpenSSL -> BoringSSL

Twenty different kinds of package manager

Many shifts in popular software

view more: ‹ prev next ›