Tangential: a friend of mine growing up refused to read Ayn Rand, because he said that everyone he knew that had read her books turned into assholes, and he didn't want to become an asshole too.
I've read enough to find this statement to be largely correct. I found myself fully aware of the kinds of people who admired the thought patterns they wrote about that now I wonder why more assholes haven't read the stuff, it seems like they'd like it.
Very similar features, Catnip is Claude Code specific and does everything in a Docker container so you can more safely run in YOLO mode and the Git worktrees don't make a mess on your host filesystem or checkout. Also is mobile responsive which is cute.
Struggling with the same thing right now. I'm trying to make it work by generating unique ports for each instance so they don't conflict. Not quite 100% successful yet.
Curious to hear more.. why is random port selection not working for your case? The other issue we've seen is machines tend to get overloaded with tons of agents running tests concurrently, hence the SSH remote isolation mode.
I recently started using Catnip (https://github.com/wandb/catnip) for this. Catnip also automatically manages multiple Git worktrees, and has a responsive UI for mobile.
I take great issue with the way CockroachDB marketing seeks to imply compatability, when infact what they are promising is wire protocol compatability (i.e. you can fire up your copy of psql on the CLI and it will connect).
Last time I looked, a great number of primitive, obvious, fundamental, low-hanging fruit were completely absent from CockroachDB, e.g. (IIRC) stored procedures are nowhere to be seen in CockroachDB.
You can't even run pgbench unaltered on CockroachDB, as simple table structures and indexes are fundamentally different there. It is in no way a compatible product, and never has been.
So yes, license (and compatibility - see https://pgscorecard.com) are two major differences between pgEdge and CockroachDB.
pgEdge version updates also come in very close alignment with upstream PostgreSQL intentionally to make sure security patches/bugfixes and the latest features get to users ASAP.
Not the OP nor knowledgeable in this area but I would suspect / hope postgres compatibility as a start. The last time I looked into whether I could use cockroachdb as a backend for my Airflow cluster, it wasn't possible due to compatibility issues.
You're actually 100% correct! CockroachDB is only 57.25% compatible with standard PostgreSQL (according to https://pgscorecard.com, which details the way it comes up with these numbers) whereas we are 100% compatible (and 100% open-source, whereas they are source-available).
Keep in mind there _may_ be a negative feedback loop there.
If you're building your software in a way that won't be able to perform better with superior disk/db/network performance, then it isn't worthwhile to ever upgrade to a more performant disk/db/network.
If it is possible, make sure your software will actually be faster on a faster disk rather than just testing on a slow disk and thinking "well we're I/O bound anyway, so no need to improve perf".
This is a common fallacy. Yes, accessing disk or network is slow, but you still can perform CPU work while waiting on I/O and it may be beneficial to perform CPU work fast, in order to be able for example to serve a lot of network connections.
Was what actually a thing? Leslie? Leslie was definitely a person who existed, who was a sort of local weirdo. I met him, once, probably have a photo I could dig out somewhere.
reply