Are we moving away from good "at scale" programming?
So I was watching a video that recently came out about developing in python: http://vimeo.com/63377197<p>Watch the guy who talks a bit later. He works for disney and explains about his project called fastpipe that he developed addressing many of the concerns of modern day code usage of parrallelism.<p>He makes a lot of notions about how software developers are moving away from developing on their single developer machines and instead are getting a large headache from doing so by using node-based multicpu programming!<p>Hadoop is horribly inefficient at best it seems for it's overhead. And reliability seems to be becoming more and more of an issue.<p>He was able to achieve decent results computing using python which is known to be a slow language by finding good reliable ways of doing the parallel code development. He makes a lot of assumptions about reliability that also are very interesting decision wise that show that he has programmed for years.<p>I was wondering what other people think of some of the things he is saying. Are we moving away from the right decisions for developing parallel code?<p>It seems like we are getting away from the learning how to split things up into processes right without conflicts. And we don't really know how to always pick the more reliable code.