I cut the below montage-y overview of the history of enterprise open source from a Register piece I’m working on. Here it is!
For me, the dawn of enterprise open source was somewhere around 2001 when IBM committed billions of dollars to shoring up Linux. Around this same time, the Eclipse Foundation (also launched by IBM) started it’s IDE market re-rigging, and the Apache Web Server was climbing the hill to market dominance piloting the way for the rest of the Apache Software Foundation.
Java’s history is representative of open source’s involvement with most infrastructure software. Java started as closed source, holding onto that model like a waterlogged man hugging floating detritus. Despite this, in the 2000s Java’s course was changed by the influence of open source with the likes of Fleury’s JBoss crew (how I miss their pirate-like antics!), Apache Tomcat, and the Spring Framework. These and so many other open source projects acted as forcing functions for innovation in Java and still do. Eventually, Sun open sourced Java, both JBoss and Spring were gobbled up by larger companies, and open source became the norm in the Java world.
To top this all off, Microsoft open sourced .Net in 2014 and now supports a wide array of open source software in its Azure cloud. Open source is the de facto standard when it comes to new infrastructure software.
I started a new column at The Register, on the topic of DevOps. I used the first column to layout the case that DevOps is a thing, and baseline for how much adoption there currently is (enough, but not a lot – a “glass almost half full” type of situation). I was surprised by how many comments it kicked up!
Next up, I’ll try to pick key concepts and explain them, along with best and worst practices for adoption of those concepts. Or whatever else pops up to fill 800 words. Tell me if you have any ideas!
(You may recall had a brief column at The Register back when I was at 451 Research.)
One of my collegues at 451 asked if I’d be interested in taking over his column at The Register. Of course I would, that’s only about my favorite news outlet ever. My first column is up now, all about what feels to me like the re-emergence of the developer market (tools and middleware), a theme I’ve been puttering about with at 451 for those who’ve been following along.
Here’s the last bit of the column:
Will the developers finally pay for the tools they use to make their write and run software? In the consumer space of $19bn exits, oddly enough, perhaps not: many of the old ways hold true – there is still DIY pride and 20-year-olds with nothing better to do than code all night.
Outside of the Ramen-noodle-coated technology world, however, as more devices get IP addresses and need software accordingly, it’s not full-on bonkers to think that there will be more developers at “normal” companies. And that’s the meat-and-potatoes of any “infrastructure” play: the mainstream companies which would rather purchase tools and middleware than quickly polish off another cup of Ramen before firing up a bare-bones editor to type up yet another chunk of middleware from scratch.
I’ll be doing this monthly, so there’ll be something more up in April. If you still know how to spell RSS, here’s the feed for my pieces.