News for hackers. Stuff that matters.
Re:Are we GUI Yet? The state of building user interfaces in ... by qwerty456127 on Friday July 09, 2021 @08:22AM (#27782926)
I have switched half back to Windows (after a decade of 100% Linux) recently just because I finally accepted there is no way of making GUI apps as a single developer nearly as easy and pleasant as WinForms with VisualStudio. The result is virtually Windows-only (it can run on Mono but there are some quirks) but it feels worth that sacrifice.
Re:Are we GUI Yet? The state of building user interfaces in ... by badsectoracula on Friday July 09, 2021 @01:07PM (#27785900)
> nearly as easy and pleasant as WinForms with VisualStudio

Check out Lazarus: http://lazarus-ide.org

It is WAY easier than WinForms. WinForms' VS "integration" feels as if they started with what Delphi 1 could do back in 1995 or so, implemented most of it and then decided that is enough.

Lazarus' GUI tools are way above and beyond anything WinForms can do and the underlying LCL is crossplatform using native widgets wherever possible with backends for Win32, Gtk1/Gtk2/Gtk3 (though Gtk2 might be the best ATM), Qt4/Qt5, Cocoa and a few others (Carbon, fpGUI and some Amiga toolkit).

Here is a video from 3 years ago where i make a simple sliding image puzzle game under Linux using it:

https://www.youtube.com/watch?v=s_01Xhd2EJM

Also here is another video from 6 years ago where i make a 2D tilemap editor in Windows:

https://www.youtube.com/watch?v=_3JgeIUo1X0

And another video from ~10 years ago making a doodle app:

https://www.youtube.com/watch?v=nZuddi3zR_0

Re:Are we GUI Yet? The state of building user interfaces in ... by qwerty456127 on Friday July 09, 2021 @06:50PM (#27789413)
Pascal seems a way too vintage programming language (not nearly as handy as C#, let alone C# 5.0) and the IDE's editor isn't nearly as intelligent as that of VisualStudio (let alone with ReSharper). But it indeed seems the only of the kind truly cross-platform. The only close-enough alternative I found on Linux was QtDesigner+Python but it still wasn't that convenient.

I adore people who code Lazarus (e.g. Double Commander authors - they have been doing an amazing job with visible progress and persistence all these years) though. Perhaps I'm going to dedicate some time to learn Pascal once, just for this. It would be easier if they had a seamlessly-compatible C++ version at least (like Delphi had).

Re:Are we GUI Yet? The state of building user interfaces in ... by badsectoracula on Wednesday July 14, 2021 @01:33AM (#27830017)
Keep in mind that Free Pascal is not exactly the same as classic Pascal. The language has a lot of features you'd find in other modern (as much as Java and C# can be called modern nowadays anyway) object oriented languages. Things like classes, interfaces, dynamic message dispatch, properties with getters/setters, for with ranges, dynamic arrays, generics, a rich RTTI (though not as rich as managed languages - yet, it is work in progress - it is rich enough to do things like serialization, etc), etc.

As for a C++ version, it would be useful (though i find Free Pascal a better language overall, despite its warts - the only thing i wish it had from C++ was 'const' and slightly more powerful generics, but both aren't that big of an issue and generics are improving anyway) but VERY difficult to do as i wrote some time ago here [0] and here [1] where i went into more details about the language side of things (C++ Builder has extended C++ to allow for Object Pascal-isms because VCL itself is written, like LCL/FCL, in Pascal, which for Borland was possible because they made both the Pascal and the C++ compilers).

[0] https://news.ycombinator.com/item?id=15893362

[1] https://news.ycombinator.com/item?id=19882489 (note that the discussion was originally about using LCL from C++ so i also mention the alternatives - and how not having the rest of the IDE would end up with a worse wxWidgets since LCL isn't really designed to be used purely via code)

Re:Are we GUI Yet? The state of building user interfaces in ... by Blaiz0r on Friday July 09, 2021 @08:58AM (#27783210)
Thats' a shame, and definitely something that the Linux ecosystem needs to address.
Re:Are we GUI Yet? The state of building user interfaces in ... by pjmlp on Friday July 09, 2021 @09:32AM (#27783481)
I lost any hope when GNOME developers decided to kill Glade and started suggesting that developers should code raw .ui files directly.

https://blogs.gnome.org/christopherdavis/2020/11/19/glade-no...

Thankfully KDE is still around, but many seem to not appreciate the UI design tooling provided by Qt, because $$$$.

So I rather waste my time on Earth on platforms that value good UI/UX tooling.

Re:Are we GUI Yet? The state of building user interfaces in ... by _d7dt on Friday July 09, 2021 @09:40AM (#27783545)
Please don't assume bad faith. Glade was not "killed," there are technical reasons why Glade cannot be used for GTK4 (I can give more detail if you want). There is currently a new tool being developed by a Glade maintainer, catch this guadec talk later this month if you want to know more: https://events.gnome.org/event/9/contributions/191/

Nobody is particularly happy about having to edit the XML directly but it's the best option right now until the new tools stabilize.

Re:Are we GUI Yet? The state of building user interfaces in ... by mumblemumble on Friday July 09, 2021 @10:21AM (#27783937)
I think that this might speak to the deeper problem that a lot of people have experienced with GTK: stability. The project isn't a huge well-funded company with lots of vendor-lock in like Microsoft is; it can't afford to be rethinking how the GUI toolkit should work every few years like Microsoft does. (Or continuing to support and maintain all the old no-longer-favored GUI frameworks like Microsoft does.)

It's great that GTK4 has decided to commit to API stability, but, at this point, it may be too little, too late as far as the project's reputation among many developers is concerned. Having to lose a venerable tool like Glade to get to the API-stable version doesn't exactly take the edge off.

Re:Are we GUI Yet? The state of building user interfaces in ... by _d7dt on Friday July 09, 2021 @10:25AM (#27783975)
I've posted about this before, but if you want GTK and you believe API stability is the most important thing then you should just use GTK3. The API there is frozen. I'm not sure what "reputation" you're referring to but if GTK does not meet your needs, and Qt (or something else) does, then I think that's great for you, you should just use that.
Re:Are we GUI Yet? The state of building user interfaces in ... by entropy1111 on Friday July 09, 2021 @04:58PM (#27788413)
GNOME being slow and not having basic features like thumbnails in the file picker after almost 18 years was often attributed, by their maintainers, to be caused by GTK3 limitations. Even now Glade still needs a lot of "volunteering" to be production ready for GTK3. I don't use GTK anymore, this is my opinion after reading a lot about it and seeing recommendations like "if you need documentation just read existing code", "why is Glade missing X or Y? just copy some XML node, just edit the XML and pray".

Anyway who cares, maybe GTK4 is good and new GTK threads will not be full of people talking about how bad it was. But why not move the tools together with the rest? I know, it's open source, lack of maintainers, but I wouldn't dare to declare my toolkit stable until basic tools work. Qt is also guilty of doing that in some ways but at least the previous version is still production ready and they move really fast.

I don't know I'll ever get over my irrational anger about how they handle(d) GTK.

Re:Are we GUI Yet? The state of building user interfaces in ... by badsectoracula on Friday July 09, 2021 @01:10PM (#27785944)
> if you want GTK and you believe API stability is the most important thing then you should just use GTK3. The API there is frozen

That is certainly not a solution, you just postpone the problem.

The real solution would be the Gtk4 to be 100% backwards compatible at both the API and ABI level with Gtk3 and similarly with Gtk5, Gtk6, etc.

Otherwise you're just subscribing to wasting your time - it might be now or it might be 5 years from now, it doesn't matter however as it will happen unless the Gtk developers finally decide to stop breaking their library every few years.

(of course don't get me wrong, it is their library and they can do whatever they please with it, they are giving it for free and they are not beholden to anyone - however that doesn't mean others like to have their code broken and waste time that they could use to improve their applications instead)

Re:Are we GUI Yet? The state of building user interfaces in ... by mumblemumble on Friday July 09, 2021 @01:33PM (#27786219)
Alternatively GTK3 could get a higher level of ongoing support. That was what I was alluding to when I referenced Microsoft. For example, WinForms has technically been superseded for ages now, but, while it's not necessarily getting any big new features, WinForms apps still look decent on newer versions of Windows, benefit from things like updates to the common dialog boxes, and continue to be well-supported in new versions of the developer tools. So one doesn't necessarily have to have a lot of anxiety about leaving an old WinForms app on WinForms. With GTK3, on the other hand, I would guess that it's going to get the absolute bare minimum of love, and probably become a liability rather sooner than I might like, because the project simply doesn't have the resources to maintain a higher level of support.

And yeah, you're right, the GTK team isn't beholden to anyone. But... GUI code is expensive to write and expensive to maintain. So a GUI toolkit can have an outsize impact on the health of projects that use it. There's value in talking about things like this publicly, so that anyone who's shopping for a GUI toolkit can have a better understanding of what they might be getting into.

Re:Are we GUI Yet? The state of building user interfaces in ... by badsectoracula on Friday July 09, 2021 @02:39PM (#27786967)
Ideally they could have done that with Gtk2 which would continue on to Gtk3 and Gtk4 without breaking backwards compatibility.

Of course yes, the next best thing wrt. backwards compatibility is at least not breaking what works - but IMO that is a waste of time for both the Gtk developers (sure, it'd be self inflicted, but still) who would need to support two (or three or four or however many times they decide to break their own APIs) libraries that do essentially the same thing in different ways, and for the developers who at the end of the day will most likely need to move on to the next version at some point to gain access to new features that they may need - so they'll spend that porting time anyway.

> And yeah, you're right, the GTK team isn't beholden to anyone. But... GUI code is expensive to write and expensive to maintain. So a GUI toolkit can have an outsize impact on the health of projects that use it. There's value in talking about things like this publicly, so that anyone who's shopping for a GUI toolkit can have a better understanding of what they might be getting into.

Indeed and this is why i mention my issues with backwards compatibility whenever i see it being relevant.

I do believe the Gtk developers are free to do whatever they want as they are not beholden to my -or anyone else's- wishes for stability, especially when they give out such an otherwise high quality library for free. However that is from their perspective.

From the library users' (that is the developers who use the library) perspective however there are additional issues, like all the time you spent learning the library (breaking the API invalidates your own knowledge which is something that is also important - unless you plan to somehow live forever it makes sense to want to avoid this sort of "knowledge churn" :-P) and writing the code that uses it (important especially for framework-style libraries like Gtk that put their tendrils everywhere in your application). And even if someone believes (wrongly, IMO) that commercial developers can afford all that time, it still is an issue with FLOSS since the vast majority of which is developed during its developers' free time: that time would have better been used to improve the applications instead of keeping up with their dependencies' breakage (e.g. XFCE or... Gimp :-P).

And of course from the end users' perspective it also means that even if the developers decide to drop a program, they can keep using it for a long time without having to worry about the libraries their program depends on getting stale (since they are linked dynamically), not supporting new features (like, e.g. Wayland - AFAIK Gtk2 apps do not support it natively and chances are if a new display server is made Gtk3 apps wont support it either) or having unfixable security issues (for the applications where that makes sense at least).

But yeah, Gtk developers - or any library developers - do not need to care about all of that nor they have to really. As you wrote, it is the developers who decide or not to use a library that care about such things mostly.

Sadly at last on Linux there aren't that many choices: of the "mainstream" toolkits only Gtk and Qt exist. Gtk is, well, Gtk and Qt cannot provide "perfect" ABI compatibility even if they wanted to because of C++ (there are some hacks that could be made but i am not aware of any project doing such a thing - i think only Haiku does something similar with proxy libraries that forward the GCC C++ 2.95 calls to modern GCC C++ calls for BeOS compatibility). But Qt is also a different beast, they are a middleware company with different priorities, the people that pay money on it (and thus affect these priorities) do not care much about providing a stable platform and can affort to waste time on upgrades. From other toolkits there is also Motif but that fell out of favor and got opensourced way too late to make much of a difference - its API/ABI is stable though and has been stable for decades, but that means nothing when barely anyone uses it or develops for it.

Personally i use Lazarus and LCL. LCL uses a variety of backends, kinda like wxWidgets, but unlike wxWidgets it doesn't break its API. This pushes the issue of keeping up to date to the LCL developers (who could have spent their time in fixing LCL's other issues - of which are many - instead) but that is how things are.

I think Java and SWT might be another stable solution for a native UI, AFAIK this never broke backwards compatibility either... or at least it never did back when i looked into it several years ago. Looking at some examples in their site, several of them seem to be somewhat old so it probably is stable (isn't it great how when you do not break your API left and right you get to also get time to build better documentation that you don't have to invalidate it after a while?)

Re:Are we GUI Yet? The state of building user interfaces in ... by jcelerier on Friday July 09, 2021 @03:50PM (#27787799)
> Qt cannot provide "perfect" ABI compatibility even if they wanted to because of C++

That does not really matter in practice though. I ship a Qt app as AppImage, it works fine from CentOS 7 to the very latest ArchLinux. I just ship libc++ along with it - which is the same that I have to do in Windows anyways.

Re:Are we GUI Yet? The state of building user interfaces in ... by badsectoracula on Friday July 09, 2021 @05:37PM (#27788820)
Of course it matters in practice since we're talking about dynamic linking that applications can link against the OS-provided libraries so that they can keep gaining new features and bug fixes.

A trivial example on Windows would be how Win32 applications get to use the Win+; emoji popup even if they were made before Windows even got that feature, or how even classic VB applications can be made to run in HiDPI mode by ticking a shortcut checkbox despite being written decades before HiDPI was even a thing (assuming they use twip instead of pixel coordinates at least).

Or on Linux, how some old games made for it need their bundled SDL removed so that the games can use the system-provided version because the old version tried to use OSS or whatever was common at the time the game as written and the new version can use ALSA or even Pulse that didn't even exist in older times. And i remember reading on twitter about some distros planning to provide the SDL1-to-SDL2 wrapper as an option instead of the real SDL1 because it provides better compatibility with some modern window managers... and Wayland (that SDL1 doesn't support at all but the API doesn't really make a difference and could work perfectly fine with Wayland).

> which is the same that I have to do in Windows anyways.

Windows comes with WAY more functionality out of the box so that applications do not have to rely as much in their own libraries and can rely on the OS to provide and keep functionality up to date. Of course applications can ignore that, but they just do not get those new features and fixes.

The recent Visual C++ runtimes not being part of Windows is a baffling and really stupid decision though. I am certain it has more to do with internal politics and feuds between WinDiv and DevDiv than something practical.

Re:Are we GUI Yet? The state of building user interfaces in ... by jcelerier on Friday July 09, 2021 @07:14PM (#27789562)
> A trivial example on Windows would be how Win32 applications get to use the Win+; emoji popup even if they were made before Windows even got that feature, or how even classic VB applications can be made to run in HiDPI mode by ticking a shortcut checkbox despite being written decades before HiDPI was even a thing (assuming they use twip instead of pixel coordinates at least).

eh, I really really disagree with this. In my experience more often than not this kind of changes breaks the app in various ways. What if the app was using that shortcut for something else ? Now it's broken and can't be used anymore. Likewise for the hidpi thing that windows does, it's terrible - running the app at original resolution and applying a 2x nearest neighbor filter to the whole window would be better than that mess of "crisp" text with upscaled pixmaps that were never made for this resolution.

> Or on Linux, how some old games made for it need their bundled SDL removed so that the games can use the system-provided version because the old version tried to use OSS or whatever was common at the time the game as written and the new version can use ALSA or even Pulse that didn't even exist in older times. And i remember reading on twitter about some distros planning to provide the SDL1-to-SDL2 wrapper as an option instead of the real SDL1 because it provides better compatibility with some modern window managers... and Wayland (that SDL1 doesn't support at all but the API doesn't really make a difference and could work perfectly fine with Wayland).

I strongly believe that for old games / software it's better to use a VM / emulator for hardware of that game's era.

Re:Are we GUI Yet? The state of building user interfaces in ... by badsectoracula on Sunday July 11, 2021 @04:44PM (#27804412)
> eh, I really really disagree with this. In my experience more often than not this kind of changes breaks the app in various ways.

What did break?

> What if the app was using that shortcut for something else ? Now it's broken and can't be used anymore.

Win+; is very unlikely to be used by anything and it is handled by the window proc of the EDIT window class, meaning that other stuff (e.g. accelerators, which are used to implement shortcuts) get to take first dibs. So if an application was using that shortcut it wouldn't reach the EDIT window proc anyway. It isn't any different than an application replacing the right click menu of a text field - the applications that do not do that (ie. most applications) get the new entries introduced in (IIRC) Vista about Unicode characters, etc and the (few) applications that replace it just do not get these options but their menus keep working.

> Likewise for the hidpi thing that windows does, it's terrible - running the app at original resolution and applying a 2x nearest neighbor filter to the whole window would be better than that mess of "crisp" text with upscaled pixmaps that were never made for this resolution.

Note that this is what Windows does by default, what i describe is something you can do manually.

But personally i disagree, i'd rather have crisp text (which is what the majority of a window contains) and a few upscaled bitmaps than lowres everything.

> I strongly believe that for old games / software it's better to use a VM / emulator for hardware of that game's era.

I play a ton of old games and i completely disagree with this. VMs pretty much never work properly and have all tons of issues. Emulators are very slow. And above all, running games on modern hardware allows for higher resolution and maxing out graphics that was often impossible in original hardware (e.g. forcing 32bit color, antialiasing, anisotropic filtering, etc). Not to mention the potential for mods that improve parts of the game which would be impossible on original hardware.

Re:Are we GUI Yet? The state of building user interfaces in ... by shock on Friday July 09, 2021 @10:17AM (#27783891)
> Nobody is particularly happy about having to edit the XML directly but it's the best option right now until the new tools stabilize.

You are proving GP's point for him:

> So I rather waste my time on Earth on platforms that value good UI/UX tooling.

The fact that that Glade was deprecated without a replacement being ready means exactly that GNOME does not "value good UI/UX tooling".

Re:Are we GUI Yet? The state of building user interfaces in ... by _d7dt on Friday July 09, 2021 @10:20AM (#27783920)
What you've said is really not correct, at all. For one, Glade is not deprecated in the sense that it doesn't work any more, it still works okay with GTK3, however it has a number of limitations that may make it difficult to use (which it always had, nothing has changed here). Two, a replacement is being worked on, I'm really not sure what your criticism is besides "go faster" which, I'm sure we all wish we could write code faster and have it work perfectly and do everything the first time, but that's not realistic.

Edit: Just to be clear here, in my opinion the new tools will likely end up being a large improvement on Glade. Glade is a pretty old application that by design does a number of weird things that don't match current best practices, you can see some of them if you read the blog post that was posted above.

Re:Are we GUI Yet? The state of building user interfaces in ... by freedomben on Friday July 09, 2021 @04:41PM (#27788250)
> The fact that that Glade was deprecated without a replacement being ready means exactly that GNOME does not "value good UI/UX tooling".

That's a false dichotomy. It could be (and I believe is) that things are a tradeoff. They obviously value good tooling (what developer doesn't? and look at the docs), but they value other things too and had to make a decision. With limited resources you can't do it all.

Re:Are we GUI Yet? The state of building user interfaces in ... by qwerty456127 on Monday July 12, 2021 @07:49AM (#27809320)
> Nobody is particularly happy about having to edit the XML directly

I wouldn't mind editing a concise XML dialect (XML really doesn't have to be monstrous, a dialect it can be designed with humans in mind). A visual designer producing XML files as its output doesn't actually solve the problem. VisualStudio's developer experience (where you can change everything on the fly, go to the relevant piece of code in a click or two, refactor something and get it also changed in the designer etc) feels really seamless and fluent while PyQt with PyCharm+QtDesigner seems nice but not nearly like that. It seems to me nothing can be considered a serious and worthy improvement until we have an actual integrated visual RAD IDE. I would immediately buy the paid version of PyCharm (I'm using the community edition if they built a good and well-integrated visual designer in it, for whatever a desktop toolkit they prefer).

Re:Are we GUI Yet? The state of building user interfaces in ... by pjmlp on Friday July 09, 2021 @12:13PM (#27785240)
Thanks for the link, I will watch it when the opportunity comes.

However it is like the sibling comments mention, this hasn't been properly managed as message to the UI/UX community.

So when someone used to Forms, WPF/Blend, Qt Designer, Interface Builder, Delphi, C++ Builder, Swift UI, Flutter, JetPack Composer,... sees blogs and tutorials where .ui files are written by hand and direct use of GtkBuilder is praised, eventually all interest is gone.

Anyway, thanks for the link and for jumping in

Re:Are we GUI Yet? The state of building user interfaces in ... by _d7dt on Friday July 09, 2021 @12:32PM (#27785480)
That blog is just one developer's opinion, not an official statement. Although I will say I share the opinion, Glade messes up my ui files and I can't recommend using it if you want to use any newer widgets. It has always had those problems, but now with GTK4 it's no longer really worth it to try to work around them.

Also, Glade is not really even used by GNOME designers that much, what they do is make mockups in some other tool (usually Inkscape) and then have the developers implement it. I don't know about other GTK based desktops, though I think some Elementary developers are working on this: https://github.com/akiraux/Akira

Re:Are we GUI Yet? The state of building user interfaces in ... by mumblemumble on Friday July 09, 2021 @10:46AM (#27784223)
Linus recently said something that left me thinking that Linux on the desktop has much deeper problems that need to be addressed before it's worth even thinking about the fine details of GUI toolkits.

https://www.youtube.com/watch?v=Pzl1B7nB9Kc

Re:Are we GUI Yet? The state of building user interfaces in ... by qwerty456127 on Friday July 09, 2021 @06:55PM (#27789454)
Yet Linux worked perfectly for me and many people/offices I migrated to it (they didn't need any Windows-only apps) during the recent decade. Since about half that time Windows and Mac users don't even have to learn nor tolerate anything - everything is familiar (today users of Ubuntu should better learn GNOME3 workspaces though but that's not necessary) and eye-candy.

So I really have zero idea of what problems might he mean. Besides lack of native Photoshop and Visual Studio the only thing which always annoyed me in desktop Linux were NumLock quirks. There was also a problem with games but apparently it's not the case any more.

Re:Are we GUI Yet? The state of building user interfaces in ... by rodelrod on Friday July 09, 2021 @11:14AM (#27784517)
> Linus recently said

At DebConf 2014

Re:Are we GUI Yet? The state of building user interfaces in ... by AnIdiotOnTheNet on Friday July 09, 2021 @04:09PM (#27787972)
True, but it isn't like the things he talks about have changed significantly since then.
Re:Are we GUI Yet? The state of building user interfaces in ... by mumblemumble on Friday July 09, 2021 @11:24AM (#27784641)
Ha. That's what I get for looking at the video posting date and assuming it means anything.
Re:Are we GUI Yet? The state of building user interfaces in ... by pengaru on Friday July 09, 2021 @12:03PM (#27785113)
To be fair, 2014 is recent in Debian time.
Re:Are we GUI Yet? The state of building user interfaces in ... by criddell on Friday July 09, 2021 @10:01AM (#27783761)
I used to think so too. Around 2005 I finally accepted that Linux on the desktop is what it is and not much will change.
Re:Are we GUI Yet? The state of building user interfaces in ... by qwerty456127 on Friday July 09, 2021 @07:29PM (#27789638)
Then, in just some years, everything changed: Wireless drivers became flawless out of the box (it could take a day to make WiFi work in 2007). Unity emerged, took some years to mature and Linux has became really like Mac but even better in many aspects (and slightly worse in some small details advanced Mac users can miss). Windows 7 came and prepared the Windows population for the Unity panel. Then Unity died making the desktop experience slightly worse again but KDE finally matured enough to achieve even more (except I still miss Unity HUD with menu search). Today I just use XFCE with Chicago95 on Manjaro for my own hot-meets-retro pleasure, give others vanilla Ubuntu (with "restricted extras") and everybody is happy. Also Pop_OS with its user-friendly tiling integration is insanely cool (but it fails to install on some laptops where Ubuntu doesn't).
Re:Are we GUI Yet? The state of building user interfaces in ... by criddell on Saturday July 10, 2021 @10:55AM (#27793719)
Nothing really changed. Linux on the desktop is still pretty much relegated to people who develop for Linux. ChromeOS is probably the closest Linux will ever come to desktop success.

When a company rolls out Linux desktops it's a news story because it's unusual. There are killer apps for Windows and Mac. How about Linux? What application is going to have my uncle calling me asking which Linux machine he should buy?

Re:Are we GUI Yet? The state of building user interfaces in ... by qwerty456127 on Monday July 12, 2021 @08:05AM (#27809427)
> Nothing really changed. Linux on the desktop is still pretty much relegated to people who develop for Linux.

I can only attribute this to marketing as I can see no single humble thing (except lack of MS Office (which is being phased out by MS favouring Office 365), MS VS, Adobe CS and the NumLock bug) in which Linux actually is worse than Windows. And I can see many in which it is better. Even the very user experience is better - Linux feels faster, is more reliable and can be customized to whatever you want (if you do) with relative ease. Lack of some specific apps is not a flaw of Linux. Whoever doesn't need these specific apps can use Linux comfortably.

> What application is going to have my uncle calling me asking which Linux machine he should buy?

What apps does he need? If he doesn't need the apps I've mentioned I would insist he uses Linux if I were you - so I won't have to fix it next time it breaks, gets slow or infected by something nasty.

> When a company rolls out Linux desktops it's a news story because it's unusual.

I have alone rolled out (and never wanted that to be in any news) Linux in a number of companies (~20 desktops/laptops, Browser+Office+Skype+Samba+RDP+OpenVPN workflow, one also needed a Windows GUI CRM client which I configured to run with Wine flawlessly). This worked fast and reliably forever ever since. I wouldn't, however, agree (unless paid extremely well) to become in charge of a Windows system of the same or bigger size as that would mean much more work regularly.

Re:Are we GUI Yet? The state of building user interfaces in ... by ZeroCool2u on Friday July 09, 2021 @12:43PM (#27785619)
Flutter desktop works shockingly well on Linux desktop in my experience. It's AOT compiled to native byte code, so it's pretty fast. I think the main weakness would be 3D applications, but I can't say for certain.
Re:Are we GUI Yet? The state of building user interfaces in ... by qwerty456127 on Monday July 12, 2021 @08:17AM (#27809491)
Cool. I've been waiting for this since Flutter has been first announced. I will surely give it a try. I just hope you don't need to be fluent in Photoshop, CSS and a pack of libraries to create a basic table-and-buttons desktop app in it like that is with the web stack.
Re:Are we GUI Yet? The state of building user interfaces in ... by ZeroCool2u on Monday July 12, 2021 @09:50AM (#27810237)
No, it's actually pretty fun writing UI's in Flutter, because it's relatively straight forward.

Edit: Fair warning, desktop development code is _interpreted_ by the VM when doing debug builds, so that you can have hot reloading, which is great. But it may seem like your app is slow until you do a release build. Though it seems obvious in retrospect, it took me by surprise at first.

Re:Are we GUI Yet? The state of building user interfaces in ... by interlocutor on Friday July 09, 2021 @08:31AM (#27783003)
And why is it better than Web technologies? Even if you don't want a server involved you can still make a desktop app using Web technologies.
Re:Are we GUI Yet? The state of building user interfaces in ... by sgift on Friday July 09, 2021 @09:09AM (#27783294)
The developer experience of web technologies is after all this time still far worse than all the desktop libs I've tried. It is even worse than Swing (for those who don't know: That's Javas GUI technology. From the 90s). Add to that the horrible RAM usage, the general jankiness and ... thanks, but no thanks.
Re:Are we GUI Yet? The state of building user interfaces in ... by gedy on Friday July 09, 2021 @09:39AM (#27783531)
> It is even worse than Swing (for those who don't know: That's Javas GUI technology. From the 90s).

As someone who loved Swing and used to hate JavaScript, that's really nonsense if you actually want to be a UI developer (and not just some side afterthought).

State management and the custom capabilities when you need them are amazing. I wasted a lot of my time writing tons of Swing code. Sorry, but the modern front end experience is much more enjoyable and productive. If you want "native widgets" I get the complaint, but most platforms seem to be less interested in consistent experiences these days.

Re:Are we GUI Yet? The state of building user interfaces in ... by kaba0 on Friday July 09, 2021 @02:33PM (#27786894)
> State management and the custom capabilities when you need them are amazing

JS devs just rediscovered MVC with some added immutability and that’s all. Hardly more productive. Also, I don’t see your point on custom capabilities - please add a slight modification to the date picker widget. Oh, you have to reimplement the whole thing with some insane number of divs, while you can trivially override certain parts of it in most desktop libs.

Re:Are we GUI Yet? The state of building user interfaces in ... by publicola1990 on Friday July 09, 2021 @11:48AM (#27784914)
Dependency management is simple for Swing. In can mostly be assumed that it is available and works. How many dependencies will an Electron /Webstack based app have?
Re:Are we GUI Yet? The state of building user interfaces in ... by pjmlp on Friday July 09, 2021 @12:33PM (#27785493)
Plus there are frameworks like JGoodies and everyone should look at Filthy Rich Clients book.

The biggest issue with Swing is just bad defaults. Except for NeWS, Sun wasn't really into the desktop business.

Re:Are we GUI Yet? The state of building user interfaces in ... by criddell on Friday July 09, 2021 @02:18PM (#27786739)
I really like JetBrains IDEs and I think they are based on Swing.

Although I haven't used it for more than a decade, I still have some fondness for Java. I like Workflowy but am not crazy about it being in the browser. I contemplated writing my own outliner and Java + Swing is one combination I'm thinking about.

Re:Are we GUI Yet? The state of building user interfaces in ... by mumblemumble on Friday July 09, 2021 @08:56AM (#27783203)
Compared to WinUI, I wouldn't exactly call web technologies' developer experience pleasant.

This was pre WinUI, but a while back I worked at a shop that simultaneously maintained Web-based and WPF versions of an app. The Web version required 3 dedicated developers to maintain. The WPF version needed about half of one person's time, and had more features.

I would say that the main thing favoring tools like Electron is entry costs. There are lots and lots of people who know who to do front-end Web development, and you can do a good job of supporting all platforms using free tools. Even if you grant me for the sake of argument that native GUIs cost less in the long run, there aren't a whole lot of people who have experience doing them these days, even fewer who have experience on more than one platform. Going that route also requires you to shell out for Macs and probably also Visual Studio.

Re:Are we GUI Yet? The state of building user interfaces in ... by criddell on Friday July 09, 2021 @10:04AM (#27783779)
In another thread somebody mentioned accessibility issues. Web technologies are still embarrassingly bad at this compared to native toolkits.

The other reason is that you care about resource usage. Web apps use more battery, bandwidth, and CPU.

Re:Are we GUI Yet? The state of building user interfaces in ... by tasogare on Friday July 09, 2021 @09:06AM (#27783271)
You wouldn't ask the question if you had developed both GUI apps on MS stack with VS and web apps: the MS dev experience is very good, while the web one is meh at best. C# vs JS, XAML vs HTML+CSS (debatable), desktop application model vs web one, VS vs whatever else, there is a lot of strong arguments in favor of the MS stack in that case.

Microsoft is trying to port some of this magic with Blazor, with is quite liked from what I read here and there.

Re:Are we GUI Yet? The state of building user interfaces in ... by interlocutor on Friday July 09, 2021 @04:36PM (#27788205)
It is C# vs Typescript. Modern JavaScript is a very good language, and when enhanced with TypeScript's static types, it is every bit as good as C#.

XAML and MVVM is all about two-way data binding. JS frameworks copied it at first. But now it is widely recognized that 2-way data binding is a bad idea.

You can use for Web development too.

Re:Are we GUI Yet? The state of building user interfaces in ... by pjmlp on Friday July 09, 2021 @09:34AM (#27783499)
If it isn't a PWA, or integration with 3rd party, I rather not make my users suffer.