11–20 of 107 posts
This is an interesting project, but there are very good reasons for having API's. Its just about is it the right tool for the job. I don't like their comment : 'They are just a necessary evil so the frontend can communicate with the backend'
The problem of serialization, deserialization, versioning, endpoint design... They aren't an artifact, they're intrinsic to how Web apps are built.
But yeah, for small projects I think this could be really neat.
Do you need a web API? If you need to serve data to a web frontend then yes. Pick your poison, but you will have one. You can do a little dance that makes it look like you don’t have one, but in my experience that usually turns out worse than just writing the damn thing.
This is an interesting project, but there are very good reasons for having API's. Its just about is it the right tool for the job. I don't like their comment : 'They are just a necessary evil so the frontend can communicate with the backend'
I'm sympathetic to your position, but right now your comment doesn't carry much information. Why are they the right tool for the jobs? Which reasons are those?
If your backend only communcates with an SPA and nothing else, then yup, this is a good tool for that job.
- and thank God gRPC never took off the way Google hoped, it was pure ego and politics like the majority of OSS projects these days (in the web world)
>Sorry, this site requires JavaScript to be enabled. For a flat blog post? Like, seriously?
welcome to the web 2.0 cooming soon: web assemply web 3.0 which (I fear) might feel a lot like flash web pages from the early 00s. I hope I'm wrong.