Do we need a web API?
liaison.dev
Do we need a web API?
1–10 of 107 posts
Re: Do we need a web API?
#2https://news.ycombinator.com/item?id=21600859 seems related.
Re: Do we need a web API?
#3This 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'
Re: Do we need a web API?
#4>Sorry, this site requires JavaScript to be enabled.
For a flat blog post? Like, seriously?
Re: Do we need a web API?
#5CORBA called, they want their ideas back
Re: Do we need a web API?
#6I've used a similar concept about 10 years ago if anyone remembers Wicket[0], and personally really liked it. The challenge was the UI and state were all server side and difficult to keep memory usage down. I'd be interested in how this model works now that client side UI and state are much more capable.
Re: Do we need a web API?
#7>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.
Re: Do we need a web API?
#8CORBA called, they want their ideas back
Yup. Looks exactly like it. SOAP is not that different either.
Add: my PTSD from a few months with DCOM is acting up :)
Re: Do we need a web API?
#9CORBA called, they want their ideas back
Even in JS, the Meteor framework was basically created to implement this.
Except they actually implement things like validation, because as much as one may want to unify both environments, the reality is that exposing all your methods to the outside world may have some pitfalls, to put it mildly.
Re: Do we need a web API?
#10>Sorry, this site requires JavaScript to be enabled. For a flat blog post? Like, seriously?
I had to disable AdGuard to display it.