>Sure, as all layers are independent, and JavaScript VERY flexible (extensible, untyped, auto coercion), you can imagine a bunch of combinations, hence the many blogs from people finding the best practices… Same for the JS frameworks: some extend the native and HTML objects, some other consider it as 'evil' to >never be done and wrap everything into an object. That's what I covered under '20 years trying to make it more simple'… except that it requires a rewrite every 5 or 10 years: we are in the process of deprecating prototype.js, considered as the 'best framework around' in 2005, now dropped as 'worst evil'; moving to >angular2 requires a deep rewrite compared to angular1; let's not talk about moving from angular to a competitor like ember or vue. How can a SMB software editor remain competitive, and even alive, while waisting time rewriting its code base, concurrently maintaining several code bases, etc. It's just impossible.
I recently watched a talk (found the link on G+ but couldn't find it) where the guy who wrote Django suggested that it might be better to write your own code in plain JS, CSS and HTML. It didn't really sound like he was suggesting writing your own framework but I think it was close. The idea was that you would write the code to meet the needs of the project. His biggest complaint was over time any framework will start trying to meet the needs of it's user "edge" cases. Which causes the framework to grow and lose it's "lean and mean". I see examples of that problem almost daily with VueJs. At the moment it is small and very fast - but everyday I see that others are asking for some module to be built into VueJs. So far Mr. You has resisted the requests.
I found it
https://www.youtube.com/watch?v=VvOsegaN9WkAnyway, my biggest complaint about web programming is the fact that it is always changing (also don't like javascript). Any small business today has to try and keep up. But that is, of course, a major challenge. So I say if you have a paying project go ahead and use the latest tech otherwise don't fix it. The problem with my statement is why I'm here today on a forum supporting FoxPro. It's hard to just give up and move on! Also many tech's are just a flash in the pan - here today and gone tomorrow. So which tech do you use. Will VueJS be here in two years. I don't know - but I sure like two way binding. I also like Electron a lot. The idea of replacing the UI library with Web tech sounds great to me. I always hated that it was not easy to change a buttons' background color or add radius corners. With Web tech it's easy. And with Electron I can use Web styling on a desktop. Yet Electron is only about three years old. And it wont matter if MS, google, and many other very large companies are using it today - it could be gone tomorrow.
Just my .02
Johnf
