The medium is the vessel
A half a century ago Marshall McLuhan coined this iconic phrase in his landmark book, Understanding Media: The Extensions of Man. In 1964, the most prevalent media were all broadcast: movies, radio, television, newspapers and books all shared this trait. Only letters and the relatively new telephone allowed for interactive communication and discourse.
Fast forward to today and almost the exact opposite is true. The power of broadcast media, while still strong, is not the all consuming grasp it once was. Interactive and collaborative media has become the norm, not the exception. So, then the question begging to be answered is that if the medium is the message, how has this new paradigm controlled “the scale and form of human association and action” as McLuhan put it in The Extensions of Man?
Each member of the populous at large is now an amateur broadcaster, but every message is inherently biased. There is no Walter Cronkite anymore. They are not impartial because each message is the vessel for the opinions and emotions of the individual, not the organization. There is no peer review. There is no newsroom for social media.
Each broadcast is imbued with the raw emotions of the individual who generated it. Individuals who often have no where else for these emotions to go. Individuals who think that their Tweets, posts, and other broadcasts are making an impact. That they are swaying public opinion. This herculean empowerment of the individual through social media has produced behavior that has wider reaching sociological impacts.
The first behavior is what I will call “emotional non-action”. That is, since the medium is the vessel for the emotion of the individual, the individuals themselves feel accomplished. That through their drop of water in the ocean they have been heard by the world.
The second is a behavior that a colleague of mine recently compared to road rage. When someone is in their car, they feel safe. So when a fellow driver cuts them off or makes some other driving mistake, they are emboldened to say similarly awful things, e.g.
“Don’t cut me off you fucking son of a bitch.”
This is, however, what has become a completely acceptable way for one to conduct themselves in public on the Internet. And not just in developer and technology communities where it has been acceptable for more than a decade (remember: don’t feed the trolls), but in our larger society as well. The latter trend has only seemed to reach a critical mass in the last five years.
A good example of this is the tragedy that happened at the Electric Zoo last year here in NYC. If you are not familiar with the incident, Mayor Mike Bloomberg cancelled the last day of the three day music festival because two people had died from drug overdoses. This, while a tragedy, was largely outside the control of any one party. The Internet (through Twitter) decided to blame the dead.
Can you imagine what this did to the parents of these children? Yes. Their children. Can you imagine in your entire life ever saying something as mean and hurtful to their face? Neither can I. But somehow there are millions -- literally millions -- of public statements like this.
We are losing something important
There is an upward trend in this behavior that is undeniable. Within a few years it will be part of our cultural DNA as a society. Maybe we are at a generational divide. Maybe things are going to get worse until they get better. Until those individuals who grew up being bullied by this behavior have children and they can pass along the next version of “if you don’t have anything nice to say, don’t say anything at all”. I hope that happens because what is most important is that we hold onto our ability for civil and public discourse on subjects that we may disagree.
The Future of npm
I have been involved with Node.js for over four years. I was the 8th contributor to npm not long after we all decided that npm had won the package manager for node discussions. Anyone who knows what kiwi is knows what I am talking about. I say "we all" because back then I could actually count the people who were intimately involved with the community. Now, only a short while later I see a massive community of developers who both love and depend on these things I've had the privilege to help grow to what they are today.
Yet even with all of the great changes, one has to remember the values and fundamentals that got us here. The key one of those being openness with a sprinkle of anarchy. Pushing the decisions to the edge of the graph: to the community members themselves. Node grew because it empowered individuals to do more with less. To encourage fundamental concepts like writing modules and piping streams instead spelunking through a monolithic, obtuse API. Help developers put the building blocks together and their applications will almost builds themselves.
How these building blocks are distributed is as important as the functionality they provide. That "how" is npm, which has had two years of 10x growth in a row with no signs of slowing down. The first 10x year is what caught my eye at LXJS in 2012 when I spent my first quality time with Jeff Jackson and Jason Smith who made up Iris Couch: the company that ran the npm registry at the time.
That growth is what motivated the company I founded, Nodejitsu, to acquire Iris Couch in May 2013. Between May and November 2013 downloaded from the public npm registry tripled from 42 million downloads to 153 million downloads. And that growth has precipitated even larger changes, as growth often does. Since the morning in mid-November that led to #scalenpm, when Jason Smith and I were woken up by the third in a series of really bad npm registry outages on our way to CouchDB Conf in Vancouver a lot has happened. These are all facts:
- The Node.js community outpoured support to make the registry better by donating $326k to Nodejitsu through #scalenpm.
- The public npm registry is now fronted by Fastly and Joyent's Manta service and still backed by the CouchDB servers run by Nodejitsu.
- The npm project has lost (hopefully just temporarily) one of its most prolific maintainers.
- Isaac has stepped down as the head of the Node.js project to start npm Inc. with very little details about what it will do.
- Nodejitsu has announced our private npm registries for teams backed by smart-private-npm, and CouchDB at http://registry.nodejitsu.com
This rapid set of changes brings to a head the question: "what is the future of npm?" I don't have all the answers to that and my efforts to help bring transparency have not received much response from the npm team. What I do know is that Nodejitsu remains committed to the community through open source, which was the central motivation for announcing http://registry.nodejitsu.com
The sad state of "Open Source Consumerism"
There. I said it. The green pastures of developer passion are not boundless: they have a finite acreage. A point at which one stops hearing "I love your project!" and "thank you for your hard work" and starts to hear "what have you done for me lately?" or "is this project abandoned?". Developer psychology has been infected with the sickness of consumerism and there is no going back. Don't believe me? Well then, let me find my soap box.
In the Cathedral and the Bazaar Eric Raymond said:
- Every good work of software starts by scratching a developer’s personal itch.
That makes sense right? You probably have written a module or two yourself. Most likely unpopular modules that don't go beyond your own itch. The fun weekend side project that gives you a momentary sense of satisfaction because you "built something".
For whatever reason some modules don't stay unpopular for long. Jacob Thorton, the creator of Twitter Bootstrap, calls this "the cute puppy syndrome": where a developer creates a module because they want to. This is "buying the puppy". Then suddenly, the module becomes exceptionally popular. It "becomes a dog". And maybe you didn't want a dog. Maybe all you wanted was a puppy. Suddenly the guilt piles up and doing what you love isn't fun anymore.
All the developers who help make a module popular (who turn the puppy into a dog) usually have never been on the other end of the story. They have never had to sacrifice to maintain Open Source software. Those who have are more empathetic to the "plight of the maintainer."
Thus: the mantra of "everyone wants to create, no one wants to maintain" rings true across the plains of Github.
What's my point will all of this veiled negativity? Why would I choose to fault a system that (overall) has produced such an enormous body of work? A system that fails to accommodate the exceptional will be doomed to mediocracy. In other words: the attitudes from developers have to change if Open Source is going to continue to grow at its current pace. We need more exceptional creative developers to continue building Open Source software. Maintaining is a lot of thankless, unpaid work, and a lot of developers who become active maintainers burn out and leave their respective communities permanently.
If we continue to loose these kinds of seminal minds without learning from the mistakes that lost them we will change from trending upward to trending downward very quickly. Open Source can continue to eat itself so long as it does not overeat its talent pool.
There is no "apples to apples" in the Cloud
What's in a name? That which we call a rose; by any other name would smell as sweet.
— William Shakespeare, Romeo & Juliet, Act II, Scene II
Probably heard that before right? What about a server on any other metal would compute the same. Probably not. There are vast and complex differences between every *aaS out there. In the IaaS world everyone wants to size up to Amazon Web Services, but there are a lot of vectors by which this comparison can be made: compute power, RAM, network, price and virtualization substrate (e.g. Xen, KVM, Zones, Containers) to name a few.
When looking beyond pure utility computing (such as in Platform-as-a-Service) the ability to perform an "apples to apples" comparison becomes even more onerous. Not just because the units by which power is subdivided, but as the paths between additional services offered (such as DBaaS) are more opaque and thus harder to quantify.
We are at somewhat of an in-pass in the state-of-the-art but there are some very interesting new developments (such as the rise in popular around Linux containers) which will be key to bringing much needed standardization to the industry.
Death, Taxes ... and Email
Growing up I overheard my parents and teachers repeat a turn-of-phrase along the lines of "nothing is certain in life except for death and taxes." As a young man I didn't fully understand the feeling of futility they were trying to convey through this light-hearted colloquialism. As I became an adult my significantly more developed grey matter teased out the nuance I had missed. That is: yes it is futile, but not meaningless. So just pull-up your bootstraps and do it.
Today I submit to you readers that there is a (relatively) new part of our lives that deserves to be grouped with these pariahs: email. This bears repeating:
Nothing is certain in life except for death, taxes, and email.
Remember that: yes, it is futile, but not meaningless. In other words: it is a certainty of life that you must learn how to conquer and accept or it will consume you. In many ways email has (in many forms) simply replaced the former necessity of letters, but the rapid pace has changed the medium itself. If you're looking to learn more about the art of letter writing from primary sources I highly suggest The Proud Highway which chronicles the early life of author Hunter S. Thompson's through the letters he wrote to his friends and colleagues.
Perhaps this is where you go back to Twitter and think to yourself "pfft, Twitter saved me from email." Before you do consider this: new communication media may have become popular, but they only supplant email for certain groups in your life, or for certain categories of communication. On top of that many of these media simply regress back to email under heavy usage making the same acceptance of regular communication through long-form text tantamount to success.
EmpireJS by the Numbers
With that in mind, I've taken the time in this post to outline how we organized the conference and more importantly what the budget looked like. It is my hope that this information will help other would-be conference organizers and help the community as a whole because when we first started organizing EmpireJS one of the biggest problems was how much to budget for each particular detail.