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].
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.
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.
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!
You're right. We're a small team of 10 people [1] and we have to ruthlessly prioritize. Gmail on web and iOS are our primary platforms right now. Our Android app is in beta and will be for longer. In the meantime, are improving the PWA experience. We just shipped a brand new inbox last week that has much better support for the Android PWA - finally fixes the back button issue we heard a lot about! I know it's not a native app, but that's not practical for our team right now. It will be eventually though.
Email is the perfect tool for these new LLMs - most of us have years, even decades, of our writing and important information in our email archives. Now that we have AI which can understand that in a deep way, a ton of value is waiting to be unlocked and email is going to change. All of our tools will. I talked a bit more about this in our blog post today [1].
Also yes, attention is nice for a small young startup fighting against a bunch of giant companies who've been doing email for decades. Marketing is indeed a thing :) But we stand by Smart Summaries as a feature that actually makes your email experience better and faster. And we plan to build more soon.
I go into this a bit more in our blog post from today [1], but we believe LLMs are going to transform how we interact with email. Yes, you still need a solid inbox with labels and contacts and push notifications and everything else that email clients like Shortwave offer. And we will continue to iterate on and nail that experience. But these new tools allow us to push the boundaries of what can be done with email, and we intend to do just that.
Outside of search and import history, our free version is 100% feature compatible with the paid version. None of the core functionality (including the new AI stuff) requires a paid plan. On a paid plan, you can import and search your full history. On the free plan, you can import and search your last 90 days. See our pricing page for more details (https://www.shortwave.com/pricing/).
Despite adding some AI features, we are definitely still focused on the core triage and workflow of getting through your inbox. We've launched a bunch of other stuff already this year (https://www.shortwave.com/changelog/) and have more non-AI features coming.
As for marking stuff as read: this is a known issue that we are planning to address. For now, it behaves like archive in Gmail, which does not mark as read. How would you like it to work?
We use OpenAI's GPT-3 API to generate summaries. We have explicitly opted out of OpenAI's default behavior of using their APIs to train their models [1].
Our summarization feature is entirely opt-in. So if you're concerned about sharing your emails with OpenAI, you can choose not to use the feature. You can also read our Privacy Policy [2] and Terms of Service [3] to see how your data is used.
Hi HN - Shortwave co-founder here. We’ve built a full-featured email client over the last couple of years, just in time for the rise of LLMs. We’ve added quite a few features (and are working on many more) that use LLMs to save you time.
I’m most excited about Smart Summaries — they’ll read and then summarize (even from a different language) long newsletters & those huge threads you just don’t want to wade through.
We’ve got a long way to go, so please do leave us feedback if you have it. Shortwave is much of the early Firebase team, and HN really helped us building that product :) Thanks in advance!