Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Astro 1.0 – a web framework for building fast, content-focused websites

astro.build

Post reply on HN
Print view View original

171–180 of 256 posts

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#171

Post by quickthrower2 »

est wrote: post #162
quickthrower2 wrote: post #156

Earlier quoted context omitted.

I think edge computing and CDNs might be what is making this all more interesting. It is not just where you render (Server vs. Client), it is where you render (Dallas vs. Rio). If you can get your app to re render small sections and have the framework figure out that these sections are static and can chuck them in a CDN (or they are not and need an edge server, or a central server) then you can get lots of optimizati…

> I think edge computing and CDNs might be what is making this all more interesting You know what's old-fashioned way of doing this? Buy multiple VPS around the world and deploy website files using a script.

Since this seems like a fairly separate concern, and it is a fair bit of maintenance, that is nice to outsource to the cloud.

Let the experts deal with adding locations, location detection, DNS, redundancy and so on, for a very small price, relatively speaking.

I am not saying you need Astro: You can make the files yourself, then use a service like Netlify to do the CDN-ing for you.

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#172

Post by Yiin »

cutler wrote: post #151
cercatrova wrote: post #149

Earlier quoted context omitted.

TypeScript, that's the differentiator. Having fully typed variables in the templates cannot be replicated in templating languages (well technically they might be able to but that's not as ergonomic as fact).

Talk about sledgehammer to crack a nut - honestly, why does anyone need type safety in a simple templating operation? Dynamic languages have their uses, you know. Type safety is a tool, not an ideology.

because it's nice to know whether that `post` variable contains a property `createdAt` or `published` At without leaving the template. Arguing "I don't use it why should you" is unproductive.

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#173

Post by cutler »

cercatrova wrote: post #154
cutler wrote: post #151

Earlier quoted context omitted.

Talk about sledgehammer to crack a nut - honestly, why does anyone need type safety in a simple templating operation? Dynamic languages have their uses, you know. Type safety is a tool, not an ideology.

I basically never use dynamic languages anymore. If there aren't algebraic data types in a language I simply don't use it. Sometimes people think I'm exaggerating but it's truly great to use a language with ADTs that you get spoiled.

So what do you use for shell scripting?

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#174

Post by Annatar »

dang wrote: post #36
Annatar wrote: post #30

Earlier quoted context omitted.

It's not a shallow dismissal, it's the scourge of our industry; I can't wait to retire so that I would never have to look at it again. Give it a rest with virtue signalling.

X being a scourge does not make every X-comment deep. On the contrary, comments about scourges are often shallow and lame. Edit: I just took a look at your recent comment history, and ouch—that makes it painfully clear that you don't want to use HN as intended. I've therefore banned the account. If you don't want to be banned, you're welcome to email hn@ycombinator.com and give us reason to believe that you'll follow…

No post body was provided.

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#175

Post by necovek »

biztos wrote: post #113

> What People are Saying > Astro works with the tools you already love, but this requires a lot of effort to get right. Luckily, Astro is supported by some amazing partners across the industry who support our vision for a faster web. Fast/easy content-focused websites are a subject dear to my heart but far from my day-jobs, so I'm always happy to hear about people making the thing I never quite finish making. But the…

They are saying it's hard to develop a tool like Astro, but they've got support from a number of companies so that's why they are succeeding.

Not very clear, agreed.

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#176

Post by ricardobeat »

zdragnar wrote: post #152
alanwreath wrote: post #143

Earlier quoted context omitted.

What are you referring to? I am unaware of what “regular” templating you’re referring to or what react is achieving that is not available or cumbersome under react or svelte. I mean if JSX is considered as something particularly powerful (not saying it does) doesn’t Vue actually do that https://vuejs.org/guide/extras/render-function.html ?

Think of JSX as a macro, rather than "regular" templating, which is typically string substitution. For static sites, this means that you get functions and objects the entire way through the render pipeline right up until there is a full tree built and the final output is rendered. You still get all the separation powers of contexts, the component based reusability, etc, and it is all regular JavaScript / typescript e…

Some day we have to stop repeating this nonsense. JSX requires much more learning than simple templating, there is no inherent benefit. Even a simple conditional is more complex than your average template.

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#177

Post by swyx »

vosper wrote: post #112
eKIK wrote: post #89

Earlier quoted context omitted.

While Astro has a lot of impressive features I found that it was the "developer experience" (god I hate that term) that was superior compared to everything I've tried before. With Hugo and Jekyll I always needed to go revisit the docs whenever I hadn't worked with it for a while. I never got to the "oh, I get this tool now" phase, where the content generation could just flow without issues. Publii was cool, but tryin…

> "developer experience" (god I hate that term) Why do you hate it? It's useful to have a term to differentiate between the experience of the person using the output of the tool (user experience) versus that of the people developing with the tool (developer experience). Honestly we need more DX improvements in this industry. Especially look at DevOps - the user experience of Chef's output (I'm picking on Chef here, i…

it is subjective and overused - perfect storm for industry jargon that takes up a lot of space without saying anything more than "this thing sparks joy"

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#179

Post by cercatrova »

cutler wrote: post #173
cercatrova wrote: post #154

Earlier quoted context omitted.

I basically never use dynamic languages anymore. If there aren't algebraic data types in a language I simply don't use it. Sometimes people think I'm exaggerating but it's truly great to use a language with ADTs that you get spoiled.

So what do you use for shell scripting?

I like using Nim or Rust, or TypeScript, depends on the script. If it's just a few lines, sure I'll write it in bash, but if it gets a little larger, I convert it into a real programming language.

Re: Astro 1.0 – a web framework for building fast, content-focused websites

#180

Post by tannhaeuser »

cercatrova wrote: post #149
cutler wrote: post #146

Earlier quoted context omitted.

You have to be joking, surely? React/Vue as a mere static template languages? Dedicated static site frameworks such as Jekyll and Middleman are a much better experience. My favourite is still Perl's Template::Toolkit.

TypeScript, that's the differentiator. Having fully typed variables in the templates cannot be replicated in templating languages (well technically they might be able to but that's not as ergonomic as fact).

There are "templating languages" such as SGML for generating type-checked markup ie. respecting the regular content model and lexical types expressed in DTDs and other markup declarations. This results in injection-free, HTML-aware templating ie. templating engines can properly quote/escape content in attributes, CDATA sections, etc. and can enforce content model rules (that eg lists consist of nothing but list items, that script elements aren't placed where forbidden as would be required in user content such as comments provided by your web site visitors, etc.) Much more powerful than programming language types, and needed in CMSs.
Post reply on HN