I like writing content in Markdown and I enjoy Astro very much. When I tried out Astro's content collections feature, I couldn't stop wondering how would a nice packaging look for it, which would smooth out the rough edges around Markdown in static websites.So I made the app that I can enjoy when writing posts on my Astro-powered blog. It's been saving me a ton of time already.I don't need...
No doubt here! I know there's a lot of nitpicking, but that's just my experience so far. I wanted to make it clear by removing all "we" or "you" words from the post to make sure I'm not saying my opinion is the definitively right one :)
> Rails is not the only choice that does so.
Absolutely, the only two reasons I went with Rails is because Ruby looks beautiful to me and I was following the news in Rails world for years.
A lot of JS tooling that popped up in the last 10 years is amazing. The React way of building a UI makes a lot of sense to me and I like it way more than HTML + JS combo from the old days. Also, using JS for both frontend and backend is convenient and great for hiring teams.
But, after years of making SPAs, it gets tiring to assemble all of the pieces from scratch every time. I don't want to configure things, I want to build my ideas.
What I was trying to say is that Rails got a lot of things right and it's making me productive, because I don't have to make the same decisions over and over again when making a JS app. Rails made those decisions for me and the only thing left for me is to build my app.
I myself like Next.js and Remix a lot, but they still leave you to spend time making basic decisions, like how to organize your project or how to implement background jobs.
That's why I'd love to see more conventions and less configuration in the JS land.
I'm not trying to convince anyone to switch or use Rosefinch anyway. I built it because I needed it exactly like this and shared it here in case there's someone else who wants something like this too.
> I'm curious whether you've considered putting this in the mac app store or not, or what your reasoning was around that.
I haven't put it on Mac App Store for two reasons primarily:
1. I already figured out licensing, integration with Paddle, building and distribution for my previous app, so I was able to reuse 99% of it 2. I wanted to have full control over rolling out updates quickly in case a critical bug appears
> Also curious if you did beta testing if you could tell us anything about what that process was like
I tested it myself, because I was building this app for my needs, so I kind of knew exactly what I wanted it to do. I also received regular extensive feedback from a friend, who's also helped me shape the app a lot.
You can listen to the 24/7 radio of only Daft Punk tracks and live sets, test your knowledge of their tracks by guessing the track name or just play some tetris, which plays faster & faster Daft Punk tracks as you progress through the levels.
Have fun!
I was really inspired how HEY solved my email inbox for me and I thought it would be great to apply similar tools to other types of notifications - GitHub ones in particular. For example:
- Screener - Reply later - Mute any thread without blocking users or repositories
Curious what your thoughts are and how does your current workflow on GitHub look like? What would you love to exist or not exist? Thanks :)