5 ms·

Another one? Why not fix the six that are already out there?

by freeone3000 7y ago

smallstepforman 7y ago
Fire and move ...
- tonyedgecombe 7y ago
  https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ https://www.joelonsoftware.com/2002/01/06/fire-and-motion/
zwirbl 7y ago
That makes seven then
- tommsy64 7y ago
  Ahh, #927. A classic! :P
  - Jack5500 7y ago
    For context: https://xkcd.com/927/ https://xkcd.com/927/
    - Talanes 7y ago
      The alt text has only become funnier with age. >Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shit.
      - nottorp 7y ago
        USB-C? Get on with the times!
        cardinalfang 7y ago
        Situation: There are 15 competing standards and they all have the same name.
0x0 7y ago
Is this going to be another silverlight? Is WPF deprecated? Is win32 gdi going away?
- jabroni_salad 7y ago
  Actually, I think they made this specifically because win32 is here to stay. UWP is officially dead and you can upload win32 to the Microsoft Store, now. This paves the way for some parts of the UWP dream (works on high dpi, supports touch, fancy graphics without needing custom assets) in win32. Between this, MSIX, containerization, etc the fat app landscape could be pretty good. Too bad all my vendors who are still releasing fat apps will never modernize and all the new vendors are web-only.
  - Mistredo 7y ago
    Dead? They still develop it, and I don't see a reason why you would start a new app in Win32 or WPF.
    - tonyedgecombe 7y ago
      One reason is you know it well and are used to the tooling.
      - SneakerXZ 7y ago
        If you ever used Win32, you wouldn't mind abandoning it. It is not good API. If you know WPF, you feel like at home with UWP.
        tonyedgecombe 7y ago
        I quite like Win32, my main app used WinForms so I still end up reaching into it quite regularly.
  - pjmlp 7y ago
    UWP is the future of Windows APIs, Win32 is mostly frozen since WIndows XP. Microsoft is just making UWP similar to what Google is making with AndroidX, detaching the technology from the OS version.
nindalf 7y ago
As pointed out in TFA, this offers the option of using the latest APIs in conjunction with the old ones, something that wasn’t possible earlier. What else did you want them to do? Continue adding features to long deprecated APIs?
- badsectoracula 7y ago
  > What else did you want them to do? Continue adding features to long deprecated APIs? Yes. It isn't like deprecating APIs is forced on them by some otherworldly power, they decide to do that and they can also decide to not do that. They are in full control of their technology, they can do whatever they want.
Mistredo 7y ago
This basically fixes all of them by building a common umbrella that all existing UI toolkits (UWP, WPF, WinForms, Win32) can use. This picture summarizes it well - https://github.com/microsoft/microsoft-ui-xaml/raw/master/docs/roadmap_winui3.png https://github.com/microsoft/microsoft-ui-xaml/raw/master/do...
- Ididntdothis 7y ago
  You know the XKCD where they have 14 standards , create the a new one to unify them and the result is 15 standards?
- ptx 7y ago
  It's the other way around, isn't it? They're not going to reimplement the Win32 API on top of WinUI, but WinUI uses Win32 in part for its implementation on some platforms (that platform being classic desktop Windows).
  - SneakerXZ 7y ago
    What I meant was you can use WinUI 3 in your Win32 app, so it is a UI toolkit that can be used in any other existing UI toolkit.
- coribuci 7y ago
  > This basically fixes all of them by building a common umbrella that all existing UI toolkits (UWP, WPF, WinForms, Win32) can use. So intead of a screwdriver, a wrench or a hex key you have now a hammer.
oaiey 7y ago
Is not WinUI the extraction of the UI part of the UWP stack? Yes namespaces break, but concepts and controls are from the same linage. UWP is more than the UI. It has also sandboxing and deployment. So essentially, it is not a new UI. Just a new version of an old one. (consider e.g. WinForms was also ported from .NET Framework to .NET Core. That is also not counted here ;))
- coribuci 7y ago
  > Is not WinUI the extraction of the UI part of the UWP stack? Yes namespaces break, but concepts and controls are from the same linage. UWP is more than the UI. It has also sandboxing and deployment. The UWP has everything except a GUI. > So essentially, it is not a UI. fixed itl > (consider e.g. WinForms was also ported from .NET Framework to .NET Core. That is also not counted here ;)) So everyday a new framework. How many days will pass until UWP will be obsolete ?
