I absolutely love Adonis. I have hands down fallen in love with it after a year of using NestJS. Nest was a miserable pain and its DI got in my way time after time. Testing was terrible, CLI was half-assed, and it just felt like a weight. With Adonis, I fell back into my Rails-based shoes and felt at home again. I haven’t used Rails in almost 7 years since I choose the NodeJS road, and no framework could scratch that itch. But with Adonis, every step has simply been Quality of Life. The DI barely exists, the CLI is feature rich, the Lucid database solved my Prisma woes, and the lack of decorators has been a godsend. For reference, I built a frontend application and backend for a crisis line call center. I’ve had to tackle with Cisco Broadworks and a 500+ page black and white pdf. I’m not an expert, but from production level experience I would never chose Nest over Adonis.
To me there are only 2 node backend frameworks: Nest (with S!) and Adonis. The rest we can't even call framework as they're too scared to be opinionated.
@@gamingwolf3385 he means, "side hustle apps or projects that generates income etc". You might as well check "Indie Hackers Podcast" that's super inspirational from other indie devs
Daniel, that's a very interesting take on Adonis. I've e been looking for alternatives to NextJS for the same reasons you've mentioned and after this video I'm definitely going to give adonis a try!
I think Nest should be a contender as well. It kinda tries to strike a balance between being modular and being batteries-included. But I wonder why it's not part of the conversation for this video
I think Nest.js is actually way more flexible than Adonis.js, for example: implementing something like Clean Architecture would be fairly more complicated in Adonis than it's for a Nest.js project. In other hand, I would say Nest.js is not at all batteries included (apart from DI and a couple of decorators), if you want to implement something like Authentication or even DB connection you will have to spend a good amount of time configuring this yourself, unlike Adonis.
Nest is probably very good but my experience is that I spent more time configuring, setting up packages and trying to understand how to work with their DI system than I did developing my application. Really not a fan of the Angular style modules approach. That's also why I think Adonis is awesome, it lets you just work on the stuff you care about. And the first party packages are insanely great.
there are some missing built-in packages also for Nest Js if we compare it to Fullstack Framework like Laravel or Rails. Bcz Nest js doesn't have any built-in template engine or built-in ORM.
NextJS has been my default choice, but I'm not a fan of having to constantly glue all kinds of third-party libraries just to get standard backend functionality. Pretty much the only reason I haven't built any project in Laravel/Rails/Django is because I prefer to use TypeScript. For the static typing and because it keeps the entire project in the same language, which makes stuff like sharing types and validation logic between frontend and backend easier. So Adonis + Inertia looks like a killer combo! It seems to have everything I'm looking for in a web framework. I guess the only downside seems to be the lack of a huge community compared to the other frameworks I mentioned, but hopefully it'll grow.
Eventually, at some point, you'll grow to understand why scripting languages are the best for building web applications (both apis and frontends). Took me a while. I totally get the thing about types... but at the end of the day, you should catch undefined / typos in your unit tests / e2e tests. I know people tend to think that just by using languages like typescript, rust or such you "can" avoid unit tests, and that's something even a certain tech influencer says! but you should never avoid writing tests, even if you're using a supposedly type-safe languages... Also, More often than not, tests serve as documentation for maintainers. TBH Adonis is pretty good, but JS/TS is still a yank language, I'd rather code php / ruby / elixir. Best wishes in your journey
@@MateoC-f4n I more or less agree. I only use React/Next.js for the very frontend if at all. Despite all of the frameworks, boilerplates, and 3rd party platforms available in JS...it's still far easier to get an MVP out in a shorter amount of time with Rails or Django. Then, there's also the constant flood of libraries, and frameworks. Which is a completely different issue altogether.
Laravel could be a great fit for you! With PHP 8+, Laravel supports static typing, which helps catch errors early and improves code quality. Additionally, Laravel’s rich and well-documented ecosystem provides a variety of packages that cover everything from authentication to API integration, reducing the need to glue together third-party libraries for basic functionality. This could streamline your development process and offer a robust, cohesive framework for your projects.
NESTjs (not next) is also very solid and complete I've used it in production twice. only downside is it's too java-like, but it's been around for a while and mature. but i agree Adonis is closer to Rails. while Nest is closer to angular/spring boot
New sub for the cat 😺 Adonis is great, the maintainers put a lot of effort into adding new stable packages when the launch the version 6 👌 I was a bit worried due to the main mantainer is also building Medusajs, but he's keeping the quality
I've been using NestJS in my projects since your video on testing JavaScript frameworks where you recommended it. It's pretty solid tbh. It reminds me of Java, which I currently work with. I keep struggling to choose a frontend framework to work btw
I hope this whole JS vs Rails and Laravel discourse leads to more people shining a light on Adonis and similar frameworks. Will hopefully lead to increasing popularity for these frameworks and maybe some people even contributing.
@@DanielBergholz its somewhat scary to know they built a framework not for a product of themselves but for hobby. or am I wrong? couldnt find their company/products
@@marcelaodev Good question, feel free to ask them on Twitter, they are very active there. AFAIK they are not shipping products like DHH on 37signals. They enjoyed the laravel/rails experience and tried to replicate that for adonis. Virk (the creator) is working full time on adonis, but it seems the other 3 core members are also working on other stuff, probably using adonis
Thank you for these very inspiring words! I will seriously try Adonis. You explain that we should avoid using next.js or prisma because they are maintained by a company that wants to make money, but what about Angular/Google and React/Facebook?
I agree also the data sharing between modules is also very hard in nextjs compared to other frameworks. so i've abandoned it. it makes me hate reactjs!! thanks for the video!
Very insightful and helpful, thank you. To make sure I'm understanding the entirety of your position, you propose that JS-centric teams / devs should consider adopting Adonis; but for those not attached to JS, then Rails / Django / Laravel (or, your personal preference, Phoenix) would still be preferable. Am I understanding your position correctly? I'm a semi-n00b researching the different paths at my disposal, before I invest the time and energy. On a related note, I'm seeing objections to Laravel claiming that its release cycle introduces breaking changes every 12 months. ("Breaking", i.e., lacking backward compatibility / inability to access new features from old code.) In this way, it seems to me that Laravel wouldn't be much different (in this regard) than the maintenance nightmare that has become the JS ecosystem. Or is this just a reality of working with web frameworks in general; i.e. that one must be committed to rewriting / refactoring code on an annual basis? I value your insights. Peace.
Sensible youtuber that is saying what I have been posting on different forums since 2016, we need stability in JS ecosystem not yet another framework. btw I have been using Laravel since 4.2 and prior to that I was a JSP guy, I liked laravel so much that I ditched Java in the backend and moved to laravel. Loved the express when it first came but it was good for a small project. I have worked with large enterprise who have used express for their monolith architecture with react. It was horrible experience, loading data on datagrid with huge amount of data sets and performing ACL was a nightmare. Upgrading to newer node package always broke something, it was so bad that in the end we were only able to fix bugs in existing architecture due to libraries being abandoning and no longer being pulled from npm. We were not able to ship any new feature and then later that product got acquired. I wouldn't recommend using JS ecosystem as a whole in backend and frontend from my personal experience.
Adonis seems very helpful, I didn't know it. I liked so much when I knew there is a solution like Inertia for Laravel, and I thought “it'd be great it was possible to do that in a true js framework“ (or a .NET one, as well, once I love C# 😂), and reading Adonis' documentation I got very happy to see that we can use Inertia with them. It sounds relieving to know we have a js framework that try to do the same Laravel do: construct monolith with maestry. I'll probably git it a try, soon. I only doesn't like this: I REALLY wanted to try Remix after your last video about it saying they're about to release new versions by the name of React Router v7 and do the best for not break oldy applications. Now I don't know at all what do I try first. 😂 But that's good. Thanks for these two videos, about Remix and Adonis.
I think that one module they really need to get super power - admin panel :) it can take pretty much time and having ready-made consturctor would be great
Rails + InertiaJS would be the perfect killer combination for me. There’s almost no recent tutorial on Rails + Inertia (React+TS) and vite_ruby. Untapped market 😂
Hey Daniel :) Great video like the others 🙏 I was wondering, what you think about NestJS then? I'm having this conversation with my tech Lead, about wether we should use Nest or Adonis for our projects. We've been using NestJS so far, and as much as I want to use Adonis I have to admit Nest feels pretty solid and reliable. The doc covers almost every use case in great details, it is open source and heavily sponsored, so it feels like its not really likely to die. My gut feeling tells me that I like the adonis DX more, but I can't argue with the fact that NestJS is more in place today ^^ It almost feels like Symfony and Laravel at some point when I was doing PHP a long time ago, when Symfony was the big bulky and not so flexible framework and Laravel was the flexible one with a good DX. How do you feel about it ? :) Anyone is welcome to argue this point in the comment, I would love to have your feedback on this !!
Use Nest. I wouldn't trust Adonis on a large application. Its maintained by one guy iirc or a very small team and its far less popular than Nest. So if you get stuck you will have a harder time finding a solution. For instance lets say there is a bug in their ORM, you are less likely to find a solution for it compared to other more popular ORMs and also you won't be able to swap it out. Use Adonis for your side projects until it becomes more popular.
@@stumpyjoe6385 Great question! I made this video for the JS fanboys that don’t want to learn a new language. But if you don’t mind learning Ruby, you should 100% try Rails!
The only problem is that even if AdonisJS is great, companies usually don't use it. Also, I'd rather use Django, Rails or Phoenix for personal projects anyway precisely to avoid having to code in Javascript.
I'm recommending Adonis only for the people who cannot stop using JS for whatever reason. Personally, I use Elixir + Phoenix for all my side projects, I'm burned out from JS completely
Next backwards compat has been inexcusable. Love the ergonomics though.... This is definitely got my eyebrow raised. Been rolling my own for a while...
I love Nest.js! I used it in the past, it's really good. However, in this video, I'm focused only on Rails-like frameworks, and Nest doesn't sell itself as the Rails of JavaScript like Adonis
@@projetoventuraas far as I know, Nestjs doesn't allow you to build templates to render pages to a client. I think you can only use it as an HTTP API (+ Web Sockets and RPC)
Adonisjs is a amazing framework, but the fact that everything is build in house scare me as fuck. Because if Adonis die basically I will have to rewrite all my source code
Excellent introduction, great video content. The reason I didn't like Adonis was because they building things by their own, but when they make abstraction and allow to use third package, it can be good. I prefer nestjs haha, but it's good to know about these things.
I personally haven't had a major issue with next.js since using it for 7yrs (I don't normally use too many packages so things don't break). I agree it's now changing too much and getting over-engineered. I think the vercel team now have too many resources to ruin an already good product. With that said, I think most js devs use way too many libraries than its necessary instead of the web platform. You don't have to use everything you see on RUclips by influencers. If you write nextjs the idiomatically vercel way, you shouldn't have an issue. I like Adonis too. I would say it's more like Laravel. Almost like someone decided to build a laravel clone. I've maintained laravel in a previous job and it's my favorite fullstack framework.
Many cloud services have nodejs libraries so I don't think it's going anywhere. Nothing wrong with JavaScript on the backend. It's the most productive language, it's among the most well supported. Rich ecosystem. Just write good code and don't over complicate things
Eu já tinha ouvido falar desse framework uns anos atrás, mas sempre o pessoal que falava, falava com um pé atrás sobre o framework, mas eu mesmo nunca dei uma change. Talvez experimente.
Continue with English please😁!
I absolutely love Adonis. I have hands down fallen in love with it after a year of using NestJS. Nest was a miserable pain and its DI got in my way time after time. Testing was terrible, CLI was half-assed, and it just felt like a weight. With Adonis, I fell back into my Rails-based shoes and felt at home again. I haven’t used Rails in almost 7 years since I choose the NodeJS road, and no framework could scratch that itch.
But with Adonis, every step has simply been Quality of Life. The DI barely exists, the CLI is feature rich, the Lucid database solved my Prisma woes, and the lack of decorators has been a godsend.
For reference, I built a frontend application and backend for a crisis line call center. I’ve had to tackle with Cisco Broadworks and a 500+ page black and white pdf. I’m not an expert, but from production level experience I would never chose Nest over Adonis.
To me there are only 2 node backend frameworks: Nest (with S!) and Adonis.
The rest we can't even call framework as they're too scared to be opinionated.
Agree 100%, these are the only real frameworks for Node, the rest are just a bunch of ultra low level libraries
Just started learning after your last video. Liking it so far
the adonis docs is deeply impressive, would use it to build my next indie project
What do you mean by indie project ?
@@gamingwolf3385 he means, "side hustle apps or projects that generates income etc". You might as well check "Indie Hackers Podcast" that's super inspirational from other indie devs
@@gamingwolf3385 it means independent project -- like a project made by an independent sole developer.
Fico feliz de ver o canal do Daniel alcançando uma audiência internacional :). Sucesso cara!
Muito obrigado 🚀
Daniel, that's a very interesting take on Adonis. I've e been looking for alternatives to NextJS for the same reasons you've mentioned and after this video I'm definitely going to give adonis a try!
nicee, it's been a while since I have watched your videos, it is good to see you making videos in English as well. congrats and keep up this format!
Tamo junto! Thank you!
Yeah you convinced me. I'm trying it in my next personal project
I think Nest should be a contender as well. It kinda tries to strike a balance between being modular and being batteries-included. But I wonder why it's not part of the conversation for this video
I believe it's not flexible enough?
Nest is mainly targeted for backend only unlike frameworks like Adonis, Laravel which comes with full stack features out of the box
I think Nest.js is actually way more flexible than Adonis.js, for example: implementing something like Clean Architecture would be fairly more complicated in Adonis than it's for a Nest.js project. In other hand, I would say Nest.js is not at all batteries included (apart from DI and a couple of decorators), if you want to implement something like Authentication or even DB connection you will have to spend a good amount of time configuring this yourself, unlike Adonis.
Nest is probably very good but my experience is that I spent more time configuring, setting up packages and trying to understand how to work with their DI system than I did developing my application. Really not a fan of the Angular style modules approach. That's also why I think Adonis is awesome, it lets you just work on the stuff you care about. And the first party packages are insanely great.
there are some missing built-in packages also for Nest Js if we compare it to Fullstack Framework like Laravel or Rails. Bcz Nest js doesn't have any built-in template engine or built-in ORM.
NextJS has been my default choice, but I'm not a fan of having to constantly glue all kinds of third-party libraries just to get standard backend functionality. Pretty much the only reason I haven't built any project in Laravel/Rails/Django is because I prefer to use TypeScript. For the static typing and because it keeps the entire project in the same language, which makes stuff like sharing types and validation logic between frontend and backend easier. So Adonis + Inertia looks like a killer combo! It seems to have everything I'm looking for in a web framework. I guess the only downside seems to be the lack of a huge community compared to the other frameworks I mentioned, but hopefully it'll grow.
Right on! Agree 100%, the only problem right now is the small community. But Adonis + inertia + react seems a killer combo
Eventually, at some point, you'll grow to understand why scripting languages are the best for building web applications (both apis and frontends). Took me a while.
I totally get the thing about types... but at the end of the day, you should catch undefined / typos in your unit tests / e2e tests. I know people tend to think that just by using languages like typescript, rust or such you "can" avoid unit tests, and that's something even a certain tech influencer says! but you should never avoid writing tests, even if you're using a supposedly type-safe languages... Also, More often than not, tests serve as documentation for maintainers.
TBH Adonis is pretty good, but JS/TS is still a yank language, I'd rather code php / ruby / elixir.
Best wishes in your journey
"but I'm not a fan of having to constantly glue all kinds of third-party libraries just to get standard backend functionality"
This.
@@MateoC-f4n I more or less agree. I only use React/Next.js for the very frontend if at all. Despite all of the frameworks, boilerplates, and 3rd party platforms available in JS...it's still far easier to get an MVP out in a shorter amount of time with Rails or Django.
Then, there's also the constant flood of libraries, and frameworks. Which is a completely different issue altogether.
Laravel could be a great fit for you! With PHP 8+, Laravel supports static typing, which helps catch errors early and improves code quality. Additionally, Laravel’s rich and well-documented ecosystem provides a variety of packages that cover everything from authentication to API integration, reducing the need to glue together third-party libraries for basic functionality. This could streamline your development process and offer a robust, cohesive framework for your projects.
I like your honesty. And I am considering it.
started playing with adonisjs after you mentioned it in another video. liking it so far
NESTjs (not next) is also very solid and complete I've used it in production twice. only downside is it's too java-like, but it's been around for a while and mature. but i agree Adonis is closer to Rails. while Nest is closer to angular/spring boot
Adonis is completely underrated!
New sub for the cat 😺
Adonis is great, the maintainers put a lot of effort into adding new stable packages when the launch the version 6 👌 I was a bit worried due to the main mantainer is also building Medusajs, but he's keeping the quality
I think mongodb support and built-in task scheduler are missing part in Adonis js. if we have it, it would be great
I've been using NestJS in my projects since your video on testing JavaScript frameworks where you recommended it. It's pretty solid tbh. It reminds me of Java, which I currently work with. I keep struggling to choose a frontend framework to work btw
Nest is awesome as well!
NestJs + Angular is a good combo. They have the same structure
@@RafaelAmaral93 My problem with Angular is the lack of UI libraries. The only one I've seen that is decent is PrimeNG
Nestjs is a real pleasure to use, solid, scalable. However, the learning curve may be difficult at first.
I hope this whole JS vs Rails and Laravel discourse leads to more people shining a light on Adonis and similar frameworks. Will hopefully lead to increasing popularity for these frameworks and maybe some people even contributing.
I don't feel any more safer with a community open source than a startup open source. just the same feeling
Yeah it's a personal preference to be honest. Some people also don't like the fact that Adonis are 4 (almost) full time OSS developers
@@DanielBergholz its somewhat scary to know they built a framework not for a product of themselves but for hobby.
or am I wrong? couldnt find their company/products
@@marcelaodev Good question, feel free to ask them on Twitter, they are very active there. AFAIK they are not shipping products like DHH on 37signals. They enjoyed the laravel/rails experience and tried to replicate that for adonis. Virk (the creator) is working full time on adonis, but it seems the other 3 core members are also working on other stuff, probably using adonis
They have been there since 9 years 2015 they have a huge community in discord. If u say like this Google killed many products too
I guess, we should have more Miguel in future videos🐈❤
Don't worry, he is going to show up A LOT in future videos 😅
Thank you for these very inspiring words! I will seriously try Adonis.
You explain that we should avoid using next.js or prisma because they are maintained by a company that wants to make money, but what about Angular/Google and React/Facebook?
Wasp is a startup, most of them go bankrupt someday. Google and Facebook are different, I feel extremely comfortable having them backing a framework
Bonus points for having a cat named Miguel on camera! 🐈
He is going to appear a lot more in the future videos 😂, he loves doing this
@@DanielBergholz Looking forward to that! 😄
I agree also the data sharing between modules is also very hard in nextjs compared to other frameworks. so i've abandoned it. it makes me hate reactjs!! thanks for the video!
Very insightful and helpful, thank you. To make sure I'm understanding the entirety of your position, you propose that JS-centric teams / devs should consider adopting Adonis; but for those not attached to JS, then Rails / Django / Laravel (or, your personal preference, Phoenix) would still be preferable. Am I understanding your position correctly? I'm a semi-n00b researching the different paths at my disposal, before I invest the time and energy.
On a related note, I'm seeing objections to Laravel claiming that its release cycle introduces breaking changes every 12 months. ("Breaking", i.e., lacking backward compatibility / inability to access new features from old code.) In this way, it seems to me that Laravel wouldn't be much different (in this regard) than the maintenance nightmare that has become the JS ecosystem. Or is this just a reality of working with web frameworks in general; i.e. that one must be committed to rewriting / refactoring code on an annual basis?
I value your insights. Peace.
The sails squad might get upset about being overlooked :p
Migueeeel we need more Miguel
Sensible youtuber that is saying what I have been posting on different forums since 2016, we need stability in JS ecosystem not yet another framework. btw I have been using Laravel since 4.2 and prior to that I was a JSP guy, I liked laravel so much that I ditched Java in the backend and moved to laravel. Loved the express when it first came but it was good for a small project.
I have worked with large enterprise who have used express for their monolith architecture with react. It was horrible experience, loading data on datagrid with huge amount of data sets and performing ACL was a nightmare. Upgrading to newer node package always broke something, it was so bad that in the end we were only able to fix bugs in existing architecture due to libraries being abandoning and no longer being pulled from npm. We were not able to ship any new feature and then later that product got acquired. I wouldn't recommend using JS ecosystem as a whole in backend and frontend from my personal experience.
Adonis seems very helpful, I didn't know it. I liked so much when I knew there is a solution like Inertia for Laravel, and I thought “it'd be great it was possible to do that in a true js framework“ (or a .NET one, as well, once I love C# 😂), and reading Adonis' documentation I got very happy to see that we can use Inertia with them. It sounds relieving to know we have a js framework that try to do the same Laravel do: construct monolith with maestry. I'll probably git it a try, soon.
I only doesn't like this: I REALLY wanted to try Remix after your last video about it saying they're about to release new versions by the name of React Router v7 and do the best for not break oldy applications. Now I don't know at all what do I try first. 😂 But that's good. Thanks for these two videos, about Remix and Adonis.
After a long time fighting with js frameworks and putting together stacks, i finally gave up and went with adonis 😅 im never look back
really liked your takes :)
Bro, im also a daniel, software developer e brasileiro. Im impressed to find you, ngl
Da hora mano! Nice!
What is Adonis' story for building isomorphic apps? Without addressing that, the comparison doesn't seem fair since this is the main draw of Next
Hi, you would rock if you could your last 6 natives videos make in ENG. Good content!
I was seriously considering that 👀
@@DanielBergholz Please do!
ORM is very important in web dev. That’s why I am sticking with Django. I will try lucid orm. It seems promising!
I think that one module they really need to get super power - admin panel :) it can take pretty much time and having ready-made consturctor would be great
They need more adoption and supporters to be able to afford creating an admin panel, it's a lot of work
@@DanielBergholz yep, I totaly agree
you can probably adapt most of the admin dashboards made in react / nuxt to adonis fairly easy.
@@MateoC-f4n still a lot of work
Rails + InertiaJS would be the perfect killer combination for me. There’s almost no recent tutorial on Rails + Inertia (React+TS) and vite_ruby. Untapped market 😂
I think there is an official package for inertia integration on Rails if I'm not mistaken
what are the products that have been shipped with Adonis? missed that in video
Isn't Nest in this group of tecnologies, what do you think about it?
Nest is awesome! I haven't mentioned it in this video because I'm only talking about Rails-like frameworks
Hey Daniel :) Great video like the others 🙏
I was wondering, what you think about NestJS then? I'm having this conversation with my tech Lead, about wether we should use Nest or Adonis for our projects.
We've been using NestJS so far, and as much as I want to use Adonis I have to admit Nest feels pretty solid and reliable. The doc covers almost every use case in great details, it is open source and heavily sponsored, so it feels like its not really likely to die.
My gut feeling tells me that I like the adonis DX more, but I can't argue with the fact that NestJS is more in place today ^^
It almost feels like Symfony and Laravel at some point when I was doing PHP a long time ago, when Symfony was the big bulky and not so flexible framework and Laravel was the flexible one with a good DX.
How do you feel about it ? :)
Anyone is welcome to argue this point in the comment, I would love to have your feedback on this !!
Use Nest. I wouldn't trust Adonis on a large application. Its maintained by one guy iirc or a very small team and its far less popular than Nest. So if you get stuck you will have a harder time finding a solution. For instance lets say there is a bug in their ORM, you are less likely to find a solution for it compared to other more popular ORMs and also you won't be able to swap it out. Use Adonis for your side projects until it becomes more popular.
the major of js frameworks die because most of them lack the financial support to keep them going, being a startup actually helps with that
Mano, você oferece algum tipo de mentoria?
Polymorphic association is missing
Cheers from Asia, continue with English
This may be a dumb question, but if you're looking for a backend framework that matches the Rails experience, why not use Rails?
@@stumpyjoe6385 Great question! I made this video for the JS fanboys that don’t want to learn a new language. But if you don’t mind learning Ruby, you should 100% try Rails!
people that use js on the server use it specifically for the fact it's not rails or php.
The only problem is that even if AdonisJS is great, companies usually don't use it. Also, I'd rather use Django, Rails or Phoenix for personal projects anyway precisely to avoid having to code in Javascript.
I'm recommending Adonis only for the people who cannot stop using JS for whatever reason. Personally, I use Elixir + Phoenix for all my side projects, I'm burned out from JS completely
Next backwards compat has been inexcusable. Love the ergonomics though.... This is definitely got my eyebrow raised. Been rolling my own for a while...
What about NuxtJS?
you should make a video listing those dead JS libs/frameworks, because you keep saying it's a lot of them, while not mentioning a single one
I will!
Brasil, JS, ganhou +1 like and subscribe
Hi MIguel! 👋
Most of the "JS influencers" already shifted towards Drizzle and are ditching Prisma - so yeah, Prisma's death is not that unlikely :D
What about nestjs as backend , and what about drizzle orm as database orm
I love Nest.js! I used it in the past, it's really good. However, in this video, I'm focused only on Rails-like frameworks, and Nest doesn't sell itself as the Rails of JavaScript like Adonis
@@DanielBergholz Do you care explaining what would be a "Rails-like" framework? I'm sorry if i overlooked that in the video
@@projetoventuraas far as I know, Nestjs doesn't allow you to build templates to render pages to a client. I think you can only use it as an HTTP API (+ Web Sockets and RPC)
next.js bad, prisma bad; htmx and drizzle are the solution
Then I would ask you... Rails or Adonis? hahaha!
Rails always. I recommend Adonis only for those who cannot stop using JavaScript
LOL, they build testing framework VineJS? That's validation library, their testing framework is called Japa 🤣
Never heard of it 😂😂😂
Adonisjs is a amazing framework, but the fact that everything is build in house scare me as fuck. Because if Adonis die basically I will have to rewrite all my source code
I think nestjs is more popular backend js framework
Yes it is. But on this video I’m talking about Rails-like frameworks
MIGUEEEEEEEEEEEEELLL
why are you speaking english bro? que saudade de vc daniel, ótimo vídeo
to reach more people I guess, it's better even my native language is not English
To reach a wider audience and practice English. I am thinking of doing it myself.
Speak english bro , to be able to understand 😅 (i like spanish but i speak english sorry )
The reason is simple: Reach a bigger audience!
Real question should be: "Why not?"
why people forget NestJS
Hahaha so true, when it might be the most rooted and solid one of them all ^^"
Excellent introduction, great video content. The reason I didn't like Adonis was because they building things by their own, but when they make abstraction and allow to use third package, it can be good. I prefer nestjs haha, but it's good to know about these things.
6:02 🐱*
I personally haven't had a major issue with next.js since using it for 7yrs (I don't normally use too many packages so things don't break). I agree it's now changing too much and getting over-engineered. I think the vercel team now have too many resources to ruin an already good product. With that said, I think most js devs use way too many libraries than its necessary instead of the web platform. You don't have to use everything you see on RUclips by influencers. If you write nextjs the idiomatically vercel way, you shouldn't have an issue.
I like Adonis too. I would say it's more like Laravel. Almost like someone decided to build a laravel clone. I've maintained laravel in a previous job and it's my favorite fullstack framework.
We need to stop with this JavaScript on the backend shit
Many cloud services have nodejs libraries so I don't think it's going anywhere. Nothing wrong with JavaScript on the backend. It's the most productive language, it's among the most well supported. Rich ecosystem. Just write good code and don't over complicate things
Salve miguel
Miguel tá sempre presente nos vídeos!
Coloca legenda em pt br
Ai eles fazem igual o adonis 4 KKKK
Em que sentido?
Eles Descontinuaram, e removeram os repositórios
@@gustavofelix9101 Po eu achei que a documentação e repositórios legacy ainda estavam disponíveis, eu usei eles quando tinham acabado de lançar o v5
Sim v5 legal, só que quem utilizou a v4 meio que se lascou
pinoy:
great meme bro, the 4 dudes will rebuild all the software, just one more day... talk about feature creep jeez
oh look another one...
Eu já tinha ouvido falar desse framework uns anos atrás, mas sempre o pessoal que falava, falava com um pé atrás sobre o framework, mas eu mesmo nunca dei uma change. Talvez experimente.