Skip to content

Comment on Is Mesop and Web Components the cure to Front-end fatigue?parent

Comments

Mesop's API is... interesting. It seems to replace all REST/CRUD/MVC abstractions with some kind of RPC,

Big shade of Towards a Modern Web Stack vibes, where someone guts everything that makes the web the web & attaches a completely non-web different world inside to move the flesh.

I have to admit, I don't think we have gotten a lot better about rest & operations/mutations & data-stores this decade. I'm far from ready to give up & start stubbing in rpc systems as we feel like it - that sounds deeply anti #rfc8890 -which is the holiest most spiritual tenant of the internet - but I do wish we at.least had worked on & tried to make stitching front & back end together over rest better, more visibly. Like GraphQL, I both want to purge this with fire, but I also appreciate the challenge; the bar should be raising!

And uh... yeah. On that other thing: hammering on a out front end fatigue is some weak-kneed reactionary bullshit, is extremely low road toxic-trash-talk culture shit. The front end has actually uhh gotten good? Do like everyone else & use vite & pick any of the really good ecosystems that've been around for a long time (React, Svelte, Vue, Alpine, maybe Qwik or Solid)

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.