Hacker News Reader

Comment by tsm | Hacker News Reader

Vanilla forms just GET or POST to some server endpoint with all of the <input>s passed in as query parameters. Frameworks (e.g., Rails) put some syntactic sugar on it, but that's really all that's happening. If the form submission contains invalid input, it's customary to return to the form page (with all the values already filled out) and show a server-generated message about what went wrong.

JS is absolutely not required for any of it.

View on HN

Thank you! it is actually enlightening :)

I think it's a little bit awkward to not use put, patch, delete... I wonder however if my server must follow the same technique, if not how to wire a delete endpoint to handle a form post and so on. I'll try to handle a form using only get and post sometime just to see how it works. Thank you!

Well you just made me feel old. For put/patch/delete you can just as easily wire different options to different URL's. We had URL's like /Foo/Delete?43. It may be awkward in a particular framework but it's about as simple as things get.

I've always hated put/patch/delete because it tends to result in data centric UI's instead of workflow centric ones.

Hmm now that you mentioned I realized I've seen this pattern before but I've never given it a thought. I'll definitely try it sometime, it seems to work pretty well. BTW sorry for make you feel old, it was not my intention haha

Here it is https://github.com/viniciusCamargo/express-crud-barebone here is my try on this approach to server requests. Any suggestion would be welcome! :)

I would really want to know more about this too, built a simple site without all that JS bloat

I'm glad for not being alone here :) I wish things were simpler...

I'm thinking about push some code to github this afternoon using these techniques with nodejs, if you want to I can send you a link to the repo ;)

Reply on news.ycombinator.com