18 minutes ago, bondsbw wrote
As much as I'd like to see a replacement for XAML, I'd give a first priority to replacing HTML/JS. It saddens me that HTML is being embraced even more today. And the languages that have been built to replace JavaScript are really more about extending it, not about fixing its inherent flaws.
well we seem to have this thing about wanting one way to do everything ... at least a bunch of folks do. it's a bad idea but it's a common one, I think at one time a lot of management in companies got on the idea of doing everything as a web page so that the corp. it staff and budget could be stream lined, they did not want to have to deploy apps and thought that web page apps were all the future.
in some cases they are very good but the "one size fits all" should not be carried to the point of not seeing that some apps might be done better as "real" apps.
html was created to serve up formatted documents with links to other documents.
we have added on all manner of stuff on top of that and try to make it work as an application server.
for the most part it works but it was never designed for this role and has areas where it shows.
no matter the details we should use the right tools for the job, not try and make a hammer into a wrench or a screw driver into a pry bar.
use html where it's a good fit, use other tools for other things.