3 ms·
Honestly, something like React/Vue has got to be as close as it gets to "The Final Paradigm". At this point, it's been a long time since I've seen a new paradig
by chrisco255 9y ago
Honestly, something like React/Vue has got to be as close as it gets to "The Final Paradigm". At this point, it's been a long time since I've seen a new paradigm that does anything vastly different or more productive and simple than JSX + React/Vue lifecycle & state hooks. Most of the new UI libs that come out (Glimmer, Marko, etc) seem to be heavily influenced by React and don't offer a giant leap in how UI is done.
I think there's plenty of more opportunities in state management, CSS management, application structure, tooling, and making those more simple, but generally I think the view layer is more or less solved.
- NeoBasilisk 9y agoIf you're still saying that in 4 years, then I'll believe you.
- nostalgeek 9y agoIt'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 9y 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)
- keithnz 9y agoI don't think so, I'm thinking it's all about to change . why? WASM. We now see languages targeting the browser, and the beginnings of front end frameworks being developed in traditionally backend languages. I think this is going to create quite a different landscape for the web world in the next 5 years. Different languages bring different approaches to problems.
- rmrfrmrf 9y agoNo reason why React couldn't be implemented in WASM. I'm less bullish than you are about WASM, though, since DOM interaction is going to be the bottleneck no matter which way you slice it.