Live data from Hacker News

Show HN: 10 Years to Build a Free SQL Editor

timestored.com

41–50 of 101 posts

Re: Show HN: 10 Years to Build a Free SQL Editor

#41
post #8

Out of curiosity, what took you 10 years? Keen to hear your journey as someone building in the same space..

> Out of curiosity, what took you 10 years

That's not the first release, that's "just" 3.0, they released QStudio 1.25 in 2013 (their first blog post) https://www.timestored.com/b/qstudio-kdb-ide-1-25-released/

Re: Show HN: 10 Years to Build a Free SQL Editor

#43
post #39
post #21

The messaging is quite confusing. The title makes it seem like it took you ten years to release a first version, but the website says it’s version 3.0 and claims it’s “the leading SQL Editor […]”¹. There is a GitHub repo² but the history is quite unhelpful, with a bunch of commits named the same and some older commits after newer ones. ¹ Unless it were the only one, it would be impossible to be leading right after la…

Yeah... what's up with these commits that just add a dot or ""? Looks very much like just boosting the commit count. 90% of the commits are just adding nonsense. update to latest = 21+16 release = 4+1 bugfix = 3+2 update readme = 3+35+35+35+35+35+35+35+14 total = 309 out of 341 commits The commits stopped at Jun 25, 2016 when it was just a "Custom JDBC Driver and Authenticator Example" and then suddenly Feb 23, 2023…

Yes, the first and only "real" commit has been this one https://github.com/timeseries/qstudio/commit/c7c39ff69b90762..., where they committed the sources. After that mostly useless changes in the readme, even the "bugfixes" do the same (nothing).

Re: Show HN: 10 Years to Build a Free SQL Editor

#45

Congrats on launching! I haven't gotten very far into it, but here's a little feedback about what it took to get to the point where I could try it out. 1. I'm running MacOS 14.4.1. 2. I downloaded the jar file. 3. I double-clicked the jar file. It wouldn't open. I've seen this before, so I navigated to the jar file, right-clicked it and chose open, and it gave me the option to launch it even though it was unsigned af…

Very helpful - TY

Re: Show HN: 10 Years to Build a Free SQL Editor

#47

Looks cool. What is the benefit of registering? I skipped it to try it out. Was very quick looking at my local MySql database. I liked being able to run sql against some local parquet files. Would need to support Redshift via an ssh tunnel for me to use it on a regular basis. I don't want to manage the tunnel with a different tool.

Currently registration is eventually enforced. I need to remove some logic to make it restricted to only happen for one niche database as I use the email to reach out to large finance firms to finance the dev effort.

>>Would need to support Redshift via an ssh tunnel for me to use it on a regular basis. Redshift has definitely moved up the priority list lately. I will look into it.

Re: Show HN: 10 Years to Build a Free SQL Editor

#48

Hi - I am trying to run this on an Intel Mac. I got it to launch once, and attempted to open a small (~30mb) sqlite DB, and got a crash. It now hangs/freezes as soon as the application opens (taking over > a full core of CPU e.g. 120% plus utilization in Activity Monitor), even after deleting and re-downloading the .jar file. Any ideas? Would love to check this out! edit: Apple silicon, which I note because the proce…

Ah! I figured it out. User error. I had hit "open file" instead of "open database" and the application decided to open the 30mb sqlite DB as text (e.g. a sql query), including syntax highlighting. Simply letting it grind away for 10 minutes or so allowed it actually open the file, at which point I could close the tab and performance is back to normal. Look forward to experimenting!

Thanks for letting me know and great QA. Another user reported this just last week and I hopefully have it fixed: https://github.com/timeseries/qstudio/issues/49 qStudio 3.04+ now only opens .sqlite/.db/.parquet as data files not for text editing.

Re: Show HN: 10 Years to Build a Free SQL Editor

#49
post #8

Out of curiosity, what took you 10 years? Keen to hear your journey as someone building in the same space..

Good software takes ten years, at least according to Joel. That’s a significant application of course.

https://www.joelonsoftware.com/2001/07/21/good-software-take... - Reference. I read this for the first time. Thank you for sharing this.

Re: Show HN: 10 Years to Build a Free SQL Editor

#50

Looks cool. What is the benefit of registering? I skipped it to try it out. Was very quick looking at my local MySql database. I liked being able to run sql against some local parquet files. Would need to support Redshift via an ssh tunnel for me to use it on a regular basis. I don't want to manage the tunnel with a different tool.

I think SSH tunnels are exactly the type of thing that should be handled by a different tool. It's a lot of complexity to add to the app, when the app (and any DB client) inherently already supports connecting via an externally managed tunnel. An established tunnel managing program, or just your terminal, would be better at managing tunnels than a tunnel tool tacked onto this app, and the interoperability is already free.

Tunnels have so many configuration options that you'd either have to support raw configuration in the app (at that point just DIY a tunnel in the terminal), implement something incomplete, or build a full featured SSH tunnel manager into the app.

SSH tunnels can be totally transparent to DB clients. Unlike DB application-layer stuff like credentials, where the DB client needs knowledge of them, I don't see the cost/benefit of integrating SSH tunnels into the app itself.

Post reply on HN