In Europe the individual has almost no legal reason to use force, and force by individuals is considered illegitimate. The "Sovereign" has all the coercive power in European states. In the US, however, a certain amount of legitimate force explicitly remains with the individual i.e. the 2nd amendment. (I am not making a value judgement here).

Of course, Europe has government with the consent of the governed, so is Lockean in that sense. But the balance of force between the "Sovereign" and the people in Europe is all Hobbes. You only notice it when you move to the US and compare it to Europe.

Europe had centuries of religious and civil war. It's not surprising Hobbes won out.

Comments URL: https://news.ycombinator.com/item?id=47403350

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46929629

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46925165

Points: 2

# Comments: 0

As for reliability - it's a fault-tolerant, highly available system. Reliability is the reason it exists. :-) If you're asking about quality and test coverage, you might like to check out these resources:

- https://rqlite.io/docs/design/

- https://rqlite.io/docs/design/#blog-posts

- https://philipotoole.com/how-is-rqlite-tested/

Comments URL: https://news.ycombinator.com/item?id=46728197

Points: 186

# Comments: 146

This is the only part of your response that doesn't quite sit right with me. There could be many "highly scrutinized and bureaucratic functions" out there that are working very well, you just don't notice because they work so well. There could be a selection-effect here.

Quality is a big deal for me[1]. But I think you're defining "quality" too narrowly in this context. "Quality" could also mean "allows everyone, at scale, reliably, to do what they need to do." The US Tax Filing system (and its associated software) meets that goal.

[1] https://philipotoole.com/always-thinking-of-the-next-guy/

Comments URL: https://news.ycombinator.com/item?id=46662827

Points: 4

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=46584880

Points: 97

# Comments: 53

Comments URL: https://news.ycombinator.com/item?id=46584860

Points: 2

# Comments: 0

Otherwise, if you try with more modern networks and disks, let me know what you see.

I did introduce Queued Writes[1] since that talk, allowing you to trade off performance versus immediate durability. It may interest you -- network is much less of a factor then, and you should get a 10-100x increase in throughput.

[1] https://rqlite.io/docs/api/queued-writes/

Yes I do have practical experience to share, I wrote a blog post on rqlite and FTS5: https://philipotoole.com/building-a-highly-available-search-...

Will it allow you to reach the same scale in terms of data set size that Elasticsearch supports? Almost certainly no, but it might be enough depending on your use case.

- https://www.philipotoole.com/2021-rqlite-cmu-tech-talk - see slide 33.

- There is also a recording that goes with the talk: https://www.youtube.com/watch?v=JLlIAWjvHxM

You can also read about Performance in the docs at: https://rqlite.io/docs/guides/performance/

An important thing to note: this testing was done 4+ years ago, on moderately-powerful hardware for the time. With higher-end, more modern hardware you may get even better results.

Comments URL: https://news.ycombinator.com/item?id=46569451

Points: 5

# Comments: 1

https://rqlite.io

Comments URL: https://news.ycombinator.com/item?id=46560217

Points: 281

# Comments: 227

Nit: dqlite is a library, it is not a network-exposed database like rqlite is. Sure, it requires connecting to other nodes over the network, but local access is via in-process. In contrast one connects with rqlite over the network - HTTP specifically.

[1] https://rqlite.io