304 karma · joined September 23, 2016
https://www.theguardian.com/commentisfree/2011/apr/05/anti-n...
The side effect of not needing to use energy to haul your energy source around is pretty cool, too.
You're right, we shouldn't bother doing anything, we should just tell them to clean up their act.
https://www.npr.org/2014/11/13/363517842/for-decades-kodak-s...
Anyway, the question was, "how do they compare?". Personally, emotionally, they're pretty damn cool, but way less exciting. More so than can be hand-waved away as simply being older and more cynical.
Pretty much the whole (western) world stopped to watch it. It felt very much like returning to space for the first time since the end of the Apollo project (it wasn't, but it felt like it), it was such a step change from the previous generation of rockets. This was science fiction in action, it was going to revolutionise space travel. It even looked like a new form of transport, and the speed with which it cleared the gantry was amazing to people used to a Saturn 5.
We taped it off the TV, and I remember going back to watch it again multiple times.
It worked fine. The founders were fairly enlightened people, and well aware that we were in this for the long haul - success would take time and nobody could work long hours without the quality of the work suffering.
This wasn't the case for all staff, mind. There were definitely people in some roles who worked longer hours. Marketing and PR mostly.
Custom/self builds are famously hard to predict, and nearly always go massively over budget and over time (twice as long, twice as much is more common than on budget, on schedule). Often because there are significant changes to the requirements as the project goes on, because the customer changes their mind, or because unexpected things are discovered during the build.
In fact, with the arguable exception of teaching, which is a classic example of deliver to deadline with no specific set of features, all of your examples are things that people are unable to accurately predict.
Whether it would improve the quality of the comment sections is an interesting question. I'd be interested to see that tested somewhere ...
I understand not wanting to learn another build tool, but I have no regrets where I've moved to gradle. It's so much faster on a project of any size it's stunning.
90% of maven projects don't do anything terribly complicated. Porting them to gradle leaves them uncomplicated and unexciting. I just wish there was a standard release mechanism. Poor as mavene-release is, at least everybody uses it and understands it.