https://www.wisdompills.com/the-famous-social-experiment-5-m...
(Even if it is bullshit)
Do you feel the same about the macOS Carbon-Cocoa transition? Nobody misses Carbon anymore, and Win32 is as old as the classic Mac Toolbox.
Eventually they have to shed the old API.
This does make me wonder if the transition from Carbon to Cocoa is analogous though. Win32 comes off as more of a "functional" approach to programming (C) and UWP is looking more object oriented (as to C++). It makes me wonder what kinds of conceptual advantages are being brought on board by moving from win32 to UWP. I think that conceptually I am in favor of the transition, and I'd wager that all the issues that arise are common to a functional to object-oriented transition.
But that real questions: What are the benefits? Is it conceptually easier to grasp thus promoting more developer interaction? Are we expecting speed benefits (are the performance losses expected and in range?) Is it a false dichotomy to only look at Functional vs OO? Maybe a context-oriented data approach is more appropriate?
Dunno.
I hate the other UWP apps. They're slow, they lack features, they have horrible UIs and they don't integrate well with the rest of the OS. The only reason why I'm using the new "Settings" app or the new calculator is because Microsoft forced me to it.
It's such a shame that Microsoft refuses to acknowledge that UWP was a mistake and keeps porting apps to it.
My biggest gripe is that startup times are just too long. So many times I've gone to launch something like calculator only to have a beefy machine hang for almost a second, if not a full second. It's likely an engineering obstacle that can be overcome but it just makes UWP look like a bad move perf wise.
The whole thing is now used in basically every library build we have at some point, even for the C# versions, as it ties in with our documentation writing process and places the correct API names and links for that product into the documentation, even though the docs start with mostly the same content for each.
I agree that lack of documentation makes working with Roslyn a bit daunting at times, although the API is very well designed and oftentimes it's very obvious where to look for something. I was also very impressed by their compatibility efforts. We started while Roslyn was in beta and upgrading through the releases worked without a hitch.
Not really. A simple empty project displays the same problems. You can try going back to 2017 right now with any project you're working on, you'll feel the difference instantly.
Intellisense simply takes longer to respond, and likewqise other editor functions.
Their feedback forums have hundreds of similar reports.
I get the exact same thing.