The assholes outnumber the good ones, and it feels like all of humanity is transactional and extractive.
At first all engagement is exciting and validating. You work nights and weekends to please people you’ve never met, sure that one good turn deserves another.
Then you get your first jerk, then your second, then your third, while your father is in the hospital. You feel pressure to ship a feature you never wanted. Your issue tracker is demoralizing. You get a PR! Maybe someone is coming to your rescue. It sucks. Now you need to figure out how to respond. You’re alone. Your passion project has become your albatross.
It’s an RFI, not an RFP. They are basically looking to build a list of vendors who might be interested in bidding an RFP or competing in a domain-relevant contest.
I originally wrote this because sometimes a CLI or TUI is just super convenient. I used to use the DuckDB and Sqlite CLIs a lot, but was frustrated by their limitations, especially for doing data analysis work (my background).
b. any particular reason why you chose to implement it the way you did (e.g. I see you use Python + Textual as opposed to something like https://charm.sh/libs/)
c. any major functionality you feel it's missing?
d. any limitations (e.g. doesn't work with Oracle?)
A. I was using the DuckDB CLI and kept hitting walls on analyses. Had a shower thought of “I wonder if anyone has used Textual for a DuckDB client” and decided to build one myself.
B. This uses Textual, a python framework for TUIs. Python is my language of choice.
C. Hoping for more db adapters soon. Canceling queries is a missing piece I have yet to figure out
E. Maybe if you don’t use Python apps and do have another sql client you really like.
Fair enough (author here). I just launched support for any databases other than DuckDb and published a guide to create adapters for new dbs. I’m expecting the community to step up here, since I’d rather spend my time adding features to Harlequin. ODBC should be coming shortly. The hard part is honestly just having access to a DB server for testing.
The Harlequin v1.0 release made it to the Front Page -- I'm back to announce v1.5, which adds support for other databases (and addresses the biggest feedback I got on HN).
At first all engagement is exciting and validating. You work nights and weekends to please people you’ve never met, sure that one good turn deserves another.
Then you get your first jerk, then your second, then your third, while your father is in the hospital. You feel pressure to ship a feature you never wanted. Your issue tracker is demoralizing. You get a PR! Maybe someone is coming to your rescue. It sucks. Now you need to figure out how to respond. You’re alone. Your passion project has become your albatross.