11 ms·

Probably because there's no commercial interest in such a thing. Now, when you say "MS controls a big pie", I can tell you there are a lot of people really not

Probably because there's no commercial interest in such a thing. Now, when you say "MS controls a big pie", I can tell you there are a lot of people really not satisfied with how MS handles things (myself included). Hopefully, they (MS) will manage to keep their WinUI promise, and make it quite easy to develop (Windows) desktop apps. As for platform-independence, there are a few attempts, but with just (a few) volunteers, it's hard to tackle such an insanely complicated issue.

tabtab 7y ago
Re: I can tell you there are a lot of people really not satisfied with how MS handles things Yes, they WANT competition for desktop/productivity app space to either motivate MS to do better, and/or provide alternatives. This will enable it. Re: Hopefully, they (MS) will manage to keep their WinUI promise, and make it quite easy to develop (Windows) desktop apps. Even if they did, one is pretty much stuck using MS's languages. Rather than write language-specific adopters, create a state-friendly GUI markup standard so any language that can read and write text and talk to the Internet can serve up GUI's. Re: it's hard to tackle such an insanely complicated issue. Base it off the Tk or QT kits rather than reinvent the GUI wheel.
- photawe 7y ago
  I'm not familiar with Tk, and how well that works, but there are a lot of things a good GUI should do -- just think of databinding and such - it's very far from trivial to develop something that looks really good on all platforms, is easy to use, uses modern concepts (MVVM), and has decent language bindings (c#, c++, java)
  - tabtab 7y ago
    A lot of those issues would be "back end framework" issues if we had a decent GUI markup standard. Tk would just be a kit to build a GUI browser with, not the domain application itself. It would be roughly analogous to "WebKit" in HTML-land. When building a domain application, you don't normally set out to build a domain application "in" WebKit, you use HTML/HTTP/CSS/JS, which are then rendered via WebKit (at least partially). A web browser doesn't have to use WebKit.

tabtab 7y ago

Re: I can tell you there are a lot of people really not satisfied with how MS handles things Yes, they WANT competition for desktop/productivity app space to either motivate MS to do better, and/or provide alternatives. This will enable it. Re: Hopefully, they (MS) will manage to keep their WinUI promise, and make it quite easy to develop (Windows) desktop apps. Even if they did, one is pretty much stuck using MS's languages. Rather than write language-specific adopters, create a state-friendly GUI markup standard so any language that can read and write text and talk to the Internet can serve up GUI's. Re: it's hard to tackle such an insanely complicated issue. Base it off the Tk or QT kits rather than reinvent the GUI wheel.

photawe 7y ago
I'm not familiar with Tk, and how well that works, but there are a lot of things a good GUI should do -- just think of databinding and such - it's very far from trivial to develop something that looks really good on all platforms, is easy to use, uses modern concepts (MVVM), and has decent language bindings (c#, c++, java)
- tabtab 7y ago
  A lot of those issues would be "back end framework" issues if we had a decent GUI markup standard. Tk would just be a kit to build a GUI browser with, not the domain application itself. It would be roughly analogous to "WebKit" in HTML-land. When building a domain application, you don't normally set out to build a domain application "in" WebKit, you use HTML/HTTP/CSS/JS, which are then rendered via WebKit (at least partially). A web browser doesn't have to use WebKit.