As it stands, we now have a relatively stable release-cycle for ECMAScript and that helps clear some of the fog. We can now safely begin writing our JS using ES2018 and allow a tool like Babel to either polyfill or compile down to ES5 for older browsers. We are even seeing ways of compiling an ES5 version of your script and only loading if it if needed, if the browsers can support ES2018 it’ll just get ES2018.
I think native web components are likely stable enough we can now begin using them instead of relying on a React-style setup. Libraries like polymer have basically said, “We just want people to use native web components and understand our product will essentially just map to that and eventually we’ll be obsolete” which is good to hear.
I think in the next 3 years we start to see the codebase truly begin to split the server-side code from the client-side code. This will make maintenance easier, allow cleaner code, faster iterations, and better prepare us to handle FHIR and in-patient use-cases.
Talk is cheap though, and so I’ll likely write up a module using the ideas here. Something simple that devs can look at and better understand. I also imagine we’ll end up with our typical Apache/Nginx based PHP server as well as a node server in the coming years.
< /novel >