thepumpkin1979
Joined 16 years ago
Karma
2,389
Submissions
429
Member since
May 28
Recent submissions
Comment · 8 years ago
To me the following are the main differences:
- CRDB talks Postgres Protocol and Dialect, TiDB talks Mysql Protocol and Dialect.
- TiDB is OLTP+OLAP, CRDB is OLTP only.
- CRDB is a single binary, TiDB has more moving parts/can be used in different ways.
I picked CockroachDB because it's Follow-the-workload[0] and Interleaved tables[1] included in their Community Edition, I'm a Postgres person so it was a natural fit. Also it's the little things, I made a comment in a closed issue and somebody paid attention in less than a day[2] which makes me feel closer to them.
On the other hand, the fact that TiDB claims OLTP+OLAP feels like they're moving faster than CockroachLabs, PingCAP also says they have 25 companies using TiDB[3] where CockroachLabs has less than 10 known study cases[4].
[0]https://www.cockroachlabs.com/docs/stable/demo-follow-the-wo...
[1]https://www.cockroachlabs.com/docs/stable/interleave-in-pare...
[2]https://github.com/cockroachdb/cockroach/issues/24932#issuec...
Comment · 8 years ago
They just wanted to say this:
> The decline in RHEL growth contrasted with the acceleration in Linux more broadly is a strong market indicator of the next wave of open source. Public cloud workloads have largely avoided RHEL. Container workloads even more so. Moving at the speed of developers means embracing open source in ways that have led the world’s largest companies, the world’s fastest moving startups, and those who believe that security and velocity are best solved together, to Ubuntu.
Comment · 8 years ago
I've been using CRDB 2.0 for a toy project for a few weeks now, today I notice 2.1 was available so I started playing with some of their new features, I ran a SQL query with correlated sub-queries and then the server crashed. It's the first time I see a crash, so I rushed to the GitHub report to report the bug and to my surprise a GitHub issue was already created for the crash[0], it included the stack trace and an anonymized version of my SQL query that caused the crash.
This really demonstrates they really care about the stability of their product, one more reason to keep recommending CockroachDB.
Comment · 8 years ago
OP, this is the comment you should be paying attention to. The (now downvoted to oblivion) counterpart to this comment sounds a lot like the top comment on Dropbox “Show HN” of it’s time: a totally engineered reasoning with zero core product value thinking [0]. Instead you should go deep, as in digging a hole or “Well”[1].
[0] https://news.ycombinator.com/item?id=9224
[1] http://paulgraham.com/startupideas.html (special emphasis on the the “Well” section)
Comment · 8 years ago
Interesting, in my mind the memory usage of M threads is too expensive when you’re mostly waiting for network or file system events, the advantage I remember from green threads is that the thread can be used to execute another CPU bound task while waiting for network events which intrinsically makes it more memory efficient. I’m interested in how Linux has evolved to reduce memory consumption when you have millions of threads, because you can have millions of green threads.
Comment · 8 years ago
Comment · 8 years ago
Exactly. I like the idea of having VSCodium as an option but I don’t have an urging need to use this fork since just removing a license and telemetry endpoints doesn’t really add any value compared to the official package.
Comment · 8 years ago
I downloaded it and launched the Browser sample Xcode project, take a look: https://vimeo.com/284388678
Comment · 8 years ago
How has AMD managed to come up with more processor and speed count the Intel? Why now?
Comment · 8 years ago
Nice, all CI should be per minute.
[ my public key: https://keybase.io/bithavoc; my proof: https://keybase.io/bithavoc/sigs/hnNGLznSOr1zX_yAzaBkc6q6nm2rgBDs3Bk7CKVggeI ]