The modern version of Gtk and its APIs started with the switch to Cairo back in Gtk 2.8 circa 2005. While Gtk 3 and 4 have undoubtedly improved upon Gtk 2, they fundamentally still work in a similar paradigm and still have all the crust of a 20 year old library. Like most old software projects, it has some level of backwards compatibility and deprecates and adds slowly. Gtk is, like, the definition of legacy, and Qt is in a similar boat. They’re OLD old.

I personally turn back on persistent sessions and history

I did as well.

My point is just that it makes sense to be the default in that browser given its inclination towards privacy.

just philosophically it should be kinda evident that over-concentration on one corporate controlled rendering engine isn’t a good thing

Totally with you on that point.

However, I feel now that Gecko has already lost. I was a long-time FF and later Librewolf user, but Websites don’t care to support FF as much, so I’d have important sites break. I’d have to have a Chromium-based backup anyway.

So I’ve now given up on that from. I have no real choice but to use Blink in some capacity.

Right. So perhaps Librewolf isn’t a good choice for Zorin OS

Could it have been because of Librewolf?

Some issues definitiely were, but I also noticed issues when going back to regular Firefox and on Firefox mobile and Mull (which is sorta like Librewolf principles but for FF Mobile).

it was mainly because Google could afford to implement new standards faster than Mozilla could

I think that’s exactly what happens.

It definitely wasn’t Firefox’s fault for the compat issues.

Websites would work for months, and then one day only work in Chromium browsers. Sometimes they’d come back. Sometimes only parts would fail. Sometimes they’d never come back. These sites were changing things and breaking Gecko compatibility, but never Blink compatibility. I’d try turning off all the privacy settings, disabling ad blockers and extensions too, but nothing could fix it except using a Blink browser.

So I don’t blame Firefox/Librewolf for this, but it also means I suddenly couldn’t, say, access my loan payment as an example in Firefox. That’s one that broke. I need that to work. It works in Chrome, but not in FF (actually I think it came back to working in FF eventually)

I was always having to have 2 browsers installed, Firefox-based for most things and a Chromium-based backup.

One day I realize that it doesn’t make sense to use a FF-based browser, since if I have to have a Chromium-based backup anyway, I might as well just use a Chromium browser. I didn’t want to use a it, I’m generally against it Blink, but I feel that Gecko has already lost the war. I have no choice. FF is not long for this world

It has to be the default tho, bc the whole point of Librewolf is that it’s trying to by default be untraceable and private.

It’s very easy to disable that and re-enable cookies and the like, but your default experience will fundamentally be private, which is its goal

What’s wrong with Brave?

• Based on Chromium so good web support
• Decent privacy
• Built-in adblock
• Easy to customize
• Open Source

It’s the browser I’ve chosen to use after getting fed up w/ Gecko’s terrible web compatibility these days (coming from Librewolf).

What’s wrong with it? How is it evil?

Slint

I really like Slint.

It has Python bindings, tho you wouldn’t know it from the docs as it’s brand new bindings.

However, it does WORK, and it works well.

Just look for python files in the examples and reference the slint docs (it uses its own UI lang for that stuff anyway).

I’m currently making an application in Python using Slint, and I really like it.

It also supports embedded systems, the web, and multiple languages, AND since it has its own UI lang, you can reuse parts of your UI code across different codebases

It seems to suit your use case.

Godot

Other than that, I second Godot.

HOWEVER

Godot’s GD Script is not Python but rather a Python-like language. (in fact, in some ways, I’m glad it’s not; there are things I prefer in GD Script).

This is important as you may want to use specific Python libraries which won’t work with Godot!

You can, however, use GD Native to bind C++ code and thus C++ libraries, so you’ll still be able to get done whatever you need to get done.

Iced

If you’re not tied to Python, then I recommend the Rust library Iced as it is a very intuitive system. I really enjoy working with it.

Although, that said, Slint has great support for Rust, so maybe I’d recommend Slint anyway if you were gonna change language.

Warning Against Legacy

Avoid GTK, Qt, and TK at all costs imo. Also WinForms if ur on Windows.

They’re old and crusty, and their APIs suck to use, even modern versions, and despite being aged, they’re buggy still, not robust “tried-and-true” methods.

It’s also hard to do dynamic stuff with them.

Just not well designed systems. Important, valuable to know bc they’re used all over, but not well designed

Immediate

I would also try ImGUI.

It’s meant more for gamedev UIs rather than Apps themselves (tho I’ve made a couple in it)

BUT

It’s a totally different way of doing UI called “Immediate” bc you program the elements in a big loop, rather than event driven.

It’s interesting and worth trying as a learning experience

React

And ofc, the Javascript/Electron world is huge and React is very popular with lots of tools. At least read up on it.