3 ms·
If we see a return to "hypermedia" it won't be wholesale, but rather in the form of a static site generator that does the 80% work and is easy to extend the res
by CuriouslyC 5y ago
If we see a return to "hypermedia" it won't be wholesale, but rather in the form of a static site generator that does the 80% work and is easy to extend the rest of the way. Something somewhere between Svelte and Gatsby. The react component model and JSX style bracketed DSLs both have a lot of traction, the main issue is the amount of groundwork and glue needed to do simple things with them.
- recursivedoubts 5y agoi don't agree at all i think it will rather be in non-javascript technologies with strong existing hypermedia infrastructure again, like rails, django, etc the front-end component model is anti-RESTful and is really a mechanism for handling the complexity of the current client-server approach, it becomes significantly less important as hypermedia is re-embraced
- CuriouslyC 5y agoI think RESTful APIs will die before component based interfaces do. Component based UI has been a thing for like 30 years outside the web dev space, and GraphQL/post-based RPC APIs solve a lot of problems and can be derived cleanly from a database schema or functional modules. Hypermedia also doesn't play well with offline-capable applications, which limits its use cases.
- recursivedoubts 5y agothe component problem, in as much as it is one that can't be dealt with via just standard template includes, can be solved server side and offline-capable isn't a huge percentage of web apps we just disagree, the future will tell us who's right
- BuckRogers 5y agoI think you’re both wrong and the future belongs to platforms that compile to web assembly.
- recursivedoubts 5y agocould be!