3 ms·

That's just a symptom of Javascript being the entry-level language. You can be sort of productive without ever understanding how anything works. Where these fr

That's just a symptom of Javascript being the entry-level language. You can be sort of productive without ever understanding how anything works. Where these frameworks really come into their own is when you want to create reusable components and share them outside a team. jQuery did a good job with their plugins back in the day but Angular 2 (and React, and soon native Web Components) so that far better.

concerned_user 7y ago
I hear the tale of "soon native Web Components" for years and still none in sight yet. As far as I remember there are some attempts from Chrome and Mozilla but not sure I saw a real cross-platform spec out, so I stopped tracking the news around it really. Can you provide some references maybe?
- floatboth 7y ago
  https://caniuse.com/#feat=custom-elementsv1 https://caniuse.com/#feat=custom-elementsv1 https://caniuse.com/#feat=shadowdomv1 https://caniuse.com/#feat=shadowdomv1 v1 shipped with Chrome 53, Safari 10 and Firefox 63. (And there's a polyfill.) It's not "soon", it's very much "been in production for a while". A base class like LitElement https://lit-element.polymer-project.org https://lit-element.polymer-project.org is all you need to achieve a sort of "react-like" development style (components with unidirectional data flow) WITHOUT build tools() and WITHOUT dom diffing! :) () if you want to use npm dependencies instead of just plain files with a bundled version of lit, you still need to rewrite import paths, until https://github.com/WICG/import-maps https://github.com/WICG/import-maps becomes a thing at least. I wrote a tiny dev server that does that: https://github.com/myfreeweb/es-module-devserver https://github.com/myfreeweb/es-module-devserver
  - rxgx 7y ago
    Anyone else get a little excited about that Edge v75?!
ousta 7y ago
I hear everyday components but JSF was components, ASP.NET was components , Knockout was components. Explain to me what is the difference?

concerned_user 7y ago

I hear the tale of "soon native Web Components" for years and still none in sight yet. As far as I remember there are some attempts from Chrome and Mozilla but not sure I saw a real cross-platform spec out, so I stopped tracking the news around it really. Can you provide some references maybe?

floatboth 7y ago
https://caniuse.com/#feat=custom-elementsv1 https://caniuse.com/#feat=custom-elementsv1 https://caniuse.com/#feat=shadowdomv1 https://caniuse.com/#feat=shadowdomv1 v1 shipped with Chrome 53, Safari 10 and Firefox 63. (And there's a polyfill.) It's not "soon", it's very much "been in production for a while". A base class like LitElement https://lit-element.polymer-project.org https://lit-element.polymer-project.org is all you need to achieve a sort of "react-like" development style (components with unidirectional data flow) WITHOUT build tools() and WITHOUT dom diffing! :) () if you want to use npm dependencies instead of just plain files with a bundled version of lit, you still need to rewrite import paths, until https://github.com/WICG/import-maps https://github.com/WICG/import-maps becomes a thing at least. I wrote a tiny dev server that does that: https://github.com/myfreeweb/es-module-devserver https://github.com/myfreeweb/es-module-devserver
- rxgx 7y ago
  Anyone else get a little excited about that Edge v75?!

ousta 7y ago

I hear everyday components but JSF was components, ASP.NET was components , Knockout was components. Explain to me what is the difference?