dsturnbull2049

Scrubbing the entire raid volume is significantly different from scrubbing every piece of data as it gets written/read.

First, in between your monthly/weekly scrubs your disks/controllers will be silently corrupting data, possibly generating errors on multiple devices resulting in data loss depending on raid type. ZFS detects corruption much more quickly.

Second, your traditional raid recovery is to rewriting the entire device to fix a single block. Let's say you're using RAID5 and you're rewriting parity. You get another block error. Oops, now you've lost everything. Since disks have an uncorrectible block error rate of 1 in 10^15 bits, you only need a moderately sized array to almost guarantee data loss. ZFS rewrites corrupt data on the fly.

A corrupt file in ZFS indicates multiple broken disks. Copy the file in from a backup, use raidz3 and/or set copies=2 for critical zfs volumes. https://blogs.oracle.com/relling/entry/zfs_copies_and_data_p...

This is one of the key strengths of ZFS. Your log file would be silently corrupted without checksumming.

Sure, it's not as free as platforms in niche markets. I don't have access to much of the equipment I own, but I don't care about a lot of that. My phone falls into that category.

Anyway, it's all about relative freedom. The 30% tax is not the 5% royalty of yesteryear.

$100 to push to the App Store is not the $30k to licence developer kits of 10 years ago.

A market of hundreds of millions is significantly higher than anything ever seen before.

The level of censorship that ecosystem owners exert is much, MUCH lower than before e.g. http://www.jjmccullough.com/Nintendo.php

iOS' ecosystem is experience rapid Glasnost. Android's is tightening up. Both are immensely more free than anything else, historically and presently. This is a question you have to look at over time.

How is this not exciting, and at the same time, completely compatible with the existing and unthreatened harder-core PC market?

I think the OP's problem is we're living in a dark age of gaming, much like the Atari bust in the mid 80s. New ideas will arrive and fix the gaming aspect of this.

For the first point, perfect is the enemy of done, and that's (to me) quite evident in the progression of iOS and Android over the years, those platforms having different thresholds for what they think is acceptable for release.

I understand that security problems are not the empowering aspect; that was snark. Still, I don't see how these aspects relate to games.

The comparison between console ecosystems and app-store ecosystems is meant as a counterargument against your feudalist claim. We've never been freer as we are now on iOS and Android, and as you say, it didn't solve anything. And with me not seeing any restrictions on these platforms relevant to /games/, then that leaves a totally unsatisfying argument.

Couple of problems here. You forgot about battery life, which is the primary reason to lock a platform down. The supposedly empowering aspects of instability and insecurity make the PC a shitty platform, too. None of those have anything to do with games. The 'closed app store model' is a million times more open than the preceding models. Ever try getting a game published on a console, or preloaded onto a pre-iPhone mobile? Or even Steam, right now.

Yeah, a stack machine. https://github.com/dsturnbull/stack_cpu

What I mean by missing files is that it's so clean that at first glance it didn't look like the whole deal :)

Very concise implementation. I keep thinking there's missing files or at least I'm missing something in my understanding. :)

I wrote a 0-operand VM in C a few years ago that used a lot of the same concepts but considerably more code, like 10x at least. I will learn a lot from this.

Python and Ruby are just as bad as Perl for this. Python being the least fluent of the three for scripting.

If you want a proper language to support your scripting goals, then if you go right up to something like Ocaml or Haskell you'll skip all the pointless stringly-typed problems of perl/ruby/python.

ZFS is not limited to your concept of a file system either. Any change is represented by the addition of a series of one or more blocks, which can be seen as direct equivalents to blobs in git. ZFS is copy-on-write, so you can always reference any particular content change regardless of what file it was called when you made it. Compression and deduplication are handled almost the exact same way as you'd expect.

One argument you might make is that the democracy peace theory is really just the Anglosphere. As Bismarck put it, "never underestimate the fact that Britain and America speak the same language."

You wouldn't imagine a civil war amongst a homogenous culture. I wonder if the Parliamentarians/Royalists or the Unionists/Confederates were more culturally different than the Anglosphere cultures are today.

I'm not quite up to speed on how bad the UK's and US's electoral systems were at the time, but a lot of the British Empire had universal suffrage, e.g. AU, NZ.

Germany had tiered suffrage until the 1918 revolution.

"This distribution meant that a first-class vote had 17.5 times the value of a third-class vote." and "... one result of which was that the industrialist Alfred Krupp was the only person able to vote for the electors in the first class in Essen."

http://en.wikipedia.org/wiki/Prussian_three-class_franchise