Live data from Hacker News

Sequel Pro – Open source macOS native MySQL GUI client

sequelpro.com

61–70 of 170 posts

Re: Sequel Pro – Open source macOS native MySQL GUI client

#61
post #54

3 SQL GUI tools (Sequel Pro, Dbeaver, HeidiSQL) on the front page at the same time. Has this happened before?

And none of them Electron based!

You know, Electron is perfect for these use cases:

A table view, a tree view, few buttons, some dialogs.

Re: Sequel Pro – Open source macOS native MySQL GUI client

#64
post #36

Projects like these should be celebrated through donations and this project makes it easy. When’s the last time you’ve seen freeware developer tool for macOS that’s not from a corporation with money to spare? I personally can’t think of anything beyond iTerm (utility), Homebrew (utility), ...aaand that's where my list ends.

I don't think that freeware is really a part of the Apple Developer ecosystem. Most of the MacOS exclusive software I use on a daily basis costs $20-$30, a price I'm more than willing to pay for software like Pixelmator, DaisyDisk and Alfred that is significantly more polished (and Mac-ish) then the average piece of open-source software just due to the resources available to them.

It used to be though. I think the freeware culture slowly moved away at 10.5 or so. Maybe that was accelerated by the app store release in 10.6.

Quicksilver, while at the time a terrible mess in terms of the code is basically the forefather of all these launchers.

Apple also removed a lot of the MacOS APIs that allowed you to mod system components (e.g. input managers) around the same time.

Re: Sequel Pro – Open source macOS native MySQL GUI client

#66
post #42

Earlier quoted context omitted.

Have you used Postico? I have both it and DataGrip but find myself primarily in Postico for Postgres, feels lighter weight and easier to navigate

Agreed that Postico is amazing. Totally worth the $40 or whatever it costs.

sadly neither postico nor tableplus can connect using an ssh certificate. this is becoming a big drawback in organisations switching to ssh certs instead of keys.

Re: Sequel Pro – Open source macOS native MySQL GUI client

#67
post #37
post #15

It hasn't been updated in a very long time. Constant crashes on Mojave. I have transitioned away to TablePlus and DataGrip. Too bad because it was a very good tool for quick edits.

Are you sure it's not actively being fixed? I see active development on GitHub with many commits. Have you reported the issue on GitHub as the website suggests?

It was fixed several months ago, apparently, but the fix still hasn't been released outside of a test build yet. There have been multiple issues opened (and closed as duplicates) but this[0] seems to be the original.

[0] https://github.com/sequelpro/sequelpro/issues/3116

Re: Sequel Pro – Open source macOS native MySQL GUI client

#68
After a brief period working with macOS, I missed Sequel Pro when moving back to Linux. In the end I wrote Sequel Joe:

https://github.com/ohwgiles/sequeljoe

Still, it's light years behind Sequel Pro in terms of features/completeness/quality and probably always will be :)

Re: Sequel Pro – Open source macOS native MySQL GUI client

#69
post #36

Projects like these should be celebrated through donations and this project makes it easy. When’s the last time you’ve seen freeware developer tool for macOS that’s not from a corporation with money to spare? I personally can’t think of anything beyond iTerm (utility), Homebrew (utility), ...aaand that's where my list ends.

I'm way more inclined to use something on a daily basis that I pay for to be honest as this means I have some kind of influence on how long the project will be around that I incorporate in my workflow. At least a little bit more than if I use a free product.

I don't mind paying for quality software and I think a lot macOS users feel the same way.

Re: Sequel Pro – Open source macOS native MySQL GUI client

#70
post #54

Earlier quoted context omitted.

And none of them Electron based!

You know, Electron is perfect for these use cases: A table view, a tree view, few buttons, some dialogs.

Until you try to actually use more than demo data and need to resort to tricks to sort out unresponsive rendering.

I have no love for Electron. Still remember Active Desktop, MSHTML, XUL and Symbian Web Runtime.

As someone that does both native and Web fullstack, the place for Web technologies is on the browser, with approaches like PWAs.

Post reply on HN