vdemedes

That's really cool, very curious to see what you came up with!

Thanks! The `thememirror` package is ESM only, so maybe that could be it?

I haven't tried it myself yet, but I'm definitely looking forward to once they complete the pivot (see https://blitzjs.com/docs/blitz-pivot).

> I think the author went too deep into details here, as this crowd is full of people who are going to be able to rip pieces of this article to shreds.

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.

Couldn't have said it better myself!

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.

I should've been more clearer. This post isn't comparing Rails to any framework out there.

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.

Thank you! Yes, working on it right now.

That's cool, if that app works for you, keep using it.

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.

Hey, thank you!

> 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.

There are great apps out there, but all of them are too complicated and too powerful. What I wanted is to have a nice minimalistic app where I could collect all my queries that I often use for debugging various stuff. That's why I won't add things like data editing or schema changes to Rosefinch. If you need extensive features like that, you'll definitely be better of with SQLiteStudio or alternatives ;)

Thank you! If it takes off, I'll consider adding Linux support. Until then I want to ship high quality experience for Mac, rather than subpar experience for everyone. ;)

Thank you! I started with SQLite, because that's what I use the most, but I'm planning to add support for MySQL and PostgreSQL in the coming weeks.

Hey HN! If you're an avid Daft Punk fan like myself, hope you're going to enjoy this fun tribute website I made.

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!

Hey HN! I don't have a beta for you to try out yet, but I thought I'd share my ideas on how to make notifications less stressful for open source maintainers.

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 :)

Nope, not yet. But there is working example in the repository, in /test folder.

Agree, I will add "before" and "after" events to the Joconut, so that developer can listen to them and display progress indicator he likes.

Awful mistake, sorry, completely forgot about that issue. Will be fixed ASAP. However, there is "new" event, which gets fired on every new page. You can listen to it using $.joconut.on, see Readme in GitHub repository at https://github.com/vdemedes/joconut.

Thanks, glad you like it!

Partially agree here with you.

It allows loading pages without refreshing browser window. User will not notice any loading indicator/progress, pages will instantly "replace" each other.

Sorry, no demo page for now. It is different from PJAX in these ways:

1. 1kb minified and gzipped

2. Auto-loading of JS and CSS from new pages, if needed

3. No need to set up and configure

1. No need to set up, just script tag

2. 1kb minified and gzipped

3. Auto-load of additional JS and CSS from new pages, if needed

Nope, you just have to include joconut.js in the web page. It will do the rest.

Update pushed, issue fixed.