yliang
yliang on Hacker News
Agree on the logo part. Could you tell me why you think the name is bad?
Well, if charging you money makes you feels better, I can set something up for you to pay ;)
Interesting. Initially I chose to use helper tool to run sudo commands. After wrapping all those poorly-documented Authorization/ServiceManagement/XPC C APIs into Swift 3, I was like, sh*t, lemme just use askpass. Also, many of those APIs are deprecated in newer version of macOS and it's unclear that when Apple will remove them. That said, I can see the HUGE benefits of using launchd under the hood.
Hmm..I'm also using 10.11 with the dark theme. Does the app on your machine look very different from what I show in the second screenshot at
http://www.marathono.com/? If it does, please consider reporting a bug thru the Help menu of the app.
lol..not a designer. I just put together some hand-drawing over the weekend. Will probably redesign the icon to make it a more serious app..
The "Show Output" menu of Marathono opens a Terminal/iTerm tab to tail the output. Currently Marathono is designed for start-and-forget kind of processes - outputs are for occasional debugging purpose only.
The "may start charging for it" piece is mostly for stopping people from asking me to open source the app. If I do start charging money, it will probably be at the price of a burger.
I'm the developer of PSequel (a popular PostgreSQL client, http://www.psequel.com/) and it has been free since it came out two years ago. I got people asking for open sourcing it almost every single day. Many people assume free == open source.
Exactly. And other convenient features like termination notification and file system monitoring.
Correct me if I'm wrong, "brew services" work for launchd services installed with homebrew only. But Marathono allows you to run any arbitrary commands.
Posted by
yliang on Tuesday October 11, 2016 @12:15PM
from the show-hn dept.
Just released a new version with SSL support. Please try it out.
Just released v1.0.2. Now supports SSL connections. Use the "Check for Update..." menu item to download the update.
Thanks for your suggestions! To replay,
1. I'll fix this.
2. When you switch from one DB to another in postgres, you are essentially making a new connection instead of reusing the same connection[1]. In PSequel, you could create different connection bookmarks for different databases and open multiple connections at the same time in multiple windows.
3. In my company, we write migration scripts (activerecord migration) to modify table structures. We usually don't modify them directly/manually. 80% of the time we use GUI tools just for viewing data and testing out complicated SELECT queries. I didn't realize that many other people's usage patterns are different. Anyway, the feature of modifying table structures is in PSequel's roadmap.
[1] http://stackoverflow.com/q/10335561
Writing a PostgreSQL adapter for Sequel Pro is a good idea. I don't know how an adapter can fit into Sequel Pro's architecture though. I'll take a look at Sequel Pro's codebase and consider this approach. Any help would be appreciated!
Because it uses some APIs introduced in 10.10.
I just received a few complaints about its performance for displaying large tables. I'm working on a fix.
Thanks for your reply! Never used Amazon Redshift. I'll try to find out what is so special about it.
Edit:
Amazon Redshift is based on PostgreSQL 8.0.2 but PSequel uses libpq 9.3. I'll work on supporting Redshift if it gets enough demands. Anyone who wants a specific feature could fire a request at http://www.psequel.com/report_bugs
Maybe. But I would like to see how it goes before open sourcing it.
Currently the auto-updating feature only reminds you to download an update. It doesn't update itself silently. And you shouldn't edit your production data directly anyway (or at least you should try on a dev server first), right?
Thanks for your suggestion! The feature of editing query results is actually the second highest priority item in my todo list. (The first one is Query Bookmarks.)
Thanks for your suggestions. My plan is to support most features in Sequel Pro (but for PostgreSQL of course) which do include schema and user management. This release is just a start.
Thanks for the reply! It's using libpq 9.3 under the hood. I'll work on supporting earlier versions if it gets enough demands.
Posted by
yliang on Monday December 01, 2014 @03:08PM
from the show-hn dept.