No post body was provided.
Ask HN: Front End Development 2022
11–20 of 22 posts
Re: Ask HN: Front End Development 2022
#12Front end dev here, formerly full stack. For moderate to high complexity apps, I would choose Next.js on Vercel for its incredible developer experience relative to either vanilla JS or React without Next. If you don't care about React (for its popularity) it might also be worth considering other frameworks. I would remove as much of the backend as possible and store whatever I could on the edge and use serverless fun…
Funny, this is my exact approach. Love it. Only comment, is that even if storing "dumb data" is the goal, we use Cloudflare KV, you still need some backend CMS or database to ensure some data integrity. So we build a simple bridge between the CMS/database and KV.
Re: Ask HN: Front End Development 2022
#13Front end dev here, formerly full stack. For moderate to high complexity apps, I would choose Next.js on Vercel for its incredible developer experience relative to either vanilla JS or React without Next. If you don't care about React (for its popularity) it might also be worth considering other frameworks. I would remove as much of the backend as possible and store whatever I could on the edge and use serverless fun…
Funny, this is my exact approach. Love it. Only comment, is that even if storing "dumb data" is the goal, we use Cloudflare KV, you still need some backend CMS or database to ensure some data integrity. So we build a simple bridge between the CMS/database and KV.
Do you use KV as a read-only cache, then, or?
Re: Ask HN: Front End Development 2022
#14Front end dev here, formerly full stack. For moderate to high complexity apps, I would choose Next.js on Vercel for its incredible developer experience relative to either vanilla JS or React without Next. If you don't care about React (for its popularity) it might also be worth considering other frameworks. I would remove as much of the backend as possible and store whatever I could on the edge and use serverless fun…
The Vercel CEO https://twitter.com/rauchg/status/1603965931293536257 and I would agree. Also, many others and I would leverage a few extras. Typescript is practically a given these days, preventing a huge class of compilation and runtime bugs. Along with TailwindCSS for much improved styling, and NextAuth for auth.
Hah, that was unexpected. Thanks for sharing.
And yeah, Next's built-in Typescript support is great. And not just TS, but dealing with the other parts of the buildchain that are traditionally a PITA to individually configure (the server, linter, bundler, package manager, etc.). Next sets it all up for you for ease of use and interop. It's beautiful.
Re: Ask HN: Front End Development 2022
#15A backend dev with minor FE exp here. 1. I would go with Vue. Because Vue is focused towards DX and pragmatism. It provides good defaults to start with and flexibility to go through less travelled paths should you need it. Part of the reason is that when I first tried react (in 2016), I couldn't get it to build. And setting up build tools was not easy. Vue can be used with a single script tag, so I was able to get it…
I also use Vue. It's got good docs, a decent amount of plugins, etc. But the main thing is that it doesn't make me use Jsx for HTML. Jsx in my opinion just creates ugly view files which are massively more complex and harder to read than they really should be.
Re: Ask HN: Front End Development 2022
#16Earlier quoted context omitted.
Funny, this is my exact approach. Love it. Only comment, is that even if storing "dumb data" is the goal, we use Cloudflare KV, you still need some backend CMS or database to ensure some data integrity. So we build a simple bridge between the CMS/database and KV.
Do you use KV as a read-only cache, then, or?
Mostly read-only, with ocassional writes when we update the database/CMS. The writes handled by a webhook which hits the Cloudflare worker upon any update. Workers is so fast, the data and website is updated in milliseconds. We use Vercel's on demand revalidation.
Honestly, the real revolution at Vercel with NextJs in my opinion is the ability to easily use Edge functions now in any NextJs project. It's strange to me how so few developers use this, and understand how powerful the Edge is with Cloudflare. Even at Vercel itself they are focusing on the App folder and React Server Components (RSC). But, if you store everything at Edge and use Edge functions, everything is so incredibly fast, and easy to hook up/maintain that all the tooling around RSC is entirely useless.
Re: Ask HN: Front End Development 2022
#17Earlier quoted context omitted.
Do you use KV as a read-only cache, then, or?
Mostly read-only, with ocassional writes when we update the database/CMS. The writes handled by a webhook which hits the Cloudflare worker upon any update. Workers is so fast, the data and website is updated in milliseconds. We use Vercel's on demand revalidation. Honestly, the real revolution at Vercel with NextJs in my opinion is the ability to easily use Edge functions now in any NextJs project. It's strange to me…
Well, edge functions have a really good case but costs have to be taken into consideration. We use them if the logic is unique to the app and access is minimal. Our backend handles the rest. This way we can control costs.
Re: Ask HN: Front End Development 2022
#18Earlier quoted context omitted.
Mostly read-only, with ocassional writes when we update the database/CMS. The writes handled by a webhook which hits the Cloudflare worker upon any update. Workers is so fast, the data and website is updated in milliseconds. We use Vercel's on demand revalidation. Honestly, the real revolution at Vercel with NextJs in my opinion is the ability to easily use Edge functions now in any NextJs project. It's strange to me…
Well, edge functions have a really good case but costs have to be taken into consideration. We use them if the logic is unique to the app and access is minimal. Our backend handles the rest. This way we can control costs.
The Vercel $20 plan comes with a million edge function invocations. Are they really that expensive at scale vs all the maintenance you have to do for a traditional backend?
Re: Ask HN: Front End Development 2022
#19A backend dev with minor FE exp here. 1. I would go with Vue. Because Vue is focused towards DX and pragmatism. It provides good defaults to start with and flexibility to go through less travelled paths should you need it. Part of the reason is that when I first tried react (in 2016), I couldn't get it to build. And setting up build tools was not easy. Vue can be used with a single script tag, so I was able to get it…
I also use Vue. It's got good docs, a decent amount of plugins, etc. But the main thing is that it doesn't make me use Jsx for HTML. Jsx in my opinion just creates ugly view files which are massively more complex and harder to read than they really should be.
JSX gives you a powerful way to describe your html. But template is easier and gives more opportunities for optimizationa.
I like that Vue has chosen to use templates as default and supports jsx for complex use case.
This way advanced use case can leverage the power of jsx while most common scenario can use html
Re: Ask HN: Front End Development 2022
#201. It depends on the product. For a landing page go with zero javascript since you want things to load blazingly fast. I like static site generators for this such as Jekyll. For simple websites (e.g. small web shops), you might be okay just serving HTML/vanilla JS through e.g. PHP or Python. For apps that need to be an app, my go-to framework is Angular. I know I’m in the minority here but its tooling has come a long way. The developer experience is stellar nowadays. For CSS: Tailwind, which finally made me productive in styling elements.
2. If you don’t know vanilla JS it’s best if you learn that first before thinking about any “stack” – I can recommend Eloquent JavaScript. After you get the hang of it, pick any stack that fits your problem and interests you, and start building. :)