81–90 of 91 posts
Earlier quoted context omitted.
The character limit is, in my opinion, the primary reason Twitter became so bad. It encourages absolute language (qualifiers take up characters!) It discourages any level of nuance. I use Mastodon which has a 500 limit, and even that sometimes is not enough.
Why use any? Why force yourself to comply with the arbitrary limitations imposed by some third party somehwere. For what?
It's blazing fast too. Good job. But is it purely text? Or do you support/will support, images and videos?
I built something for a similar goal, make it easy for someone to start their blog. But instead it's a static website, clone the repo, adjust the config.ts, write the posts in markdown, host anywhere: https://starter.bryanhogan.com/
Please don't use !important at scale https://github.com/BryanHogan/astro-starter-template/commit/...
I built something for a similar goal, make it easy for someone to start their blog. But instead it's a static website, clone the repo, adjust the config.ts, write the posts in markdown, host anywhere: https://starter.bryanhogan.com/
> The simplest way to build a high-quality website. The build (generation) step should be able to execute on/inside the browser runtime (using standardized APIs, not hardcoded against proprietary APIs that the NodeJS people invented). See also https://crussell.ichi.city/pager.app.htm >
Earlier quoted context omitted.
> The simplest way to build a high-quality website. The build (generation) step should be able to execute on/inside the browser runtime (using standardized APIs, not hardcoded against proprietary APIs that the NodeJS people invented). See also https://crussell.ichi.city/pager.app.htm >
That would mean using a completely different architecture, and I think there many benefits to using Astro. I like your underlying goal of fewer environment-specific dependencies, but the ones used here were carefully selected because they do provide a benefit.
> the [dependencies] used here were carefully selected because they do provide a benefit.
You're moving the goalposts.
Earlier quoted context omitted.
That would mean using a completely different architecture, and I think there many benefits to using Astro. I like your underlying goal of fewer environment-specific dependencies, but the ones used here were carefully selected because they do provide a benefit.
I'm responding to a specific claim that you put at the top of the page the linked to. > the [dependencies] used here were carefully selected because they do provide a benefit. You're moving the goalposts.
The thing you linked doesn't meet the bar I'm aiming for, either for the resulting site or for the experience of building it. Astro helps me achieve those goals as part of this project, which is why I consider it a beneficial dependency.