> Oh, its good at doing desktop applications these days? Which GUI libraries are good these days? Some native win32 binding? Are there good equivalents for Qt?
If your goal is "delivering applications to only well-sighted people who can handle non-native and buggy UI", yes iced, EGUI, gpui exist. But as you can guess they are years behind Qt where you have quite the professional toolkit and properly implemented accessibility features (with a lot of bugs and horrible API because Qt).
The only foolproof way of having truly professional software is still the same: have N different, very-well integrated UI implementations (like Adobe does, $$$ in developer or agent fees) or use a Web browser aka Electron.
With Rust you can use Win32 or WinUI3. Both are provided by Microsoft-developed crate windows-rs.
I'm using LineageOS so I have the AOSP Phone app. If Graphene uses the same, then you can actually determine the exact time of call, but you need to jump through a couple of hoops: Go to "Call History" from the three dots then click on the call of interest. You'll see a button called "Call Details". Then you can see the exact time.
Rust's async can be very lightweight depending on the runtime implementation. tokio and embassy are both runtimes but former is a throughput-optimized heavily multi-threaded while latter is a simple cooperative multitasking for embedded. We use both at my day job. Even 64k flash and 16k ram is enough for embassy.
EU isn't a single identity. Usually overt displays of nationalism is frowned upon in Europe, especially in Germany. Moreover I have a strong guess that if there would be a flag, it would be the Bavarian one for a company called "Isar".
EU is a single well defined entity, the frowned upon flags are the German flags, EU flags are well tolerated especially in international settings.
For example the first electric plane that recently flew was originally European until last year and they had an EU flag on it. When eventually flew in USA they had the US flag.
Yeah let's start on a specific version that they overhauled the API since computers are getting new hardware features, god forbid a different DPI. And use that as a leverage point against a library that kept their API quite stable for the last 20 years!
Especially when comparing Qt against a library who couldn't keep its shit together for 5 years and is infamous for breaking all sorts of API and removing features.
> since computers are getting new hardware features
It's not possible to move forwards fast anywhere.
> and removing features
Yeah, this is indeed very unfortunate. They claim the GTK core team is about 2 devs, so tiny that we're lucky the development goes further at all. Hard to understand considering Red Hat became part of IBM.
There are more layers, if you'd like to look into it.
- Web developers don't support older browsers because they lack the skill and economic motivation for it.
- The managers of web developers will not support them, because there is no money to be made in supporting older browsers. Nor are there career benefits in maintenance projects. No developer or manager will get promotions for it.
- The actual management of the companies will not promote or compensate engineering managers or developers for maintenance projects since it doesn't contribute to "line goes up"-economics.
If 99.9999% is on WWW, nobody will move to Gemini. There is no business to build on Gemini, no publicly accessible, culturally broad community exists on it and none will exist. You'll only find programmers on Gemini. No authors, philosophers, non-IT engineers/makers with their projects. WWW has organically grown. Gemini has to be equally or more capable and more user and business friendly to have a significant contributor base.
But seriously, web is asymptotically approaching zero usefulness precisely because of all those "capabilities". In those circumstances, can't you see a million nerds muttering "we'll build our own interweb! with blackjack and hookers!" And one of them might even get lucky, and get a tipping point. Gemini's just an example.
I don't think web's ever going away for corporate stuff, but I can imagine the cultural party moving next door, to a less capable protocol.
It's like Reddit and Lemmy. The majority of users did not switch to Lemmy but the ones that did seem to engage more and share cooler stuff. They are there on purpose, not because it's the default platform.
This is the most insane cope. The old web was good because a naive user could find the coolest thing imaginable. The naive user isn't digging into a forum, finding a reference to a niche forum from the other forum, figuring out how to install or access it, and then actively engaging in it. People don't know passwords can have spaces now.
For a browser, that's not really possible without a significant team of over-the-average and paid developers. There are a lot of complexities in a browser. It has to have its own GPU driver, JIT compiler, optimized scheduler to pull page components, another scheduler to run JS, a cross-platform rendering abstraction, hacks for 30+ years of WWW. All of that should be fast. Because everything else is extremely slow and wasteful on Web.
People who can handle this complexity are extremely mobile in the industry. They can always find employment in a much better paying place than Mozilla. And a competitive browser has to have such developers on generous payroll.
One of the issues with Firefox is its codebase. Some parts of it are slowly rotting and it has its own fair share of 20-year-old bugs. Mozilla is slowly failing to keep up with the ever changing landscape and dealing with the age of their codebase. There is a reason why Electron could be developed with Chromium but not Firefox. Mozilla really tried this as well, it just didn't work.
If you're forking, Chromium or Safari are a better start point than Firefox.
How so? Firefox isn't a small, raggedy development project. Mozilla developers are well-paid and Mozilla has offices in a premium location and it can afford paying millions to their CEO, despite losing significant marketshare.
If your goal is "delivering applications to only well-sighted people who can handle non-native and buggy UI", yes iced, EGUI, gpui exist. But as you can guess they are years behind Qt where you have quite the professional toolkit and properly implemented accessibility features (with a lot of bugs and horrible API because Qt).
The only foolproof way of having truly professional software is still the same: have N different, very-well integrated UI implementations (like Adobe does, $$$ in developer or agent fees) or use a Web browser aka Electron.
With Rust you can use Win32 or WinUI3. Both are provided by Microsoft-developed crate windows-rs.
reply