Re:Front-of-the-Front-End and Back-of-the-Front-End Web Deve...
by hootbootscoot on Tuesday February 16, 2021 @09:24PM
(#26161877)
Apollo client? you mean where the Meteor Dev team suddenly leaped to when it dawned upon the world that Mongo as a primary-store and a bizarre architecture that let you walk away with exactly one artifact towards your inevitable rewrite? (moustache templates!) was probably not going to take-off in a big way.
Awesome integration and polished docs etc.
Mini-mongo and pub-sub with websockets always for everyone? mmmm it ran rather slowly...
Put that at 30 degrees North North-West and integrate "what is good for a FAANG may bankrupt me and not provide foreign keys" lol..
Nothing against VC, but lets separate busy-work trends that mega-corps use in trench warfare of attrition (Google has more developers than you do.) from productivity tools.
GraphQL? I'd probably Postgrest if I were a one-human front-end/SPA shop
[ Parent
| on HN ]
Re:Front-of-the-Front-End and Back-of-the-Front-End Web Deve...
by ervine on Tuesday February 16, 2021 @09:31PM
(#26161934)
I mentioned it as an example of one of the more popular solutions available. Yes, it's complicated and requires a deep understanding of what it's doing - and even then it has warts that you have to work around - but we're talking about situations this complexity is necessary for the desired UX.
Whether the user actually desires this experience is another question entirely...