wkoszek

The right question might be: how to expose a kid to many things to pick up what are they into. And how to let them spend as much time on it as possible.

LowEndBox often lists similar VPSes if anyone here is interested

I haven't yet tried the units from Amazon where you connect the Waterpik to the faucet, but perhaps they could be good -- for me the problem has always been how small the water container was.

Human teeth need cleaning :)

If this is doing better waterpik + toothbrush and perhaps has a long guarantee and leaves you with a 2x normal feeling every morning, I could see the appeal. I dropped $60 on Waterpic and it broke. So then I got a better Waterpik for $100+ but it was clunky unit with bigger water container that didn't fit in my small bathroom. And it broke. But I do like the feeling of electric toothbrush.

PayPal might still be the sweetheart, but there's no innovation I feel. With eBay having CC support and being able to charge and return a charge back to the card, PayPal now is in a niche. I'm helping a founder recruit. To handle the load of candidates, we give folks applying some $ for doing a small 1hr project, and Claude told me that PayPal may still be universal way of sending a "gift amounts". I often wonder how much work would it be to bring IBAN accounts to the US. The need for Zelle baffles me, and the fact that person A can't send $ to person B via normal bank infrastructure is interesting.

I'm really happy seeing this project. Not sure if this helps you gain $$$ customers, but stupid thing that turns out very difficult in PG is making this fast:

SELECT COUNT(*) FROM large_text_db WHERE X

Where X is something that must be matched exactly. X can be FTS query on FTS-indexed table, but the way COUNT() works in PG is that it's impossible to make it fast. Over large tables, lets say 1B+ rows, it can be very very slow.

Example use case is: searching through a hospital DB of reports that have "pancreatic cancer" in them. This is trivial in SQLite, but in PG it's hard.

You use stability of PostgreSQL to open a pitch. Also most people use PostgreSQL because someone out there was a fan, proponent and champion of Postgres. Otherwise they'd be on MySQL or Oracle.

And your sales folks would call and say: "No need to change anything, we still run PostgreSQL, and ours is just called pgrust, but it's N times as fast".

I'd help with testing if you helped them add this. I'd be interested in this.

I really hope your project succeeds so that you can sit, sip delicious coffee with your legs on a high desk, and laugh really loud, like a gorilla, at all the haters from this and previous HN threads.

There's so much to do in databases, and it's so hard to get right and test is all, I think we'll all have 10x the jobs. The easy stuff will go away, but to e.g.: test the new DB engine and ensure there aren't any exploits -> let's just work on it. But it's not that the introduction of compilers made engineers obsolete.

I mean.. they made it 2 weeks ago. Clearly the time isn't now. Why be so negative immediately.

Don't give up. Just publish it, if you know your invention is better. Devtool VCs will give you money based on the growth of your GitHub stars, popularity and the size of community. I can even intro you to some - but it can't be to "burn angel money". You'd just have to commit to build a DB company for 10yrs. Devtool community building is low effort: Discord channel and you can write code in 1 window, and talk in another as your thing is testing/compiling.

If someone did this before with PG, provide links. Practical pragmatic example where I think this project is cool: process vs thread. There were members of the PG core team that wanted to explore it, and members who said it'd tank a project. pgrust is an amazing experimentation ground for it.

I published similar project here: www.emuko.dev - emulator for RISC-V. This one turned out to be 3x as slow as QEMU for example.

re: CTOs - if the improvement is 3% nobody of course will look at it. If the improvement is 30%, it'll be too big for big players to ignore, so as a CTO you'll be tasked with trying it out. It's really a matter of whether this thing is safe and secure, losing data or has a trojan. If the authors can prove it's all valid working code etc., it'll be a viable project.

Congrats for launching this project. I think it's awesome. I did two similar projects, just to learn how to work with LLMs and it felt good--reminded me times debugging code with GDB and going through stuff in semi-manual mode.

I'm building data + AI platform. It got complex, and I'm using AI-assisted coding to move fast. One thing that helps me was property based testing. I have a traffic generator that simulates 10 users working on my platform. I run it 24/7 and if it shows that the software survives the test (I called it "fate" after ffmpeg's CI), it's good enough to roll out. If you wrote something like that, core PostgreSQL folks would like it too, unless there's something equivalent like this. It'd be: create random tables, fill with random data, then issue randomly constructed query.