I am truly getting sick of frontend development... I don't understand what this field is becoming where people are proud to say that there's 50 awesome frameworks out there, and with this latest framework you can combine it with other frameworks on top of meta-frameworks to create super ultimate meta frameworks that can be combined with future new frameworks to replace your previous frameworks from 2 months ago. It's ridiculous.
I think it's starting to become obvious, there is a reason "new" things are popping up with increasing frequency. People are seeing that this Vercel model works (at least for them, and rather they THINK it works), and you see a bunch of old and new vendors alike (Vue, Laravel even getting in on this paid stuff) trying to essentially use this "open source" --> paid service model in the web development space, it's not just javascript. In my opinion you are very foolish to get your stack wrapped up in ventural capital hype that will only end one way, they're going to eventually sell and it's going to get much worse after that. It's so obvious... but people just go along with it because it seems nice and comfy right now, forget about later on amirite.
I use both and both are great. Astro for websites - landing page, documentation sites, lead gen sites, blogs, MPAs and other content driven websites Next.js for web apps - dashboard, SaaS, admin portal, PWAs, SPAs and other apps
@@ziad_jkhan Hi! The main reason is the ecosystem and flexibility for building complex SPAs. The React ecosystem, especially with Next.js, is well-established for SPAs and highly dynamic applications. While Astro's islands architecture allows integration of components from different frameworks, it has limitations with certain React ecosystem libraries that require global state management or complex interactivity across the entire app. Another factor is Astro’s partial hydration model. State management tools like Redux or Zustand can be used within Astro, but they’re confined to specific islands where JavaScript is hydrated. This limits Astro’s ability to handle global state in the same seamless way as a single-page application built with frameworks like React or Vue, making Astro better suited for content-heavy sites with isolated interactivity.
@@ziad_jkhan if your app needs to reach android/ios users and you build cross-platform with flutter, then you will probably want to use same codebase in your webapp
I’m using Astro for my personal website, I especially like how page transitions are easy to use and clean. I have yet to discover the full potential of Astro Islands.
I agree. I feel like the new generation of javascript programmers don't have the experience of not using any frameworks so they start with different view of what is unnecessary or over complex. Simplicity has no value these days, marketing has dominated the scene. Developers nowadays have more concern about they're own career, that's not about making things easier or better, it's about what should I know to get the next job. If there are no astro in most of companies, then people are not willing to try it.
i tried learning astro a lot then i visited a freelancing website and saw a lot of job posting using wordpress so i am now starting my learning journey with wordpress
You can use Astro as migration tool. If you, e.g., would want to switch away from React to Svelte you could do it step by step using Astro. I don't think it's a good idea to use that feature to have multiple teams using multiple different frameworks and their different tech stack for the same project. Too much complexity, too much expertise required to maintain the project. But for migrating form one tech to the other it's awesome, in my opinion!
I agree Astro is amazing .. but was hoping for a actual answer into why people aren't using it .. for me, is hard to sell it to the company i work, knowing the eco system is a bit small in comparison to next/nuxt .. but it is a amazing framwork i 100% agree
the awesome thing about astro is that you don't really need that much of an ecosystem. You can still use your react front end code, it will work. You can even pair it with htmx to have spa like page transitions.
I'm seeing more and more devs/projects replacing Next for their marketing website in favor of Astro with React components or starlight docs websites. Of course, it's a framework with a direct focus on content websites.
Hey Max & Team, I’ve taken a few of your courses before, and you’re one of the best. I switched to Astro for my personal tinkering a while ago. I’m still having trouble rendering the actual markdown content in list form (as opposed to listing just the frontmatter) from content collections and content layers. I want to be able to generate relatively complex “textbooks” that read like infinite scroll with lots of menu nav options. I would pay for a course if you covered that use case. Would even pay a lot to kickstart it.
If your website work proer...never switch... It's all unproven garbage....Only if you know it's been running for years, and I'm not talking about a stupid website that has some content and pictures.. if you want help send me message make i can fix it for you
Astro can handle different version of React, or Angular, etc in the same project. It is possible. Imagine starting a compononent with the latest React features instead of being stuck with legacy code because updating everything gets complex and costly. Game changer. I have to test this.
It's because Astro fills in the same role as a backend language with templates. It would be like asking if I'd rather use Astro/Node or Templates/Go. I can still use Svelte or HTMX on the front for either of those projects. If I was still going to use Node then I'd rather use SvelteKit to get a feature complete experience.
Some people think Laravel is easier to work with compared to complex JavaScript frameworks. But those who haven't tried Astro might find it even simpler to manage and keep updated over time. In my opinion, I don't really like how Laravel is set up or its main ideas, but it's important to remember that different people have different preferences based on their own experiences and needs.
I've been using Astro since 2021. Absolutely everything you can do with Next, you can do in Astro, in a simpler, faster, and lighter way. You can choose between Svelte, Vue, HTMX, React, Solid, etc. For me, using React/Next stopped making sense a long time ago. Killer combo for AI projects: Astro + Svelte + Turso.
Astro is quite nice. Then only thing for me is that it there are only very few things it can do that something like nextjs does not. And I feel like if I have to start using react components at some point, I might as well have used nextJS from the start. However Astro is great to learn how frontend framework work without the extra state management and such. And of course if you know you'll only do static, then there's no problems. Also Astro is great for markdown-based content, even though Nuxt now has Nuxt Content that is just as good.
If only all front end devs concentrate on a single tool to make an ultimate best solution for FE development instead of building 10000 different frameworks.
Astro is like Next.js, but less powerful. They both let you choose or mix Static Site Generation, Server-side Rendering, Client-side Rendering, they both provide image optimization and other stuff. But Next.js's features are more advanced and more powerful
@@ledannam@ledannam the main reason is that node or bunjs runtime is too slow. It take several minutes to restart to server. We have migrated to serve react js server side rendering with golang(the performance is great, it take just a few seconds to restart the backend server).
It doesnt get visibility because; 1. Not enough mainstream, 2. Nowadays most people want reactivity, 3. Doesn't have a enough complexity (devs install too much over engineered libraries haha)
I think you are a very smart developer and a good content creator. However, as someone who has gotten lost in the teckstack of Webdevelopment and who is tormenting himself by learning Java, you are stressing me out by introducing the solution number 1000000000000000000000000000000000000000000000000000000000000000000 for the SAME GODDAMN PROBLEM!!!
Yeah, thats what everyone dreams about. Working on a project that has multiple frontend libraries to debug.. I wonder why it never caught on which such a great feature.
I am truly getting sick of frontend development... I don't understand what this field is becoming where people are proud to say that there's 50 awesome frameworks out there, and with this latest framework you can combine it with other frameworks on top of meta-frameworks to create super ultimate meta frameworks that can be combined with future new frameworks to replace your previous frameworks from 2 months ago. It's ridiculous.
😂
Do you have a problem with self control or something?
😂😂😂
Take a deep breath, the more the better, the problem is not that there is too many, it's that you dont want to study.
I think it's starting to become obvious, there is a reason "new" things are popping up with increasing frequency. People are seeing that this Vercel model works (at least for them, and rather they THINK it works), and you see a bunch of old and new vendors alike (Vue, Laravel even getting in on this paid stuff) trying to essentially use this "open source" --> paid service model in the web development space, it's not just javascript.
In my opinion you are very foolish to get your stack wrapped up in ventural capital hype that will only end one way, they're going to eventually sell and it's going to get much worse after that. It's so obvious... but people just go along with it because it seems nice and comfy right now, forget about later on amirite.
I migrated from NextJS to Astro. It was the best decision. Using Astro as fullstack in server mode and host it on VPS.
Can you actually host astro on something like firebase or github pages or anything that is free
Sounds good? Have you got something built/in production? Any links to have a look please?
@@darz_k. Latest addition is Ikea's home page.
If you inspect it you'll find plenty of Astro Islands.
AstroDotBuild has a showcase page.
I use both and both are great.
Astro for websites - landing page, documentation sites, lead gen sites, blogs, MPAs and other content driven websites
Next.js for web apps - dashboard, SaaS, admin portal, PWAs, SPAs and other apps
Any reason in particular for not just using Astro for both websites and apps?
Same, I also through Remix into the mix.
@@ziad_jkhan Hi! The main reason is the ecosystem and flexibility for building complex SPAs. The React ecosystem, especially with Next.js, is well-established for SPAs and highly dynamic applications. While Astro's islands architecture allows integration of components from different frameworks, it has limitations with certain React ecosystem libraries that require global state management or complex interactivity across the entire app.
Another factor is Astro’s partial hydration model. State management tools like Redux or Zustand can be used within Astro, but they’re confined to specific islands where JavaScript is hydrated. This limits Astro’s ability to handle global state in the same seamless way as a single-page application built with frameworks like React or Vue, making Astro better suited for content-heavy sites with isolated interactivity.
I am using Astro for all you mention.
@@ziad_jkhan if your app needs to reach android/ios users and you build cross-platform with flutter, then you will probably want to use same codebase in your webapp
I’m using Astro for my personal website, I especially like how page transitions are easy to use and clean. I have yet to discover the full potential of Astro Islands.
I agree. I feel like the new generation of javascript programmers don't have the experience of not using any frameworks so they start with different view of what is unnecessary or over complex.
Simplicity has no value these days, marketing has dominated the scene.
Developers nowadays have more concern about they're own career, that's not about making things easier or better, it's about what should I know to get the next job.
If there are no astro in most of companies, then people are not willing to try it.
So we have now a meta frameworks that's so meta it can be used not only with Meta's React, but also other UI frameworks.
i tried learning astro a lot then i visited a freelancing website and saw a lot of job posting using wordpress so i am now starting my learning journey with wordpress
Great perspective. Just found Astro and using it for light sites work, a nice relief from the next.js complexities and "heavy" feeling.
You can use Astro as migration tool.
If you, e.g., would want to switch away from React to Svelte you could do it step by step using Astro.
I don't think it's a good idea to use that feature to have multiple teams using multiple different frameworks and their different tech stack for the same project.
Too much complexity, too much expertise required to maintain the project.
But for migrating form one tech to the other it's awesome, in my opinion!
Astro can do everything next can do in my experience. Its been my favorite framework for a while now.
how does Astro handle caching and invalidating SSR pages or parts of pages that are not statically generated? How does it handle partial prerendering?
Astro Server Islands for Partial Prerendering
I agree Astro is amazing .. but was hoping for a actual answer into why people aren't using it .. for me, is hard to sell it to the company i work, knowing the eco system is a bit small in comparison to next/nuxt .. but it is a amazing framwork i 100% agree
the awesome thing about astro is that you don't really need that much of an ecosystem. You can still use your react front end code, it will work. You can even pair it with htmx to have spa like page transitions.
I'm using Astro as well. It's fantastic! Throw in a Node adapter and you have a proper backend too! People be sleeping on Astro.
Have you done that? Node adapter? That's new to me - any links to check out regarding how to do that please?
What exactly do you mean by node Adapter?
Node adapter?
Node adapter for Astro allows you to SSR and use mode server. So you can benefit from fullstack Astro (frontend + backend in javascript).
I'm seeing more and more devs/projects replacing Next for their marketing website in favor of Astro with React components or starlight docs websites. Of course, it's a framework with a direct focus on content websites.
if content is one option, what are the other options?
2:10 I love the color theme, please does anyone know the name?
4 months later, you upload a new video "Why I hate Astro?"
😂😂😂
I already hate it actually just from trying to convert something from svelte to Astro. It felt like I was unnecessarily losing features.
@@jsward17 I am using SvelteKit and still don't have a reason to migrate to Astro.
Hey Max & Team, I’ve taken a few of your courses before, and you’re one of the best. I switched to Astro for my personal tinkering a while ago. I’m still having trouble rendering the actual markdown content in list form (as opposed to listing just the frontmatter) from content collections and content layers. I want to be able to generate relatively complex “textbooks” that read like infinite scroll with lots of menu nav options. I would pay for a course if you covered that use case. Would even pay a lot to kickstart it.
If your website work proer...never switch... It's all unproven garbage....Only if you know it's been running for years, and I'm not talking about a stupid website that has some content and pictures.. if you want help send me message make i can fix it for you
Astro is awesome, some features: UI-agnostic (easy integration with react, vue, etc.), server-first, customizable, great SEO support.
Astro can handle different version of React, or Angular, etc in the same project. It is possible. Imagine starting a compononent with the latest React features instead of being stuck with legacy code because updating everything gets complex and costly. Game changer.
I have to test this.
It's because Astro fills in the same role as a backend language with templates. It would be like asking if I'd rather use Astro/Node or Templates/Go. I can still use Svelte or HTMX on the front for either of those projects. If I was still going to use Node then I'd rather use SvelteKit to get a feature complete experience.
Thank you, a lot of people i see just jump to adding react. You can do a lot with core astro
shifted from remix to astro. Documentation is amazing
Some people think Laravel is easier to work with compared to complex JavaScript frameworks. But those who haven't tried Astro might find it even simpler to manage and keep updated over time. In my opinion, I don't really like how Laravel is set up or its main ideas, but it's important to remember that different people have different preferences based on their own experiences and needs.
I've been using Astro since 2021. Absolutely everything you can do with Next, you can do in Astro, in a simpler, faster, and lighter way. You can choose between Svelte, Vue, HTMX, React, Solid, etc. For me, using React/Next stopped making sense a long time ago. Killer combo for AI projects: Astro + Svelte + Turso.
Full course on astro we want.
Learn to read the docs.
Believe me you don’t need the course. Just open some sample project and the docs. All is pretty straightforward in Astro.
was about to say the same thing
@@phat80 seriously, people need to learn to study on their own by reading the docs instead of waiting for courses
+1
you know what, I am going now to try astro, this is crazy awesome.
I really really REALLY hope for a future Bun/Elysia course. No? but PLEASE! 🙏
Can we do SPA-like routing on Astro now? That was the only thing keeping me from using it.
you were always do SPA also in Astro also but that is not the power to use Astro
how is Astro used more often in production, with other frameworks, or on vanilla JS?
Astro is quite nice. Then only thing for me is that it there are only very few things it can do that something like nextjs does not. And I feel like if I have to start using react components at some point, I might as well have used nextJS from the start. However Astro is great to learn how frontend framework work without the extra state management and such. And of course if you know you'll only do static, then there's no problems. Also Astro is great for markdown-based content, even though Nuxt now has Nuxt Content that is just as good.
Why use Astro when I can use Svelte or Next?
What is the big benefit for Astro over Svelte?
simplicity. multi page apps
because neither svelte nor next arent static site generators by default
@@martinlesko1521 SvelteKit is.
You can use Svelte, React, Vue etc. in Astro at one moment :D The implementation is just one command.
@@palockocz i meant svelte as in sveltekit
I'm surprised SvelteKit weren't mentioned at all
Astro course coming?
make a course on astro js and update remix js course
Astro is great, combine that with Cloudflare adapter, and SQL in durable objects 🤯
I would be interested to hear your take on nanoDjango
Isn't it true that ASTRO and Jekyll are the only systems that allow both markdown and HTML to play nice on the same page?
Personally, I love Astro and I use it for my personal website. Super easy to learn!
I tried Astro… but it was still buggy. Then, SolidStart turned v1… and now there is no point in using Astro.
I think Astro are more rather trying to be position as the JavaScript WordPress project?
express and ejs ?
why not use that ? isn't it almost the same ?
i tried it it's a cool concept but i didn't like the syntax it felt forced
whats forced about html-like syntax
NextJS is also a full-stack framework
Because you can render anything to HTML by putting a puppeteer caching instance in front of your application in your Kubernetes…..
I am using Astro Starlight its so easy u literally dont need any Js its just the best for creating documentation.
If only all front end devs concentrate on a single tool to make an ultimate best solution for FE development instead of building 10000 different frameworks.
IKEA uses Astro in the latest website refresh
Great, another framework to learn... :(
I was just getting Pro in previous latest framework.
im using Astro for static websites.
Make an Astro course for us
Astro is amazing, but you don't answer the question on the Title (and was expecting understand why is not popular)
Why is everybody making false statements in their RUclips titles?
Im looking for a astro course made for you
I stop using next and only use astro for develop websites, regards from Mexico
i am using, really enjoying so far
Why do you say nobody is using Astro?
Would call it a meta-framework or super-framework because it sits above other frameworks.
Easy answer: because it's not associated with a tech giant company that created it 😢
Who told you that?
Astro is like Next.js, but less powerful.
They both let you choose or mix Static Site Generation, Server-side Rendering, Client-side Rendering, they both provide image optimization and other stuff. But Next.js's features are more advanced and more powerful
The reason is simple. React is Java of frontend. The inescapable demon.
angular
Wrong, angular is the spring of js 😂
Everytime I see another JS video I am glad I've discovered Elixir 😅
PS: thx to Max I am Vue dev .. but hope I'll make Elixir my next job.
took a while but we got there...
Don't know about everyone else but I'm not using it because I don't believe in SSR. 🤮
I want a course on Udemy in my table now! LOL
I am using Astro 😅
I prefer Qwik over Astro to be honest
Astro and Qwik work together really well, actually.
@@JasonEPerkins I mean I'd choose Qwik CITY directly instead of Astro from the start
I am building my first Astro site as I watch this video. :)
Incoming course?
Every day New JS Frameworks are coming Angular,React,Vue,Hono,Bun,Astro..... Always we have to update ourself
Those are old, and some of them that you mentined aren't even in the same category.
Bun is a JS runtime... React, Vue and Angular are over a decade old.
They're js, what do you expect 😂
Seth Codegen
i love astro. Its kinda like nextJS but with vite and less fuss.
honestly HTMX has really been serving me well!
not everyone cares about ssr
I love astro
Because they faked a lot of benchmarks.
Couldn't find a good course with Auth and TypeScript on it 😅
Nothing beats PHP + HTMX
👌
We don't use nextjs, ASTRO. We use pure reactjs for building our front-end
Astro can render React component to HTML and only send JS if needed -> super fast website.
@@ledannam@ledannam the main reason is that node or bunjs runtime is too slow. It take several minutes to restart to server. We have migrated to serve react js server side rendering with golang(the performance is great, it take just a few seconds to restart the backend server).
It doesnt get visibility because; 1. Not enough mainstream, 2. Nowadays most people want reactivity, 3. Doesn't have a enough complexity (devs install too much over engineered libraries haha)
SSR is overrated
its not soo amazing as you think
why is that? do you see some downfalls of the astro? For me it's a great NextJS alternative without vendor lockin. And super fast as a bonus.
@@carlofpvdiary4819
How it compares with Sveltekit and Nuxt?
proof
I think you are a very smart developer and a good content creator. However, as someone who has gotten lost in the teckstack of Webdevelopment and who is tormenting himself by learning Java, you are stressing me out by introducing the solution number 1000000000000000000000000000000000000000000000000000000000000000000 for the SAME GODDAMN PROBLEM!!!
Yeah, thats what everyone dreams about. Working on a project that has multiple frontend libraries to debug.. I wonder why it never caught on which such a great feature.
The mess with JS made me move to Phoenix and Elixir, happiest decision even. NEVER GOING BACK TO JS.