Earlier quoted context omitted.
If your application saves me time (is intuitive) or enables me to do tasks that I couldn't do before (is powerful) then I don't care one whit what it looks like. As long as it doesn't actively hurt my eyes to stare at you can do whatever you want.
Sure, if I'm building something for myself or fellow hobbyists this approach works (though in that case I'd prefer a good TUI/CLI). But if you're building an app for the average person, how it looks has a big effect on whether they choose it over an alternative.
Windows native app development is a mess
301–310 of 481 posts
Re: Windows native app development is a mess
#302Earlier quoted context omitted.
There are like three settings pages that use JavaScript and React Native, the vast majority of Settings is C++ and XAML/WinUI2
but that was already developed, all new development it's going with web based at microsoft
Re: Windows native app development is a mess
#303That is why everyone even Microsoft themselves does Electron. Running with html/css/js has benefits it really is open and free development based on international standards and not locked into any single big tech.
Say what you will about Apple, they at least still think it’s important to support and do native development, especially for their OS. Microsoft might as well have bought webOS as their new Windows replacement and admitted they’ve given up on native apps.
Re: Windows native app development is a mess
#304"So when I went to work on my app, I was astonished to find that twenty years after the release of WPF, the boilerplate had barely changed." Such is the benefit and the curse, I guess, of having the Windows API being locked in the distant past for backwards compatibility. I've always been surprised that Microsoft didn't do a full operating system refactor and provide a compatibility layer for running old binaries. Pe…
"I've always been surprised that Microsoft didn't do a full operating system refactor and provide a compatibility layer for running old binaries" Just keeping a legacy system in working order is different skillset than writing a new system from scratch. So you need a new team. Nothing from Windows maintenance transfers. Maybe would require hiring someone who knows how to design an OS. It would be a major undertaking,…
Re: Windows native app development is a mess
#305Earlier quoted context omitted.
Have you tried WinForms? It isn’t the latest hotness so Microsoft has to be dragged kicking and screaming to support it in current VS, but they were forced to do so because corporate developers still have some clout.
I still think that WPF was the peak desktop UI framework. Extremely powerful with lots of small composable primitives, can easily do declarative but drop into more traditional event-driven imperative style where it makes sense.
Re: Windows native app development is a mess
#306Earlier quoted context omitted.
Programming with GUIs?
Why wouldn't you program a GUI with a GUI if one is available? Avoiding the use of WYSIWYG editors when making GUIs is like avoiding the use of musical instruments when writing songs.
Re: Windows native app development is a mess
#307Earlier quoted context omitted.
Programming with GUIs?
Why wouldn't you program a GUI with a GUI if one is available? Avoiding the use of WYSIWYG editors when making GUIs is like avoiding the use of musical instruments when writing songs.
And as a side-effect of that, merge conflicts become murder when your "Fix right-hand margins" commit with a 20 line readable +/- diff instead becomes a 1000 line +/- diff.
The one time I built an iOS app using the xCode IB so that I could get up to speed more quickly, I really came to regret it several years into the project.
Re: Windows native app development is a mess
#308I’m still confused which frameworks are tied to which “visuals”. Ignoring the web-frameworks, do Win32 apps inherently look like Windows XP buttons or can they look more modern? It might be nice if the article could add screenshots, a few of the Wikipedia links have a screenshot, but again I’m not sure if you’re limited to that UI or not. I also like the carousel in the article showing the tray menus, but again not s…
Now, I'm not 100% sure, since there are so many commenters in this thread saying "just use Win32/MFC like a real man". (Most of them ignoring the memory safety angle.) I might do a follow-up asking Claude to reproduce my UI in the various frameworks to test. But my strong guess is that we just have a bunch of HackerNews curmudgeons who are happy to foist pixelated Vista-era light-mode-only UIs on their users.
[1]: https://github.com/dotnet/winforms/issues?q=is%3Aissue%20sta...
Re: Windows native app development is a mess
#309The Windows code signing experience has prevented me from shipping apps that otherwise run perfectly fine on the platform. It is a nightmare and I cannot believe it wasn't called out in the "We want to fix Windows" blog post. Just do exactly what Apple does. Charge me $100 directly from you and let me build an .exe that I can distribute on my website.
This isn't well-known, so I figured I'd mention it. Microsoft offers a service called Azure Artifact Signing (used to be called Trusted Signing) that manages code signing for you: https://azure.microsoft.com/en-us/pricing/details/artifact-s... It's $9.99/mo, and you don't need to worry about procuring or renewing code signing certs.
Re: Windows native app development is a mess
#310Excellent summary of the stupid state of Windows native GUI app development after the complete lack of direction or coherence Microsoft has shown. Not to mention the irony of Visual Studio not having a GUI designer for anything except Windows Forms.