So there is no difference between me and the core developers?
Core developers represent a double-edged sword. They are critical for getting the network adopted, and for adapting the network to new demands, but they can also be a risk due to their influence. By all accounts, the Ethereum core developers have been open and responsive. Not all Ethereum devs wanted this fork. I do think they could be faulted for not strongly advising Slock.it to cap The DAO. That may be one reason why they were amenable to a refund solution.
You definitely should consider the core devs when investing time and money in a blockchain. They have an inertia that influences the system.
you can see that the miners have indeed enforced the hard fork chain.
Is block number the last block number to be processed under the chain? Is it a monotonically increasing number? Is the block hex string meaningful in the context of showing me what's going on (the site seems unable to show me any data related to the non-fork block so who knows.)
What does the difficulty percentage and total difficulty entries mean? How do they relate to each other? The linked reddit post doesn't shed light on it. I am guessing from bits of conversations on that reddit post that "fork" = new client, fork; "non-fork" = new client, no fork; and "legacy" = old client, no fork?
Maybe it's reflecting the difficulty of me figuring out what is going on the page? :)
Obviously the HF isn't ideal, but not forking was potentially much worse. This settles the issue, and allows people to get back to work.
Hard forks will become less viable as a solution the larger the network gets, and as more interests are involved. However, blockchains are consensus mechanisms. Anyone can propose a hard fork update at any time.
Here is something to consider: as more than 80% of Bitcoin's hash power is in the hands of a few Chinese companies, the CCP could very realistically enforce a Bitcoin hard fork.