deleted 7y ago
[deleted]

Another one? Why not fix the six that are already out there?

smallstepforman 7y ago

Fire and move ...

tonyedgecombe 7y ago
https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ https://www.joelonsoftware.com/2002/01/06/fire-and-motion/

zwirbl 7y ago

That makes seven then

tommsy64 7y ago
Ahh, #927. A classic! :P
- Jack5500 7y ago
  For context: https://xkcd.com/927/ https://xkcd.com/927/
  - Talanes 7y ago
    The alt text has only become funnier with age. >Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shit.
    - nottorp 7y ago
      USB-C? Get on with the times!
      - cardinalfang 7y ago
        Situation: There are 15 competing standards and they all have the same name.

0x0 7y ago

Is this going to be another silverlight? Is WPF deprecated? Is win32 gdi going away?

jabroni_salad 7y ago
Actually, I think they made this specifically because win32 is here to stay. UWP is officially dead and you can upload win32 to the Microsoft Store, now. This paves the way for some parts of the UWP dream (works on high dpi, supports touch, fancy graphics without needing custom assets) in win32. Between this, MSIX, containerization, etc the fat app landscape could be pretty good. Too bad all my vendors who are still releasing fat apps will never modernize and all the new vendors are web-only.
- Mistredo 7y ago
  Dead? They still develop it, and I don't see a reason why you would start a new app in Win32 or WPF.
  - tonyedgecombe 7y ago
    One reason is you know it well and are used to the tooling.
    - SneakerXZ 7y ago
      If you ever used Win32, you wouldn't mind abandoning it. It is not good API. If you know WPF, you feel like at home with UWP.
      - tonyedgecombe 7y ago
        I quite like Win32, my main app used WinForms so I still end up reaching into it quite regularly.
- pjmlp 7y ago
  UWP is the future of Windows APIs, Win32 is mostly frozen since WIndows XP. Microsoft is just making UWP similar to what Google is making with AndroidX, detaching the technology from the OS version.

nindalf 7y ago

As pointed out in TFA, this offers the option of using the latest APIs in conjunction with the old ones, something that wasn’t possible earlier. What else did you want them to do? Continue adding features to long deprecated APIs?

badsectoracula 7y ago
> What else did you want them to do? Continue adding features to long deprecated APIs? Yes. It isn't like deprecating APIs is forced on them by some otherworldly power, they decide to do that and they can also decide to not do that. They are in full control of their technology, they can do whatever they want.

Mistredo 7y ago

This basically fixes all of them by building a common umbrella that all existing UI toolkits (UWP, WPF, WinForms, Win32) can use. This picture summarizes it well - https://github.com/microsoft/microsoft-ui-xaml/raw/master/docs/roadmap_winui3.png https://github.com/microsoft/microsoft-ui-xaml/raw/master/do...

Ididntdothis 7y ago
You know the XKCD where they have 14 standards , create the a new one to unify them and the result is 15 standards?
ptx 7y ago
It's the other way around, isn't it? They're not going to reimplement the Win32 API on top of WinUI, but WinUI uses Win32 in part for its implementation on some platforms (that platform being classic desktop Windows).
- SneakerXZ 7y ago
  What I meant was you can use WinUI 3 in your Win32 app, so it is a UI toolkit that can be used in any other existing UI toolkit.
coribuci 7y ago
> This basically fixes all of them by building a common umbrella that all existing UI toolkits (UWP, WPF, WinForms, Win32) can use. So intead of a screwdriver, a wrench or a hex key you have now a hammer.

oaiey 7y ago

Is not WinUI the extraction of the UI part of the UWP stack? Yes namespaces break, but concepts and controls are from the same linage. UWP is more than the UI. It has also sandboxing and deployment. So essentially, it is not a new UI. Just a new version of an old one. (consider e.g. WinForms was also ported from .NET Framework to .NET Core. That is also not counted here ;))

coribuci 7y ago
> Is not WinUI the extraction of the UI part of the UWP stack? Yes namespaces break, but concepts and controls are from the same linage. UWP is more than the UI. It has also sandboxing and deployment. The UWP has everything except a GUI. > So essentially, it is not a UI. fixed itl > (consider e.g. WinForms was also ported from .NET Framework to .NET Core. That is also not counted here ;)) So everyday a new framework. How many days will pass until UWP will be obsolete ?

deleted 7y ago

[deleted]