Vik

Huh, so the onboard power play was unstable? Which model GPU was this with?

they’re just little bulbasaurs charging up their solar beam

suse is neat 🥰

habibi I’m afraid I’ve not had good experiences with manjaro, I may need to defer to someone else in this thread. tumbleweed is cool as heck though.

I’d personally stick to fedora?

This may be at odds with stability somewhat being rolling release, but you may want to check out SUSE tumbleweed or EndeavourOS. You already have a solid pick based on your established requirements.

Couldn’t hurt to poke around other offerings in a VM, though

Yeah, they’re vastly different approaches, and despite my admittedly petty complaints, I’m eternally grateful for both; to me it feels as if both GNOME and KDE in some way cater to the creature comforts of MacOS and Windows respectively, and for end users hopefully moving on from both of those environments.

I find both KDE Plasma and GNOME can be made into serviceable experiences with enough time, and given the nature of FOSS and such, automating this as part of a custom deployment is a fairly trivial task in 2025 😊

I use this on specific systems but plasma’s information architecture (namely within the settings area) is bizarre to me. Yes you can search. No you shouldn’t have to resort to that.

I’m not keen on the little ‘K name everything’ in joke either, though thankfully you can rename desktop shortcuts to whatever you’d like there.

I can appreciate that people use their systems very differently, but this is something that gnomes designers did not care to acknowledge throughout that whole exchange; input directly from their end users, and that’s bearing in mind they collect no telemetry.

I appreciate working in UX for a community driven project is no easy task, many of the people commenting in the thread linked above could be considered more advanced users with their own desktop shortcuts configured, and a one size fits all approach satisfying all is difficult to deliver. All they asked for was an option for this new behaviour.

The communication in that thread was so poor that matt miller got involved.

I gather the DE is supposed to stay out of your way, but it feels like a bandaid for another poor design decision when you frame it like that.

And in addition, no other desktop environment feels the need prompt the user to open or search for something from the get go.

On default gnome, you still have a hot corner in the upper left, and the dash along the bottom edge of the screen and I’m not sure I get that either.

Dash to panel, no overview at login, kstatus / appindicator tray icon support and gsconnect

The no overview at login story highlighted the sheer hubris of the gnome design team. Wild ride.

Haven’t run the comparison on NV33 versus 44, but if find the 5060 series kind of interesting given the area and transistor count increases relative to ada lovelace.

33 was a full node behind and priced high for what it was (even if BOM was mostly in-line).

I wouldn’t be surprised if something like that was the case. Could have been that the successive work was negotiated with khronos & lunarg before the final name was chosen.

Yup, derived from a point in time where Vulkan was seen as a direct successor to OpenGL.

I suppose credit where due, AMD did kind of put an end to mantle, and give that over to the Khronos group to later become Vulkan. XGL as the UMD reference may predate the name Vulkan altogether.

As far as I’m aware, the RadeonSI driver was built internally, whilst RADV was an external effort.

The focus was on AMDVLK as it’s similar in design to the XGL windows vulkan driver

Is it not being recognised as a usable device?

E: nvm, just realised hw accel support in kdenlive is experimental

life is good

I appreciate the analogy

It’s a shame that consumer oriented TR ended with the 3000 series. Platform owners must have felt massively short changed by that (my friends and associates with 2 and 3000 series TRX rigs certainly did)

aye she’s a lil pumpkin