3 ms·
It's funny to think retrospectively that something like Backbone.js absolutely did not solve view state management at all and people adopted it because it someh
by nostalgeek 8y ago
It's funny to think retrospectively that something like Backbone.js absolutely did not solve view state management at all and people adopted it because it somehow looked like Rails with big models, Angular.js misunderstood the issue completely with factories everywhere instead of a single dataflow.
The new paradigm would be the browser handling all that and there is no need for frameworks anymore. We are not there yet given how poor web component support is : https://caniuse.com/#search=web%20component https://caniuse.com/#search=web%20component
- 52-6F-62 8y agoI think you nailed it (though I think Jeremy Ashkenas and Mike Bostock and that NYT group are brilliant... especially working in the media space at a company that doesn't encourage that kind of work to put it mildly). I've had my whimsical entries into experimenting with Web Components, but they just haven't felt like they're quite there—ignoring the lack of support. They're workable, but I think design patterns surrounding current paradigms might need more readily addressed. As they are, you'd probably want a framework on top of Web Components to improve the semantics and just make working component state in generally less verbose. I have a hastily-written example here playing with them: https://robert-fairley.github.io/es6-webcomponents/ https://robert-fairley.github.io/es6-webcomponents/ (No repo, it's not worth it. Just check the source–it's short enough)