The vote by the stockholders was approved to sell Sun Microsystems in July 2009.
This will be my last blog at Sun Microsystems. I do not know what the future holds at this point. I imagine that I will be told along with everyone else when/if the Oracle acquisition of Sun occurs. I am ending my blogging at Sun because it just feels like the right time to do this and I want greater flexibility in expressing my personal views. I do clearly understand and respect the legal requirements when a company is being acquired.
I chose the photo above because my best memories of Sun were at Sun's Club for High Achievers and that was called Sunrise Club. I was fortunate in that I was selected to go to 7 of them in my career.
Sun Microsystems will be just a memory, but a GREAT memory for those of us who put in a lot of blood, sweat, hard smart work, and fun all while creating lifelong friendships. I came here as a true believer in "Open Systems for Open Minds" and that has been part of my DNA. I will always bleed Sun purple :-)
What was the most fun I had at Sun? That's really easy. Working with Dave Patterson at Berkeley to reinvent the machine tool industry with MTConnect.


What was I the most proud of? My oldest son, John, being selected Sun's Campus Ambassador of the Month out of over 500 Sun Campus Ambassadors.
What team effort at Sun am I most proud of? That is much harder for me. I would say it would be a three way tie:
- The East Coast Technology Center (ECTC) that was an all SE volunteer group that created a Technology Center that held over 400 benchmarks and POCs in the Dunn Loring and McLean, VA Sun Microsystems offices.
- Software Genius University (SGU) This was also an SE led effort working with a variety of groups around Sun that put together over 740 hours of content.
- A little background history...
Sun SGU grew out of the extremely successful Software Genius Program (SGP). The
genesis of SGP was a conversation that Scott Radeztsky and I had in the fall of
2005 when we asked the basic question, "what can we do to help the SEs to
embrace the developer and Sun's software stack?" In January 2006, we kicked
off the Software Genius Program Council (SGPC) where the SEs in Americas
Software Practice created ten courses, or twenty hours, of software training.
This program had one goal - to ensure Sun's Systems Engineers were properly
equipped with the necessary software knowledge and skills to be successful.
Sun SGU served a very important need when it was announced globally on July 1st
2007. SGU now has 740 hours of course work in it and the best of that content
will be transitioned to Software University. There are countless individuals
who should be thanked for the (literally) 1,000s of hours that went into Sun SGU.
We will continue to make the necessary student competence mappings transitions
from the Sun SGU's University certifications levels to Software University's
Accreditations much like we did with the global Solaris training that came out
of Dan Berg's organization last FY. We will make it very clear regarding the
how, when, where, why and what as we go through this effort. - Last but not least, was the High Performance Workstations opportunity that put $2BILLION (Billion with a B) into Sun Microsystems over the years.
-
A little background history...
When I first spoke with Sun Microsystems, it was the summer of 1984 and Betsy MacLean (later Ferry) and Steve Ferry had recently went over to Sun Microsystems from Systems Development Corporation (SDC) a Division of Burroughs Corporation. I met Betsy and Steve while we were all at SDC. It is interesting to note that SDC based in Santa Monica, California, was arguably the world's first computer software company as noted by Wikipedia. I was not smart enough to go over to Sun in 1984 :-)
Sun was founded in 1982 with Sun standing for Stanford University Network (SUN).
In 1986, I was an SE for SDC and technical lead for a HUGE and extremely challenging opportunity for High Performance Workstations opportunity where Sun Microsystems was the digital workstation and Masscomp was the analog workstation of choice. At the end of 1986 and long after the completion of the bid and benchmarks, I started talking to Sun Microsystems about working there. I started on May 4th, 1987.
Betsy hired me and was a great manager and leader. My mentor was Neil Groundwater who was clearly the smartest person in computers that I had ever met. In the summer of 1987 we found out we won the HPW business that has since been worth at least $2 BILLION to Sun Microsystems over the years - yes that is B as in BILLION. Steve Ferry was THE Sales Rep on this opportunity and to this day is far and away the best Sales Rep I have ever seen/worked with and a great friend to this day.
I already thanked Scott, Bill, Andy, Vinod and John previously, but you can check it again here.
For everyone else, there are way too many people to thank from fellow employees to customers to partners and most importantly - family and friends.
Most importantly, I must thank my beautiful wife - Julie - for all her support through thick and thin.
If you are interested in following Dave Edstrom's blog, my private blog is at:
I will definitely keep blogging on software, technology, life and of course Corvettes :-)
You can also reach me here via LinkedIn:
My private email is edstromvette@yahoo.com
I would be a liar if I did NOT state that I am bummed that Sun Microsystems had to end this way. As the often quoted old poem by John Greenleaf Whittier. (1807–1892) goes:
"Of all sad songs of tongue and and pen, the saddest are these, what might have been....."
Stay in touch, take care and remember the three things that I, Dave Edstrom Sun employee #3705, always tells people:
- Life is short.
- Death is certain.
- If you do not make your own decisions now, time will make them for you....







Hello Dave,
Thank you so much for putting efforts on creating this article.
What i understood from this article is that, open source project cannot be a standalone project as it must be backed up by enterprise versions which generates revenue for open source projects as well, and when the feature of open source project gets stable it will be transformed to enterprise version.The developers and employees developing open source project gets their income from the revenue generated from enterprise versions.
I hope i understood exactly as u r trying to make me understand.
If not please clarify me.
Thank you so much.
Yes, you are absolutely right. That is the general framework. Where things can get a little more complicated are the corner cases. What becomes extremely important is the latency or delay between the Community Version and the Enterprise Edition.
Let me give you a specific example. Let's say we have a Community Version that has nightly builds. Let's also say that we have an Enterprise Edition that was being released semi-annually. If the Community Version introduces a specific feature that the market place is clamoring for. Let's use as an example a Enterprise Service Bus (ESB ) with a new healthcare protocol adapter. If the customer base is clamoring for this particular adapter, the obvious question jumps to the forefront:
Does the new healthcare protocol adapter have to "wait" until it is rolled into the Enterprise Edition from the Community Version?
There are different ways that some companies address this situation. Some companies believe that you never, ever support the Community Version and you simply tell the customer to wait until the healthcare adapter gets rolled into the Enterprise Edition. Other companies believe that you do support the Community Version, but do it from your PS services group at a premium cost with the idea that you move your customer to the Enterprise Edition as soon as the healthcare adapter is officially supported.
My personal view is that when you are designing your Community Version and Enterprise Edition monetization framework, that you carefully review what makes sense to have as plugins that can be rapidly supported in the Enterprise Edition. Keeping with the example above, it would certainly be logical to separate out the protocol adapters to allow for flexibility in official product support in an Enterprise Edition. I also believe that it is perfectly reasonable to have certain plugins as non-open source in the outer ring of the Community Version/Enterprise Edition monetization framework.
There is a hard core group of open source enthusiasts who firmly believe that EVERY line of code must be open source and the only two driving factors are indemnification and support. These hard core enthusiasts call anything that is not totally open source as being crippleware. I believe crippleware is software that has had a critical piece of code purposely removed from it. An example of this is not allowing saves to a file or limiting the size of a particular structure or file. I do not subscribe to this view that EVERY piece of code must be open source. I believe that it is a balancing act between the Community Version and the Enterprise Edition.