Thanks for sharing! I use Fireabse Hosting, which I guess gets grouped in with the other services you mentioned. It's free, has a lightweight devX, and integrates with CI via GitHub actions for preview and production builds [1].
Right, I didn't consider Google. The 360MB/day of free egress traffic (Spark plan) strike me as very peculiar. But at least it isn't Cloudflare's "unlimited" with secret limits in place, or Netlify's 100GB/month and then enormous costs on everything above.
Thanks for reminding me! I'll give Firebase a look.
By the way, very minor thing I noticed. Clicking on your photo on the homepage swaps backgrounds, but the timer-based swapping still runs on its fixed interval. Can look unpolished if you click it a bunch or in the wrong moment.
Not a full replacement in all scenarios. But for my personal website with a basic blog, Astro is by far the simpler and more maintainable option. I bet that is true for most people here who maintain their own personal website.
keystatic supports editing mdx files. keystatic is basically a frontend to update files on github, so if e.g. you want to write a blog post from your phone it can let you do that kind of thing.
I felt the same way! But I came around. Take a look at the source code for a component [1]. The .astro format is pretty much just TS, CSS, and HTML. I don't even need React anymore. Way less glue code and dependencies than with Gatsby. There is a configuration file and some abstractions for things like collections, but almost everything is opt-in.
There's not really any DSL. You just put some TS in the frontmatter for fetching/transforming at build time, TS in a script tab (if needed) and the html is just basic templating that takes props.
Me too! The closer my framework is to raw HTML, JavaScript (really TypeScript nowadays), and CSS, the less lock-in I feel. Those 3 languages are continue to get better year over year. And we are get better framework abstractions every few years too. Astro feels like it hit the sweet spot, but maybe there is more to come.
Astro is what I wanted and thought Gatsby would be. GraphQL was the wrong sized abstraction for a basic blog site like mine. And once Gatsby turned towards the cloud (which made sense as a business), everything just got so complicated. I was swept up by it too.
Cool insight on frontend ceilings -- deployment is king.
Creator here. Glad that HN rediscovered my old side project. All the code is freely available on GitHub [1]. It's running on a tiny f1-micro GCE instance which is currently down due to the traffic. I don't have time to fix it right now, but it should resolve itself once traffic dies down. The data source is also several years out of date at this point, so the links it returns may not match current reality. Other than that, it should still work!
I'm currently building an AI email app called Shortwave [2]. I promise that has much better uptime and more consistent updates!
I have been using shortwave for quite some time off and on. I absolutely don't appreciate it's shifted focus / pivot on the AI hype train. Shortwave itself can use that focus instead to add more productivity features instead.
It's interesting to see you now pitching it as an "AI email app". If it's actually working you to gain more traction than may be it's worth riding the wave but please don't loose focus. It was not meant to be an AI first email app, it was a better Google Inbox, a better email client.
Definitely gonna try it out, I've been frustrated with Gmail's inability to sub-segment it's main categories of smart labels in a good way, and it's a long term battle to not miss important emails amid the clutter of time waster stuff. Tried another paid for client "mimestream" which delivers a real gmail desktop app experience, but doesn't really address this.
[1] https://github.com/jwngr/jwn.gr/tree/master/.github/workflow...