Live data from Hacker News

Astro 7.0

astro.build

51–60 of 61 posts

Re: Astro 7.0

#51
Switch from widely supported unified/rehype to own rehype-incompatible markdown tooling just for build time speed improvement is quite upsetting

Good that they added a tool to keep using rehype, but I’m unsure that it will last

Re: Astro 7.0

#52
post #15

I have been trying to convince my marketing department to replace there archaic wordpress with an Astro build with AstroCMS and markdown for there needs. I have build several sites using Astro 6, and i am finding the ease of building the sites amazing and exceptional in SEO as well.

What’s AstroCMS?

Emdash?

Re: Astro 7.0

#53

Switch from widely supported unified/rehype to own rehype-incompatible markdown tooling just for build time speed improvement is quite upsetting Good that they added a tool to keep using rehype, but I’m unsure that it will last

We don't intend on removing support for the unified ecosystem, we on purpose made the Markdown processing pipeline pluggable so that it was possible for both to exists!

The vast majority of our users don't use any sort of unified plugins, so a pipeline that's faster (and about 100 deps leaner) felt like a better default.

Re: Astro 7.0

#54
post #22

It's very cool to see the JS ecosystem reducing dependencies and I hope this trend continues. Astro has gone from 247 deps in v6 to 190 in v7. https://node-modules.dev/#install=astro@7.0.6 https://node-modules.dev/#install=astro@6.0.0

The ultimate reduction is leaving JS to the browser and write backend code in Go, Rust, Java, C#,...

Re: Astro 7.0

#55
post #54
post #22

It's very cool to see the JS ecosystem reducing dependencies and I hope this trend continues. Astro has gone from 247 deps in v6 to 190 in v7. https://node-modules.dev/#install=astro@7.0.6 https://node-modules.dev/#install=astro@6.0.0

The ultimate reduction is leaving JS to the browser and write backend code in Go, Rust, Java, C#,...

Do you really have to make the exact same comment in every related thread?

It’s just tedious at this point.

Re: Astro 7.0

#56
post #54

Earlier quoted context omitted.

The ultimate reduction is leaving JS to the browser and write backend code in Go, Rust, Java, C#,...

Do you really have to make the exact same comment in every related thread? It’s just tedious at this point.

Yes, apparently it isn't tedious enough, otherwise you would have not wasted a few seconds replying.

Re: Astro 7.0

#57
post #54
post #22

It's very cool to see the JS ecosystem reducing dependencies and I hope this trend continues. Astro has gone from 247 deps in v6 to 190 in v7. https://node-modules.dev/#install=astro@7.0.6 https://node-modules.dev/#install=astro@6.0.0

The ultimate reduction is leaving JS to the browser and write backend code in Go, Rust, Java, C#,...

Astro is a backend project...

Re: Astro 7.0

#58
post #57
post #54

Earlier quoted context omitted.

The ultimate reduction is leaving JS to the browser and write backend code in Go, Rust, Java, C#,...

Astro is a backend project...

Which started as JavaScript, and as all things go, got rewriten into Rust.

Re: Astro 7.0

#60
post #59
post #58

Earlier quoted context omitted.

Which started as JavaScript, and as all things go, got rewriten into Rust.

+90% of Astro is still written in TS

Still.... lets see how long it stays that way, now that RIR got started.
Post reply on HN