Skip to main content

Microsoft Lovers versus Open Source Lovers versus The Battle Itself

The battle has gone on for a very long time. The Microsoft developers hate the open source hippies. The code huggers hate the corporate dogs. When does either side realize the dagger they're digging in is piercing themselves, because we're all the same.

We code because we like it. Software is our craft and development tools, languages, and software ecosystems are the spice racks for us chefs of bytes. Some chefs enjoy working on the grill, and others can't get enough from the stove. But if backyard grillers love a good lasagna and bakers enjoy a barbecue, why can't our camps live and let live? Joe likes GNU tools and Mary builds Silverlight apps in C#, so obviously they need to glare at one another with malice, right? Wrong.

Can't we all just get along?


Labels:

Comments

Paul said…
An interesting collection of metaphors in use here to frame anyone who disagrees with your message almost as some kind of extremist, but anyway...

Can Microsoft and the Free Software movement get along? Yes and no: there are certain areas where Microsoft actively seek to undermine Free (and open source) Software by, for example, promoting software patent legislation, and there clearly is a need to oppose this in the wider software development community - yes, even amongst proprietary software vendors, too. I imagine that Microsoft feel threatened by Free Software, too, but as long as Microsoft have the "consumer" market locked down with obligatory Windows on every machine, I don't much care for what they don't like.

Can Joe and Mary get along? Well, even though Mary's toolmaker wants to stifle competition from, amongst others, Joe's toolmaker, they'll still have mutual technical interests, yes. But the referenced article shows what happens when you put your head down and claim that cool tools and "the code" is all that matters.
6:11 AM
Post a Comment

Popular posts from this blog

My Software Job Transition Strategies?

I’ve been spending a good deal of the last two days preparing mentally for starting a whole new challenge as a developer. New things aren’t new to me, but this is different and big enough really call for some Deep Thoughts ™. For one thing, I’ve made a big move from the world of Python web development to totally other Python work and while web development has never been the only thing I do, it has been the only work that paid the bills. That transition isn’t one that bothers me or daunts me, though. Instead, I’m thinking about transitioning to the scope of the work I’m getting into. For a long time, I juggled multiple clients and client projects every day, so no single project usually took up most of my time. Every developer juggles time through the day, but exactly how that works in each company and on each project varies a lot. I was looking for a place that I could really focus in a way that I haven’t for a long time. I think I found that, but now I have to deal with the consequen...
Post a Comment
Read more

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...
1 comment
Read more

The Snake Pit is About to Burst

The signs are all over the place. I can count at least five implementations of Python today: CPython, CL-Python, Jython, IronPython, and PyPy. The use of the language is sky rocketting and set to grab real mind-share as the hype over Ruby subsides. Things are looking good for a favorite green snake and british comedy troop reference, aren't they? Trouble is on the horizon in the very ingredients that could push us into true success. Our community and our very language is in danger of segregation, unless we all do something about it and learn to get along. One of the most visible dangers (to me) is being ignored for various political, cultural, and non-technical reasons. IronPython's users are increasingly pushing IronPython-only recipes, libraries, and tutorials. No one is talking about the transition of the alternative implemenations to CPython 3.0 compatability. To make matters worse, we still can not define the language without refering to an implementation. This is very un...
11 comments
Read more