HN user

cnlwsu

771 karma
Posts3
Comments269
View on HN
Jepsen: NATS 2.12.1 8 months ago

durability through replication and distribution and better throughput to build up more within the window on a lazy fsync

Cockroach doesn't offer strict serializability. It has serializability with some limits depending on clock drift. Also CockroachDB does not provide linearizability over the entire database.

You’re describing compare and swap which is a good solution. You’re pushing complexity down to the database, and remember this is distributed locking. When you have a single database it’s simple until the database crashes leaving you in state of not knowing which of your CAS writes took effect. In major systems that demand high availability and multi datacenter backups this becomings pretty complicated with scenarios that break this as well around node failure. Usually some form of paxos transaction log is used. Never assume there is an easy solution in distributed systems… it just always sucks

Seems like unnecessary shade to throw on the helpline. There was a viral thing a bit ago making rounds on social media accusing them of it but its far from reality. There are like 50k of 3 million calls a year that result in contacting the authorities, but its extreme scenarios.

Its a rare thing and highlighting it as the default scenario is spreading FUD and possibly keeping people from getting the help they need. It is true though that if you call and describe an immediate plan to kill yourself there is some legal, ethical, and liability requirements that mean they will call authorities. Exact same thing if you tell your doctor or therapist.

My son and I made a video game when he was 6 (started at least). I did 99% of the coding, was 3d and math a little advanced but he drew it out, recorded audio and did a lot of research and work for it.

If the kid is excited about project you don’t need to explain much, it’s more holding them back from grandiose ideas. Kid doesn’t need to be a genius, hard work trumps that.

It’s not a real requirement. Just a performance thing. Each partition has an index and as it grows the deserialization of it to find the queried start column takes longer. It is lazy loads but there a perf hit. Easier to have a rule of thumb like “100mb partitions” and have more fixed tps per core etc expectations.

Facebook deleted and moderated the shooters content. Twitter and youtube also both delete and moderate content that violates reasonable TOS that overlaps with apples and googles terms of service. Comparison isn’t even remotely the same. Parler had posts inciting violence and refuse to moderate

I guess I am older but pre jira things were so much worse that yeah... best version of this thing I’ve seen. Not that I love it but it’s functional and not an Oracle form or some ugly crud tool cookie cut for a process different than my teams.

Even if the complete public distrust of the companies ability to be reliable is "just a meme" it's brand damaging and creates a scenario that impacts adoption of new products.

While products come and go is true, it's more a matter of scale on why this reputation exists.

I know I personally have been burned by the platform I was using going out from beneath me. That memory comes up each time I am considering between an AWS (where its never happened to me), azure, and google cloud solution.

A lot of what you just claimed is completely false or misleading, given your rants throughout this thread though I doubt it’s worth time to enumerate it. You seem very intent to distract the discussions for this post towards Apple and whataboutisms.