QT is a cross platform UI development framework, its goal is to look native to the platform it operates on. This video by a linux maintainer from 2014 explains its benefits over GTK, its a fun video and I don’t think the issues have really changed.

Most GTK advocates will argue QT is developed by Trolltech and isn’t GPL licensed so could go closed source! This argument seems to ignore open source projects use the Open Source releases of QT and if Trolltech did close source then the last open source would be maintained (much like GTK).

Personally I would avoid Flutter on the grounds its a Google owned library and Google have the attention span of a toddler.

Not helping that assessment is Google let go of the Fuschia team (which Flutter was being developed for) and seems to have let go a lot of Flutter developers.

Personally I hate web frontends as local applications. They integrate poorly on the desktop and often the JS engine has weird memory leaks

Every big UK company I have worked for doesn’t own its building. They will typically agree to rent a building for 5-20 years at a fixed rate (longer times if its being purpose built for them) .

So I would expect this is paying out the rest of the rental agreements for a building to escape the building lease.

It is to do with financial reporting and the way asset and operational costs are reported.

Immutable distributions won’t solve the problem.

You have 3 types of testing unit (descrete part of code), integration (how a software piece works with others) and system testing (e.g. the software running in its environment). Modern software development has build chains to simplify testing all 3 levels.

Debian’s change freeze effectively puts a known state of software through system testing. The downside its effecitvely ‘free play’ testing of the software so it requires a big pool of users and a lot of time to be effective. This means software in debian can use releases up to 3 years old.

Something like Fedora relies on the test packs built into the open source software, the issue here is testing in open source world is really variable in quality. So somethinng like Fedora can pull down broken code that passes its tests and compiles.

The immutable concept is about testing a core set of utilities so you can run the containers of software on top. You haven’t stopped the code in the containers being released with bugs or breaking changes you’ve just given yourself a means to back out of it. It’s a band aid to the actual problem.

The solution is to look at core parts of the software stack and look to improve the test infrastructure, phoronix manages to run the latest Kernel’s on various types of hardware for benchmarking, why hasn’t the Linux foundation set up a computing hall to compile and run system level testing for staged changes?

Similarly website’s are largely developed with all 3 levels of testing, using things like Jest/Mocha/etc… for Unit/Integration testing and Robots/Cypress/Selenium/Storybook/etc… for system testing. While GTK and KDE apps all have unit/integration tests where are the system level test frameworks?

All this is kinda boring while ‘containers!’ is exciting new technology

Docker swarm was an idea worse than kubernetes, that came out after kubernetes, that isn’t really supported by anyone.

Kubernetes has the concept of a storage layer, you create a volume and can then mount the volume into the docker image. The volume is then accessible to the docker image regardless of where it is running.

There is also a difference between a volume for a deployment and a statefulset, since one is supposed to hold the application state and one is supposed to be transient.

The splash screen (boot screen instead of text)used to get me. It provided by an application called ‘Plymouth’.

You used to need to install it and configure grub, however I think if you go into ‘System Settings’ and type ‘Splash’ KDE has an option to install and choose the screen

Pirate Trainer & Uru: Ages Beyond Myst

I remember trying Pirate Trainer in a Nvidia game booth when VR was new. It was incredible, years later I get a VR headset and its the free game. I don’t understand how no one has improved upon it.

Uru was the first puzzle game I thought struck a good balance between physical and mental puzzles. They were set at a level that felt challenging but not impossible and laid out so you alternated really nicely. Myst Online actually went backwards in this

Removed by mod

I wouldn’t use “certified” in this context.

Limiting support of software to specific software configurations makes sense.

Its stuff like Debian might be using Python 3.8 Ubuntu Python 3.9, OpenSuse Python 3.9, etc… Your application might use a Python 3.9 requiring library and act odd on 3.8 but fine on 3.7, etc… so only supporting X distributions let you make the test/QA process sane.

This is also why Docker/Flatpack exist since you can define all of this.

However the normal mix is RHEL/Suse/Ubuntu because those target businesses and your target market will most likely be running one.

I suspect they mean around packaging.

I honestly believe Red Hat has a policy that everything should pull in Gnome. I have had headless RHEL installs and half the CLI tools require Gnome Keyring (even if they don’t deal with secrets or store any). Back in RHEL 7, Kate the KDE based Text Editor pulled in a bunch of GTK dependencies somehow.

Certification is really someone paid to go through a process and so its designed so they pass.

Think about the people you know who are Agile/Cloud/whatever certified and how all it means is they have learnt the basic examples.

Its no different when a business gets certified.

The only reason people care is because they can point to the cert if it all goes wrong

Debian isn’t old == stable, its tested == stable.

Debian has an effective Rolling distribution through testing than can get ahead of Arch.

At some point they freeze the software versions in testing and look for Release Critical and Major bugs. Once they have shaken everything and submitted fixes where possible. It then becomes stable.

The idea is people have tested a set baseline of software and there are no known major bugs.

For the 4-5 releases Debian has released every 2 years (Similar to Ubuntu LTS). Debian tends to align its release with LTS Kernel and Mesa releases so there have been times the latest stable is running newer versions than Ubuntu and the newest software crown switches between Ubuntu LTS and Debian each year.

For some the priority to run software that won’t have major bugs, that is what Debian, Ubuntu LTS and RHEL offer.