1,667 karma · joined December 21, 2010
The optimization opportunities for some packages are typically on the order of 2x-5x faster, which isn't enough to deal with the headache of extra config for a personal dev box. So, my rule of thumb is, unless I know exactly the performance trade off I am trying to take advantage of by going with MacPorts, I will be better served by using Homebrew. I will wind up spending more time fixing config then I will have saved on execution processing time.
In keeping with the No-Free-Lunch theorem, it's also highly desirable in general to have a variety of approaches at hand for solving certain predictive coding problems. Yes, this makes ML (as a field) cumbersome, but it also prevents us from painting ourselves into a corner.
I generally try hard to remove bias/noise from data before analyzing it, but I also add noise back in later on... e.g. jittering data for plots, or putting a noise feature into a model to establish a threshold for useless features. I'm also a bit miffed that I had to discover this all on my own... Noise is useful and interesting! In business-oriented analysis, noise can be even more important, since changes in "data noise" can indicate important changes in business patterns, or problems with how they're collecting data (companies seldom share this information with analysts beforehand). I'd go so far as to say that understanding the noise in a dataset is the primary concern for most of my analyses these days.
Here's a good book with more pop-sci noise examples: https://www.amazon.com/Noise-Bart-Kosko/dp/0670034959
The article bills Vapor as helping to decentralize the "data layer" of an api. This naturally has some immediate caveats... like... this sort of framework would not be suitable for real time or streaming Apis.
Also, the article doesn't really touch on the cost of maintaining all of this. It's true that vapor api hosts can charge a small transaction fee to maintain/run their processing nodes. I have to wonder what that looks like, and if people are willing to pay a per-request fee for an http transaction.
I don't believe this is intended to replace standard authentication, and calling out how it's impractical for common scenarios is fair game. However, I think it's more interesting to think about scenarios where this might be useful.
https://www.eff.org/deeplinks/2011/04/unqualified-names-ssl-...
https://security.googleblog.com/2013/12/further-improving-di...
Vapor also addresses decentralization in distribution of content as well.
I'm extremely skeptical of Vapor for other reasons, but we ought to at least keep the value proposition clear here.
I suppose you'd have to factor in other issues in the "real" world, like managing inclines, curves, and starts/stops for traffic. Boats generally have fewer constraints on those fronts. Also, boats can increase their size in more than one dimension, which lets them increase size more geometrically and efficiently (trains can only get longer, and hits practical length limitations faster).
I thought it was a drawback at first, but now that I've moved away I kind of miss it.
In short, doubling the weight on a ship does not double the energy needs required for moving it. The same can't be said for wheeled transportation, let alone air. Batteries are very heavy, but on boats this doesn't have to be a big negative.
However, we're not talking large amounts of freight here, this is more or less a personal watercraft. Also, for personal watercraft most of the energy is spent on accelerating and decelerating, something that boats are not as efficient at.
So, good idea in theory, bad idea in application.