Live data from Hacker News

Build your own web framework

vercel.com

1–10 of 155 posts

Re: Build your own web framework

#5
This is a nice overview of modern front-end development but I'm constantly disappointed with what 'web framework' means in node-land. None of these things are strictly necessary when building a web app but authz/authn, user management, databases, server-side logic vs client-side logic, are pretty much always needed. When I see the phrase 'web framework' these are the things I am interested in seeing and they all seem to be treated as afterthoughts in the node community. Most tutorials either point you to paid/proprietary services or to really bad local solutions like back in the hotscripts days of php. If you google 'node user login' the first tutorial has you storing a password in plain text and checking the password with the equivalent of '=='. The first result when googling the same for php, python, and ruby all returned solutions using a hash.

Re: Build your own web framework

#6

not sure how this differs with AWS, you can do more at less cost than Vercel

I'd say give it a shot. Vercel has a much more reasonable Free Tier, was insanely easy to use and incredibly fast. I had my changes pushed to prod from github in I haven't built anything big on Vercel, but from my test drive, I'd be happy to use them in the future, and this is coming from someone who works AT the A in AWS. AWS does NOT make the easy things easy; though you are right, it does make the "more" possible, but it all depends on what you're optimizing.

Re: Build your own web framework

#7
post #2

I'm struggling with the idea that React is a primitive used to build a Web Framework.

React is "just" a library, it doesn't give you everything you need to build out a full-stack or framework.

For example, see Clojure's Luminus: https://luminusweb.com/

You have to dig down deep to find where React is.

Re: Build your own web framework

#8
post #5

This is a nice overview of modern front-end development but I'm constantly disappointed with what 'web framework' means in node-land. None of these things are strictly necessary when building a web app but authz/authn, user management, databases, server-side logic vs client-side logic, are pretty much always needed. When I see the phrase 'web framework' these are the things I am interested in seeing and they all seem…

Its pretty hard to trust a lot of the eng content on the web right now; so much blogspam, self promo stuff from frankly underqualified people who are trying to build up a profile to get hired.

Somehow I still don't feel that way about StackOverflow. Google and random results though... yikes.

Re: Build your own web framework

#9

not sure how this differs with AWS, you can do more at less cost than Vercel

AWS is overwhelming for most of Developers. Also vercel is focusing on ease of deployment for front end, it is also zero config, you can just deploy nextjs, react, svelte, remix apps in matter of minutes. Which is impossible with AWS

Re: Build your own web framework

#10
post #2

I'm struggling with the idea that React is a primitive used to build a Web Framework.

You could swap out React here for another solution (e.g Svelte) and it would mostly read the same. The Build Output API[1] mentioned is how React, Vue, Svelte, and their "metaframeworks" run on Vercel today.

[1]: https://vercel.com/blog/build-output-api

Post reply on HN