A complete desktop app for browsing and editing your Postgres, MySQL, SQLite data, creating beautiful dashboards, and soon designing automated workflows for repeat tasks.
I've kept a devlog of the last 10 months of building DB Pro, which has been the best way to bring users to the product. I'd highly recommend folks starting a devlog if they can.
Finished reading the article, having really enjoyed it (I grew up with Terry's books), came back to the HN comments and the top comment is someone ranting "dIS iS aye-EyE sLoP"
What a terrible, terrible timeline we live in now. Seriously. I genuinely hate it.
We're building a product [1] to compete with DataGrip, a JetBrains product.
Many people told us we were crazy to compete with such a mature product as DataGrip before we got started.
It has been fascinating to speak to people who use database apps and to learn about their experiences.
Now, we have many, many customers telling us that they have cancelled their DataGrip/JetBrains sub and have switched to using our product, mainly due to speed but also cost.
I'd love to give this a try, I work at a privacy sensitive company, can I ask in advance is it possible to opt out of:
> We automatically collect certain information when you use DB Pro:
> Device information (IP address, browser type, operating system)
> Usage patterns and interaction with our services
> Log files and analytics data
> Cookies and similar tracking technologies
My Neo runs like a sowing machine with 8GBs. So well that I honestly cannot think of any instances where I have felt the system slowdown. I use the device appropriately though -- I'm not trying to run SOTA LLMs locally or anything. For web browsing, light programming, and an iPad replacement, the Neo has exceeded my expectations. Compared to my M4 Mini, I honestly cannot tell a difference.
One of my favourite things of being on HN is reading comments like this. Namely, devs who worked on games I played growing up. I absolutely love hearing stories from their past about little technical nuances like this comment. The more technical / specific, the better.
I'd honestly love to compile a book of "war stories" told by devs like netcoyote.
This is a great idea, but respectfully, if you're going to get traction you need to be the one instigating getting people to talk to you. Have a pitch, have an explicit ask, and be willing to put effort into making it happen.
Correct. Order-of-magnitude-wise, it's roughly the same as the alternatives.
In the context of writing a new service for a new company, you should not spend one second thinking about whether your technical choices will allow you to serve 100,000 requests per second, or 150,000 requests per second. If you are, you are focusing on the wrong thing. If you get to 1,000 requests per second with a real paying client base you already achieved more than most dream of.
On the other hand, if you are optimizing a mature distributed low-latency equity trading system that is consuming ten's of thousands of market data ticks per second, a 50% improvement in performance on a 20 machine cluster might turn into some real $$$ savings. But that's not what this article is about.
Counterpoint, Meta is currently (and for the last decade) trying to rewrite MySQL so it is basically Postgres. They could just change their code so it works with Postgres and retrain their ops on Postgres. But for some reason they think its easier to just rewrite MySQL. Now, that is almost certainly more about office politics than technical matters...but it could also be the case that they have so much code that only works with MySQL that it is true (seriously doubtful).
You are just mislabling good architecture as 'premature optimization'. So I will give you another platitude...
"There is nothing so permanent as a temporary software solution"
Your article completely ignores operational considerations: backups, schema changes, replication/HA. As well as security, i.e. your application has full permissions to completely destroy your data file.
Regardless of whether most apps have enough requests per second to "need" a database for performance reasons, these are extremely important topics for any app used by a real business.
A complete desktop app for browsing and editing your Postgres, MySQL, SQLite data, creating beautiful dashboards, and soon designing automated workflows for repeat tasks.
[1] https://dbpro.app
I've kept a devlog of the last 10 months of building DB Pro, which has been the best way to bring users to the product. I'd highly recommend folks starting a devlog if they can.
reply