Live data from Hacker News

Writing GUI apps for Windows is painful

tulach.cc

191–200 of 577 posts

Re: Writing GUI apps for Windows is painful

#191

Earlier quoted context omitted.

For >1 minute incremental compile times? No thanks.

[flagged]

The complaint is that writing GUI apps is painful not that it's impossible. In particular, when compared to other platforms, windows has had 30 years, several frameworks, market dominance, and they all still end up getting a D- for one reason or another.

Re: Writing GUI apps for Windows is painful

#192
post #27

Writing GUI apps is painful everywhere, and has been for years. I remember the half-baked transition from Windows Forms to WPF, which was then taken-over by the Windows Phone initiative, which was also extremely painful and half-baked. There's a reason electron is so popular, despite all the complaints about it as a platform. Don't blame the electron devs, blame Microsoft for completely failing to support their own p…

The lack of windows support for windows GUI's on windows is mind blowing. I remember absolutely whipping up Visual Basic line of business apps using the form designer in Visual Studio and data bound controls etc. If you wanted more there was MFC (with MTL developed by some insiders I guess at microsoft) The absolute insanity of going to WPF (wasn't data binding via reflection -> these apps got horribly sluggish!) the…

> The emphasis on Universal Windows Platform as "the future" of app development is absurd.

Remember when Microsoft honestly thought they had a shot at making a mobile platform to compete with Android and Apple?

Re: Writing GUI apps for Windows is painful

#193

I'm working on a GUI toolkit that should match the requirements: Slint - https://slint.dev Can be compiled statically in a single .exe that is smaller than 40M. Has a license that allow proprietary on desktop for free. Has dark/light styles. Even comes with a (work in progress) drag and drop WYSISYG editor.

Where did the idea come from that starting with a 40MB exe is small? That's completely outrageous. You could embed all of python, tk, fltk, wxwidgets and pyqt and still not be close to 40MB.

FLTK static binaries start at 100KB, win32 binaries can start at 1KB, Juce is about 2MB.

Using GLFW or SDL for an openGL window then using IMGUI would start at a few hundred kilobytes.

What are you doing in there that makes your binaries 100x times as big and why would this be a selling point?

Re: Writing GUI apps for Windows is painful

#194

Earlier quoted context omitted.

For >1 minute incremental compile times? No thanks.

[flagged]

You're being an unnecessary dick.

Long compile times are annoying and affect productivity. Some people are really sensitive to this type of disruption and it gets very difficult to stay in flow when the only thing you can do is sit and stare at a progress bar. This is particularly offensive to C# developers.

Take your elitist attitude and your gigantic C++ monstrosity elsewhere. Tell me you haven't used a modern JIT language without telling me you're a scrub. Jesus.

Re: Writing GUI apps for Windows is painful

#196
post #116

Earlier quoted context omitted.

It's funny that you mentioned apple because their system shortcuts are integrated as hell and they even let you map them in the OS -> App level, way better than anything MS has ever shipped.

Yep, among other things both Apple-unique and emacs-esque text navigation shortcuts are in every native textfield across all apps and anything that's a menu item in any app can have its shortcut key rebound in System Settings without any extra work on the part of third-party devs. It's one of the reasons why longtime Mac users are disinclined towards non-native apps. Most don't bother to reproduce these behaviors, an…

Don't forget you can type any of those menu items in the help dialog and it will not only tell you where it is, and not only let you activate it, it will helpfully show you the deeply nested set of submenus required to activate it.

Oh and of course those shortcuts are activateable by other applications to simplify app integration.

Re: Writing GUI apps for Windows is painful

#197

Earlier quoted context omitted.

For >1 minute incremental compile times? No thanks.

[flagged]

incremental compiles. Changing a single line should not take over a minute to compile in 2024.

And it's not even a "truly large" project, your patronising tone is wasted.

Re: Writing GUI apps for Windows is painful

#199
I've been using EGUI to write GUI programs. Works nicely and runs on both Linux and Windows without notable differences. (I haven't tried Mac, but it presumably will work there as well without changes). Small binaries (a few Mb), and can integrate with maps, 3D rendering etc.
Post reply on HN