162 karma · joined July 22, 2013
You also confuse "CDN somewhere" with OpenConnect box literally inside your ISP's DC. It is probably faster to get it this way than it would be to P2P it from your neighbor since, at the end of the day, that P2P traffic _must_ go through your ISP and their ISP. It will not, by definition, peer at the local hub. You are _NOT_ on a local network with your building/neighbors/etc. Your communication routes to your ISP and then out to anywhere else, even if that somewhere else is on the other side of your wall.
Even if it was possible. Even if it was slightly faster. Do you really think studio execs are going to be okay with customers hosting/serving their content off their machines? Even _IF_ this was "technically" a good idea, this is a non-starter from the business standpoint.
This sounds like an issue with being able to articulate why something is or isn't going to net the expected benefits or being able to foresee unexpected risks. Keeping silent is better than throwing out silly hyperbole risks, but not bring up real risks because "they don't want to hear it" is completely bogus. Any solid engineer will bite at another potential risk to ensure they don't find themselves engineered into a corner 65% through a project. Your comment also makes it out like the notion the article is making, monolith over microserves, is gospel for every situation; that in no condition would it ever make sense to use microserves and that only naive zealots would espouse the wisdom (dogma) to use them. You can use any piece of technology poorly, that doesn't mean the core concept is flawed, just that your problem space is different than what that software is trying to solve. Consider using HDFS as a primary data store in place of MySQL where it doesn't make sense and you might cry the wisdom of wishing someone had told you HDFS is terrible and to just use the tried and true MySQL of olden days.
Suppose a solar flare destroyed all existing digital equipment. What would a physical printout of a wallet be worth?
TL;DR Automation will...
* replace some current blue collar work over time
* create new blue collar work over time
* take a protracted period of time to fully supplant all labor needs
Geographic mobility really is a huge hurdle. A lot of business is becoming centralized around major long-distance transportation hubs, San Francisco being chief among them. Live in Concord, but want to work in Los Gatos? Good luck getting there by train. I lived in the Mission and to get to China Basin was a bus to a train to a bus. I opted for the ten minute drive instead of forty-five minutes of transferring. It's embarrassing how much better we could do so much better moving people around. Right now I opt to drive the 101 south instead of taking Caltrain, even though my employer covers the cost, because it would cost me an additional $10 a day to take other trains/buses to get to the Milbrae transfer, and by the time I've driven myself either to 4th/King or San Bruno I could have already been half way to work just driving the whole way. We need to do better.
Here's a better article that was linked a few days ago: http://www.wsj.com/articles/if-your-teacher-sounds-like-a-ro...