Here is the rant I promised on arrogant, dismissive replies about software quality on Twitter, complete with several exhibits for your delight and amusement:https://www.youtube.com/watch?v=GC-0tCy4P1U …
-
-
Also, the steady decline in documentation quality. MSDN used to be very good, and it was easy to read how to make a Windows EXE. MSDN is now a complete disaster, and I don't expect anyone can use it who doesn't already know the answer they're looking for.
-
I agree it used to be much better even as recent as 10 years back.
End of conversation
New conversation -
-
-
It's more than that though. It was the new hotness during the .com boom & we never went back because it's easier to tell end-users to go to a web site than to roll out a new version with native code where the user may not have install privileges.
-
But again, also because of the API decline to a large extent. It used to be that you just shipped an EXE. Then installs became these massive COM registration nightmares, with thousands of DLLs and registry settings. It just isn't sustainable - so it didn't sustain :)
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

Appeal to emotion. Point-of-fact : Web development produces slow products compared to native code. Any other line of thought is counter-factual. The byproduct is a general acceptance of slow apps; boiling frog analogy. I don't know why you'd defend a sentiment otherwise.