Hacker Newsnew | past | comments | ask | show | jobs | submit | iobert's commentslogin

As a developer, I was eager to explore the AI tools available today to see how they can accelerate the development process. So, I've spent the last few months digging into the realm of AI tools for developers. I have tested, fiddled with, and tweaked a variety of these tools. Today, I'll share some highlights I encountered.


I'm not sure why you're all complaining. API is literally in T-Pain (3/5). I couldn't think of a better act.


I used the WhatsApp API to build a photo-sharing app for my friend's wedding with virtually no entry barrier and a close-to-perfect onboarding experience.


> The author is seriously suggesting Next.js to build a company website.

Hi, I'm the author :). I wanted to highlight this recommendation has the modifier "If you'd like to learn something new". This very subjective recommendation is solely based on the exciting mix of rendering options, the vast popularity, and my preference for JS and React.

You're spot-on when you emphasize that there are web applications that are a different beast anyway and websites that run perfectly fine with a CMS in the background.


I agree that the lines get more blurry the closer you look, "is it still SSG or already a hybrid approach when it contains localized strings?" What I meant to describe in the post is the conceptual difference to understand the purpose of the rendering frameworks better.


Makes sense, the problem is that rendering frameworks are lagging behind the current understanding of server-side rendering, Next 13 is the only exception I know


You're right, thanks for pointing this out. I'm the author; I updated the graphic to split based on the framework's purpose, "pure backend" vs. "focus on rendering". I hope this is clearer now.


I definitely have SvelteKit on my radar, but I wanted to focus on the top five frameworks this time. Maybe SvelteKit will make it in the 2022 results :) https://stateofjs.com/


Haha, this title was actually suggested by a friend of mine when I did the research for this post. But then I found out that someone already created an npm package with this name, but the project seems to be dead :D

https://www.npmjs.com/package/nust


Yes, I only focused on the top five frameworks :) I just checked and Sails, once on place five, fell out of the named ranking in 2019 https://2019.stateofjs.com/back-end/


I don't blame you a bit, you've got to make the scope of your writing relevant to the audience and the moment... just more surprised that Sails seemed to have its moment and then disappear just as quickly, especially given the chat in a thread like this one on HN where there are apparently many people curious if not outright looking for a full-stack js framework.

I attempted to start a (personal, but with commercial aims) project using Nuxt about three weeks ago, as I'd had good experiences with it in the past. It's not been at all fun - whereas with Nuxt2 it felt like I could get up and working quickly, it's been weeks worth of playing whack-a-mole fixing errors. Settled back to Vue3 and got up and running in a few hours.

Sveltekit certainly looks interesting. I've tried to get excited about React / Nextjs in the past, but while the concept feels solid, I guess I've always felt like Vue was a better implementation of the concept.


Absolutely! And it doesn't help that each framework has 2-3 ways to be spelled: Is it nest, Nest, or NestJS vs Next or NestJS?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: