First off, your argument is quite sound and I appreciate the way you think.
I have a different take on the "100 new features" though. That they could do "all that" and be so wildly off the mark is not something I would celebrate. I don't see it as impressive at all (not as a customer, anyway). As a developer myself (SQL Server,
BI, .Net stuff), I can appreciate it to a degree in that context.
But lemme put it this way. 15 years ago, I had a team leader who had 10 years of Lotus Notes database development experience. We just had a merger and he came from the other bank. He was a great team leader -- but when I submitted a pilot for an application
that could really help in merging our data, he was blinded by his background. He loved the idea -- but he wanted to implement it in Lotus Notes (since we wouldn't have to install anything that way).
My point of view: What difference does that make if it doesn't work?
But therein lies the rub -- how do you define "work"? I conceived of this whole thing -- from the full-text indexing process I built, to the pilot for the manual-matching of outliers, to the VB.Net application for a more feature-rich version of the pilot.
Why does that matter? Because I was coming at it from the perspective of a user (someone who developed an automated process that still had an unavoidable component of manual intervention.
I knew enough about Lotus Notes to know that it would not deliver what I had in mind, so I built that .Net version on my own time in one week (so I could counter his version with something demonstrably provable). I'm not trying to claim some super coding
skills or anything of the kind (I was just learning VB.Net at the time). I'm simply saying that my mindset was rooted in how the user would interact with the application -- not slapping something together that we "didn't have to install."
It was not even in question once I presented my version -- it blew his Lotus Notes version out of the water. I would add that the primary user of the program absolutely loved it. That team leader had my pilot on a silver platter (and he fully approved of
it) -- and yet he was still way off the mark.
Now why do you think that is? It wasn't just the platform at issue, it was the attitude in his approach. Had he worked with the data like I did, perhaps he would have seen things differently.
The point is -- Microsoft's "one size fits all mentality" is exactly line with that team leader's thinking. And I'm not telling you anything you don't know -- you said it yourself below: "Having one program to focus development on will make life easier for
the MS programmers."
EXACTLY! It has absolutely nothing to do with what's in the best interests of the customer.
Microsoft is not even remotely concerned with how I use OneNote -- and it shows!
You might be interested in checking this out -- it's a video by some guy who seems to have an angle in peddling this half-****ed knockoff:
https://youtu.be/S5hLShifujw
Yes, that youtube is interesting take on the Windows 10 UWP <cr>applet. His point about adding 100 new features in 2018 is amazing. That is an incredible pace of development. Frankly it is almost unbelievable. As a former developer it would be a massive
PITA just to keep up with other changes being rolled out. BUT, maybe MS should have waited another year to add another hundred missing features before they made UWP mandatory.
The point about UWP being the same across all OS's is nice, but it does not make up for missing features. Having one program to focus development on will make life easier for the MS programmers. BUT, it means that new features will ALWAYS be limited by
the lowest common denominator OS. So it will always be dumbed down due to the limits of the cheapest device supported.
dd