So, no, Markdown is not holding me back. It is perfectly capable of what the author claims it isn't.

[0]: https://daringfireball.net/projects/markdown/syntax#html

1. The various clients and servers implemented different subsets of the functionality, which deteriorated UX.

2. Service providers have an incentive to lock you in and the average user doesn't mind. So no one pushed for it.

Or do you mean something else altogether by 'CSS attributes'?

[0]: `https://docs.astro.build/en/guides/routing/#static-ssg-mode

What makes it so great is not that it serves a particular niche (like "content-driven websites") but that it provides a developer experience that makes it incredibly easy to scale from a static website to something very complex and interaction-heavy without compromising UX.

Using a framework has upsides over writing static pages manually. Most notably, you can decompose your website into reusable components which makes your implementation more DRY. Also, you can fluently upgrade to a very interaction-heavy website without ever changing tech or architecture. But that's just what I value. I whole-heartedly recommend trying it out.

They suggest a platform where "you upload any docker-compose.yml". Consequently, this makes SSO, updates, etc. the user's responsibility.

- https://kvmpods.com/

- https://dockerdeploy.cloud/

The word 'object' has different meanings. One includes arrays and the other does not. They prefer the latter. You prefer the former. I don't think this has much to do with 'facts' and 'opinions', but rather with the practicality of choosing a certain way to speak.

I’d liken it to the word 'sorting'. JavaScript libraries sort in a certain way that is simple to implement. However, this is so different from what we typically mean by 'sorting' that people came up with natural sorting algorithms. Are these people treating facts like opinions on how to sort? I’d rather say, they acknowledge the relevance of a certain way to speak.

Components (be it Astro, Svelte, React, etc.) have a lovely API for sharing code across web pages. I used Hugo before and hit the limits of shortcodes pretty quickly. I can't comment on Jekyll though.

Furthermore, if the need for some dynamically rendered pages or client-side interactivity comes up, it is very easy to integrate this later on. I can build static, server-rendered and client-rendered pages (and everything in between) with the same set of tools, which means less mental load when I develop.

Comments URL: https://news.ycombinator.com/item?id=43514695

Points: 262

# Comments: 42

Comments URL: https://news.ycombinator.com/item?id=43514186

Points: 1

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=43366920

Points: 4

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=43230726

Points: 1

# Comments: 0