HackerTrans
TopNewTrendsCommentsPastAskShowJobs

iobert

no profile record

Submissions

[untitled]

1 points·by iobert·last year·0 comments

Adding Messaging Functionality to AI Agents

twilio.com
1 points·by iobert·2 years ago·0 comments

AI in Software Development: Ready for the Pilot Seat?

twilio.com
2 points·by iobert·2 years ago·1 comments

Build a Photo Guest Book with WhatsApp

twilio.com
1 points·by iobert·3 years ago·1 comments

Comparing the Gatsby, Next, Nuxt, and Nest Open-Source JavaScript Frameworks

twilio.com
1 points·by iobert·4 years ago·1 comments

comments

iobert
·2 years ago·discuss
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.
iobert
·2 years ago·discuss
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.
iobert
·3 years ago·discuss
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.
iobert
·4 years ago·discuss
> 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.
iobert
·4 years ago·discuss
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.
iobert
·4 years ago·discuss
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.
iobert
·4 years ago·discuss
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/
iobert
·4 years ago·discuss
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
iobert
·4 years ago·discuss
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/
iobert
·4 years ago·discuss
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?
iobert
·4 years ago·discuss
Hi, I'm the author of the blog post and wanted to say that I completely agree with your statement. I picked these metrics because I find them very useful to explain the differences between the rendering options. I did not mean to say that every website needs to optimize for all of them.
iobert
·4 years ago·discuss
This blog post is for everyone looking for their new favorite JavaScript backend framework. A few months ago, I was precisely in this place and wanted to learn a new JavaScript backend framework.