CheezeIt

Its issue trackers. There have been sad bugs going on years deep into the project. Maybe they’re all mopped up in 2022 but I wouldn’t count on it. Its design does well on a certain usage profile at the expense of mixed read/write or other workloads. Cockroach has more money and could throw better developers (more experienced) at the problem. Haven’t looked at Pebble though.

Along with the other reasons, Badger is not that great. When you have the funding and presumably the developers they have, it makes sense to do something better.

Pebble is a key-value store, not an SQL database.

So you think, what, any forcible annexation of a country is genocide because it has fighting? That’s not the definition. They aren’t exterminating Ukrainians, defined ethnically or nationally.

By your own claims, and the definition of genocide.

This isn’t a “genocidal” war.

They’d have to have built up troops while the Olympics were being held.

Crossing open water is tricky to do on short notice; they were hosting the Olympics; they have all the time in the world; the U.S. isn’t actively fighting in any war; they have domestic financial problems to focus on and a lot of room for domestic growth, which would improve their position even more; their biggest risk is regime collapse, and invading Taiwan worsens that risk.

This is just a fact. The police are better in wealthier municipalities because they can pay for better recruits. This includes higher crime big cities if they have a decent tax base.

In my experience, no. I’ve only gotten pulled over when I was pretty much asking for it. When people say they get pulled over often, I usually find stuff out like they were doing +20 on a residential road. But this is in nicer parts of the country.

Wealthier cities can afford higher quality police officers.

> It isn't supposed to be profitable!

It’s supposed to break even. It’s supposed to be a service that provides value. If it isn’t providing value, it loses its reason to exist.

You can argue that the consumer captures a lot of surplus value from the postal service. But it doesn’t exist just to please people who like public programs.

The same with libraries.

It’s not in any way a constitutional problem.

HBR has been at this level for a while.

They have broken this rule.

The purpose is to protect Americans’ human rights.

This is partly true — for example, two quartz clocks might both have crystals age at the same rate.

Both are, up to the level of drift between them.

Another atomic clock.

In the sunbelt or not? You’ll get more power outages in places with weather and overhead power lines with overhanging trees. AZ also tends to have newer infrastructure.

The funny thing about many old U.S. cities is that they were designed up-front to have wide streets.

Do you understand why we have a patent system?

Yes, exactly!

Every day you slow down FSD development with this kind of safetyism, a hundred people die in car accidents (in the USA).

But why were you wearing a mask outside?

> That would be whole-progam analysis which isn't done.

That doesn’t matter.

> This breaks down with mutation, especially atomics, which are allowed as struct fields.

Not true at all. First, the compiler could refrain from doing this sort of code generation on fields with atomics (or any kind of mutable cell). Second, the object could be misaligned in some local contexts sometimes but references passed to functions could be always properly aligned. So a RefCell or atomic could still be copied or moved out and mutated, then moved back in, when the object is known not to have any references.

In general, this is close to reasonable code generation — a local struct could have some of its parts in registers. Its parts might be in noncontiguous stack locations. A language spec needs to specify that a field can be referenced or accessed via its pointer. It might also distinguish this from an alignment guarantee.

It has majority opposition in California.

There could be some loophole. If the program globally never makes a reference to a field, must it be aligned? If the field is referenced, could it be that when making a reference, the field gets copied or moved out and a reference is implemented as a pointer to that copy?

An open source non-sql db is a tough business model. I mean, here's a simple question: Would you use DGraph? Would you pay for it?

With something like CockroachDB or TiDB I can easily say yes to that. The value proposition is clear.

I think Dgraph's DQL is a worse interface than SQL; there are some aspects of it that give me the heebie-jeebies.

YC doesn’t seem relevant to the situation, it’s just an investor at this point.