I’ve found flatpak to have taken several design decisions that almost seem tailor made to make it hard to use. I use an app launcher as I use I3 to run apps, except I can’t use it for flatpak because it doesn’t just make stuff available on the path, I’d have to make a wrapper script or something at which point I’ve decided to use another app or package. It also had an issue where everytime I got a gpu driver update it updated every single flatpak fair enough but it kept all the old versions! It was using double digit percentage of my disk for no reason, and the response on issue for this on the repo was just this is intended behaviour.

If it wants to get mass adoption they need to work on letting it get out of the way of people trying to use it.

I’m just waiting for the inbuilt file explorer to stabilise. The only thing I miss is easy file navigation. The fuzzy searcher just isn’t what I want most of the time.

A lot of ^s. It’s like a weird dotnet dialect of c++ for interopt. I think they rebranded it to c++/cli. I mainly had to use it as a previous dev had written a large windows based app in it and I was lumbered with optimising it. (He was on the c++ standards committee so why he did this I don’t know). To be honest I have forgotten most of the details about it.

Learnt Java first, then moved on to c# and dotnet. Job meant I needed to learn c, then shudder managed c++ then plain c++. Got pretty good at c++ and then moved on to Rust and haven’t looked back, had to also pick up python recently. At some point I also learnt f# and a bit of haskell.