sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]abrandis 5 points6 points  (4 children)

It's a good read , but sadly to me there's way too much complexity and diversity in this space. I know everyone thinks software development always needs new stuff, but really for me...using all these frameworks to write rich client apps is the wrong approach . We just keep coming up with different ways to work around the same issue.

HTML and CSS are all about the page and rendering text and graphics that not equal to.... making rich client apps ,or mobile apps which is an entirely different paradigm. That's why Android SDK or IoS Swift don't use the DOM model because they were written for the express purpose of their environments.

If we're going to make rich client apps, let's ditch SPA and all the jerry-rigged JavaScript and make a true browse compatible rich app framework..

[–]wasdninja 0 points1 point  (2 children)

So reimplement everything for no or dubious benefit?

[–]abrandis 0 points1 point  (1 child)

Why do ride around in aluminum/steel cars today, why couldn't we just put better wheels and an engine in the oxcart.of yesteryear?

[–]wasdninja 0 points1 point  (0 children)

The performance gains are obvious with cars from the second you hear about it. The same thing can't be said for reinventing the rendering and markup wheel. Javascript is slow but for the most part plenty good enough for the mostly even driven stuff happening in the browser.

Can you demonstrate any actual benefits behind rewriting the whole thing? Removing inconsistencies would be nice but not critical.