←back to thread

Microsoft Edit

(github.com)
486 points ethanpil | 1 comments | | HN request time: 0.538s | source
Show context
wasimanitoba ◴[] No.44375245[source]
Meanwhile, they forced AI Copilot bloat into Notepad, whose singular use-case was supposed to be that it does one thing well without unnecessary features.
replies(8): >>44375319 #>>44375373 #>>44375660 #>>44375874 #>>44375957 #>>44377416 #>>44378243 #>>44378896 #
pjmlp ◴[] No.44375660[source]
Unfortunately, the new Edit isn't safe from such decisions.

While Satya might have made the change Microsoft <3 FOSS, the Gates/Balmer era was much better towards Windows developers.

Now we have a schizophrenia of Web and Desktop frameworks, and themselves hardly use them, what used to be a comfortable VS wizard, or plugin, now is e.g. a CLI tool that dumps an Excel file, showing that newer blood has hardly any Windows development culture, or their upper management.

replies(3): >>44375851 #>>44376654 #>>44380828 #
shortrounddev2 ◴[] No.44376654[source]
There are currently no ideal native app development frameworks on Windows. WinForms is the closest thing
replies(3): >>44377505 #>>44378577 #>>44380244 #
Timwi ◴[] No.44377505[source]
I'm so glad to hear that from someone unprompted. I tried WPF and it was a million times harder to use than WinForms, and I couldn't even be bothered to try out MAUI (although I accept it as an apology for WPF lol). I'm still using a WinForms application every day (Git Extensions) and have been able to contribute to it not least because it's the good old familiar WinForms.

This is not to say that WinForms isn't without its problems. I often wonder what it could be like if all the effort of making WPF and MAUI had gone into maintaining, modernizing and improving it.

replies(1): >>44378018 #
shortrounddev2 ◴[] No.44378018{3}[source]
I think that the native GUI development APIs provided by OS vendors need a kind of "headless" implementation first, where you can build UI in pure code like winforms, and then they should offer a framework on top of that. I, personally, hate XAML. It's stricter than HTML/CSS and very opinionated about how to organize your application. I feel that XAML frameworks should have a common Winforms-like API behind them that you can switch to any time you want. But I've found that using the C# code-behind APIs manually for WPF, UWP, MAUI, etc, is far more verbose than Winforms was.

My only major problem with winforms is that it's still using GDI under the hood which, despite what many people believe, is actually still primarily software-rendered. If they could just swap out Winforms for Direct2D under the hood (or at least allow a client hint at startup to say "prefer Direct2D") it would really bring new life to Winforms, I think.

I would also like a C++ native GUI API that's more modern than MFC

replies(2): >>44379220 #>>44380191 #
1. WorldMaker ◴[] No.44380191[source]
"C# Markup" [1] [2] sounds a lot like what you are looking for. As the only "second party" option in this space it's interesting that it is so MAUI only/MAUI focused, but I suppose that's the "new hotness".

There have been similar F# libraries and third-party C# libraries for a while that seem nice to work with in similar ways.

[1] https://learn.microsoft.com/en-us/windows/apps/windows-dotne...

[2] https://github.com/CommunityToolkit/Maui.Markup