[HN Gopher] Astro 2.0
___________________________________________________________________
Astro 2.0
Author : todotask
Score : 135 points
Date : 2023-01-24 17:48 UTC (5 hours ago)
(HTM) web link (astro.build)
(TXT) w3m dump (astro.build)
| [deleted]
| [deleted]
| helij wrote:
| I like the idea of "performant, content-focused websites" but the
| website itself hosting Astro doesn't really feel performant. When
| I scroll down it struggles on my quite powerful desktop computer.
| [deleted]
| __Parfait__ wrote:
| The homepage is text and static images.. I doubt the issue is
| with them
| POiNTx wrote:
| Does anyone have any experience with Astro and Sveltekit? What
| would you choose over the other one in which situation? Is Astro
| only used for websites that just display content, while Sveltekit
| can be used for more complex webapps?
| axwdev wrote:
| I've been evaluating these two along with some other options
| for a project over the last couple of weeks.
|
| If you have pretty much entirely static content, Astro will
| almost definitely be more suitable due to the lower JS you'll
| be shipping.
|
| If you need complex interactions and nice client side routing
| you'll want SvelteKit. You can embed SPA routers etc within
| Astro but I feel like once you're going down that route you
| might as well just use a more appropriate meta framework.
|
| For something in between, it's a toss up.
|
| I will say SvelteKit is the best frontend meta framework I've
| tried so far. Happy to answer any specific questions.
| Alifatisk wrote:
| Who is the team behind Astro? I forgot what they created before
| this.
|
| Update, they created Snowpack (https://www.snowpack.dev), PikaCDN
| (now Skypack, https://www.pika.dev/cdn),
| uzername wrote:
| I believe it was Snowpack.
| steveklabnik wrote:
| I recently tried Astro for the first time and really enjoyed it!
|
| Guess it's time to learn how smooth the upgrade path is...
| majkinetor wrote:
| I read entire documentation yesterday, and I am very impressed.
| Looks fantastic, with some great conventions if you need it
| quick, but fully customizable if you change your mind later. I
| particularly like the fact that I can switch from SSG to SSR and
| back.
|
| File system as db, markdown with templating and js expressions,
| nasting layouts, quick random endpoints, filtering of
| collections, named slots everything repo friendly - whats not to
| like. Also, great content and looking docs (particularly
| interactive tutorial).
|
| Reminds me a lot of nanoc SSG framework (ruby).
| Alifatisk wrote:
| Never heard of nanoc, interesting!
| lern_too_spel wrote:
| How does Astro hybrid rendering compare to Qwik?
| https://qwik.builder.io/
| SparkyMcUnicorn wrote:
| Apparently Astro is faster.
|
| https://docs.astro.build/en/concepts/mpa-vs-spa/#case-studie...
| Alifatisk wrote:
| To my understanding...
|
| Astro is tries to rely on SSR as much as possible with MPA
| approach, so the client have to render as little JS as
| possible.
|
| Qwiks goal is to be instant for every device, it does this by
| delaying the download & execution of JS so much it can. Qwik
| also partially renders the content in its state on the server,
| then sends it over to the client to do the rest.
| lern_too_spel wrote:
| Qwik can fully render server-side, but if you cause an
| update, it downloads the minimum JS needed to make that
| update on the client.
| dang wrote:
| Related:
|
| _Astro 1.0 - a web framework for building fast, content-focused
| websites_ - https://news.ycombinator.com/item?id=32401159 - Aug
| 2022 (249 comments)
| acedTrex wrote:
| Once astro support in webstorm is complete it will be to me the
| perfect static site fx
| fks wrote:
| https://youtrack.jetbrains.com/issue/WEB-52015/Astro-Languag...
|
| > Hi everyone! Sorry for not posting the announcement here,
| too. I can confirm that we're going to add Astro support in
| v2023.1. We will keep you posted on our progress once we start
| working on the issue and will ask you to give Astro support a
| try and share your feedback with us. Please keep monitoring the
| issue for updates.
|
| Sounds like it's coming soon!
| Onion44 wrote:
| [dead]
| kkarimi wrote:
| We switched to Astro a few months ago. Some team members were not
| super convinced since NextJs is better known but during our spike
| to test them both out Astro came on top on ease of use. We have
| now been in production for a couple of months and could not be
| happier. It's very straight forward for simple sites but we
| switched a couple of legacy react apps to SSR with it and it was
| super easy and developer experience is great and speed of
| rendering could not be better. Looking forward to switching our
| marketing site next with the help of this new collection API in
| v2
| vijaybritto wrote:
| Did you start by rendering all of the react app as a fat
| island?
| jongold wrote:
| tried Astro recently and really, really love the DX and docs - so
| well executed
| satvikpendem wrote:
| Astro is nice but it misses the UX of instant page transitions
| via client side routing, so I switched back to NextJS.
| mikojan wrote:
| You mean it misses the UX of instantly interrupting you with
| random flashes of spinners and skeleton elements.
| satvikpendem wrote:
| No, I don't mean that, actually.
| verzeichnis wrote:
| Maybe I am not understanding completely what you are missing,
| but there is an SPA integration that gives you instant
| navigation. It also features pre-fetching, so it's not limited
| to already visited pages.
|
| https://github.com/RafidMuhymin/astro-spa
| satvikpendem wrote:
| Then what's the point? With NextJS I can have SSR but with
| client side navigation hydration. It's simply a better
| solution for that use case than an almost year old random
| library for Astro. Astro is good for traditional MPAs that
| don't need much interaction.
| verzeichnis wrote:
| Sure, I wasn't saying Astro is for every use case. Like, no
| tool ever is.
| satvikpendem wrote:
| Indeed, hence why I said I moved back to NextJS for my
| use case, personally speaking.
| cosmojg wrote:
| How does Astro 2.0 compare to isles[1] (beyond what's mentioned
| in the FAQ[2])?
|
| [1] https://iles.pages.dev/
|
| [2] https://iles.pages.dev/faqs#astro
| chimen wrote:
| Had a hard time using MANY existing React ui components from
| various packages. I guess it is fast but the work involved in
| trying to build anything more interactive is not worth it just to
| shape 2-3-10ms. I can't find a plus for using this over something
| like Hugo (https://gohugo.io/) for example.
| mikojan wrote:
| Every time I returned to my Hugo project it felt like I had to
| learn everything all over again.
|
| With Astro it is just components. I am used to those. The
| cognitive load is much lower.
| rickrollin wrote:
| I think I will give Astro another try but from my experience it
| was a bit clunky. There were a ton of dependencies and it did not
| go smooth at the beginning.
| gherkinnn wrote:
| I recently tried to get MDX to work with Next.js app directory.
| It _might_ be possible, bit I did not have the patience.
|
| Astro might just be the solution. It is for a largely text-based
| project.
| rcarr wrote:
| Been building my blog with this the last couple of weeks. It's
| great and this version seems to sand down some of the rough edges
| (error messages used to be terrible, now they look like they'll
| be useful, content collections mean I don't have to glob
| everything then filter). Oh and markdown type checking is really
| cool. Looking forward to seeing how it develops over the next few
| years.
| vlaaad wrote:
| Was this post written by ChatGPT? Were many other comments in
| this thread written by people with undisclosed interest in this
| project (e.g. employees, founder friends)?
|
| Maybe I'm thinking too much about it, but I got triggered by
| "This new release is a game-changer for anyone working with
| Markdown on the web", the style of writing is very similar to
| ChatGPT... Also, I work with markdown on the web and never had
| any problems with it, not sure what's the problem solved by
| Astro.
| MrOwnPut wrote:
| The previous sentence before your quote:
|
| > Astro now helps you organize your Markdown with built-in
| parsing, validation, and automatic TypeScript type generation.
|
| The bolded text leading the paragraph of your quote:
|
| > deliver complete type-safety for Markdown and MDX
|
| The announcement is about typing MDX. Also, Astro just works
| out-of-the-box with MDX, Next.js you have to do configuring. In
| others your don't get SSR. Personally Astro has the easiest and
| most flexible markdown experience ever. It makes sense to focus
| on that support and to lead with it. You can even have
| templates in JSX with MDX content files, cool stuff like that.
|
| The Hybrid Rendering feature is really cool too. I have a few
| pages I wanted to SSR, but most of the site can be SSG. This
| saves from needing two projects. I can select pages to generate
| at build.
|
| The rest of the error message optimization and dev tool
| improvements is always welcome.
|
| Not affiliate with Astro btw.
___________________________________________________________________
(page generated 2023-01-24 23:01 UTC)