2 ms·
I think the OP's issue is custom-written enterprise application development though: I agree with your examples of spreadsheets and IDEs (I mentioned those above
by __d 9y ago
I think the OP's issue is custom-written enterprise application development though: I agree with your examples of spreadsheets and IDEs (I mentioned those above), but they're generic applications, and their development doesn't justify Microsoft investing in an entire stack.
If the UX and latency requirements can be met with a web app, it doesn't support WPF/.NET maintenance/enhancement.
Web apps can do density so long as the latency requirements aren't too tight. There's where the banking folks spend their IT money.
- michaelt 9y agothey're generic applications, and their development doesn't justify Microsoft investing in an entire stack. Seems to me there's one or two applications for every profession, and they probably mount up. I mean, I'm sure if you look at the statistics only 0.1% of users use Photoshop, or Premiere Pro, or AutoCAD, or SolidWorks, or Altium, or Matlab, or whatever - but if you drop support for all of them, what are users going to do?
- bonesss 9y agoThere are also new development fronts in specialist domains that are computationally intensive or a poor fit for web-apps. Specifically, when WPF was launched all they could talk about were the cool 3D possibilities for doctors, researchers, and such... The reality has been less "Minority Report" than we had hoped, but those kinds of demands are growing, and very often will require the level of control over hardware that demands a desktop app. In theory a lot of this is solvable with webapps, in practice there is a reason desktop computing environments exist :)