In March of this year I switched to OSX, running on a shiny new 17” MacBook Pro. I wrote about it here. I prepared myself for the change, and I was committed to giving it a fair shot for my computing time.

The initial feeling of running OSX was one just like driving a brand new car. Everything was shiny, worked well, and it had the new OS smell. Oh, there were some unsettling moments early on, like when I realized that the OS was not case-sensitive. ( Leopard ). But, overall it seemed like it was going to be UNIX enough for me. Don't get me wrong. There are plenty of people who know UNIX far better than I. I am just saying that it is my preferred environment, and as such, I expect UNIX to behave in a certain fashion. Now that I have given OSX a fair shot, I feel that I can properly give the OS a proper evaluation.

The good part was the hardware. By far the MacBook Pro is the most solid laptop I have ever used. It is fast, the screen is bright and clear. I love the keyboard, and I also purchased an external keyboard, so I could have the feel of the laptop keyboard all the time on all my computers. I can not say enough good things about the keyboard. The touchpad is awesome, it is what touchpads should have always been. Click anywhere is great, response is great. Hardware grade : A-

What did I like about the software? Oh, oh… I got one.. I liked the office suite. I have not used MS Office for many years, I have used many open source alternatives, and have settled in on OpenOffice handling my day to day word processing and spreadsheet duties. When I got the MacBook, I also got a copy of iWork. I liked that it was very clean and uncomplicated in presentation and use. For simple word processing and spreadsheets it worked fine. Software grade : C+

Working in OSX always felt like something was missing. The context switching of the menu bar with the application drove me crazy. I want one thing that is for my Windowing environment and the context of my apps to stay with my application. Of all the idiosyncrasies that come along for the ride with a MacBook + OSX that is the one that I could not overlook. Have you ever heard a Mac guy say “It just works!”? Well, they are lying. A lot of stuff works out of the box, and the stuff that doesn't is a pain in the butt. The Apple faithful make a lot of excuses about what doesn't work, or they have a band of wood nymphs that crank out apple script to patch and band aid the OS. My biggest gripe about the OS is that it is not case sensitive. It is supposed to be UNIX!!! Unix is case sensitive. See how I typed the word Unix in the last two sentences? Unix can tell the difference, OSX can not. I know there is an option under Snow Leopard that if you wish to reformat your drive, it can be case sensitive now, but out of the shoot, nope…

Did my printer at home work with OSX? Nope. This is not Apple's fault, just an example of how things just don't always work.

I really like music, and I have a large digital collection of music. That should sum up why I dislike iTunes and refuse to use it.

Did I say that my biggest gripe was the case sensitive thing? I was wrong, the biggest issue is spinning beach balls. OMG!!! I am just trying to switch between one terminal session to another, and I get get a spinning ball. Click on firefox, spinning ball. Click on netbeans – beachball. Fair enough, netbeans is a big java app, switch to vim… beachball. You gotta be kidding me! I wait out the service pack 1, errr, I mean software update. Surely it will fix this beach ball mania. NOPE!! This is seriously impacting my work. I can no longer use the Macbook Pro as my primary work system. I switch back to my desktop system ( runing Linux ) for my day to day chores. I use the MacBook as my secondary system, reading mail, and web surfing. Guess what? I still get beach balls. I have an old 486 laptop with puppy linux on it that can handle email and web surfing. While we are in a big push at work to get a release done, I vow to hold out until there is time to remedy the situation. There is only a couple of weeks or so to go until the next version of Ubuntu is coming out, and I am ready to try it out, I can make it until then, I tell myself.

WRONG!! The wireless networking on the MacBook Pro has stopped working. Now it is not even good for email and web surfing. I have an expensive aluminum hand warmer now. Stupid Mac.

I think that it must be the hardware, but how can I tell? I hook up and external drive and do a time machine backup to it. ( Oh, just so you don't think I am a complete hater, time machine is awesome. )

Then I prep the system to dual boot. I start here https://help.ubuntu.com/community/MacBookPro

But, decided that I needed to wait for Karmic Koala. I got a secondary partition created, and installed Windows 7. In the spirit of competition and fair play, I installed Windows 7 on another Dell laptop and in a VM on my Linux desktop.

In a head to head evaluation of OSX and Windows 7, Windows 7 wins. Once I installed my tool chain on Windows 7, it worked well, without any issues. I did have to install a few more things, but the installs were clean, fast and simple. I installed the same tools that I had on OSX, and they all worked.

Did you catch that? I installed… how you might ask? The wireless refused to work under OSX, it claimed that my wireless at home was more foreign than that alien network that Jeff Goldblum hacked in Independence day. Windows 7 seems to think it is fine. The hardware is quite obviously fine. I do a quick test. Reboot to OSX. No network. Stupid Mac. Reboot to Windows. Works.

If I were on the TV commercial where the lady is going to OSX from XP, I would tell her to run to the store and get Windows 7. She will be much happier in the end. If those were her only choices, I would leave it there, but there is another choice. I am a supporter of Open Source. While Windows 7 has a pleasing look and feel, and is better than OSX, it is still… windows. It has a lot of the issues of it's predecessors and a few new problems of it own. The only real choice at this point is which Linux distribution should you use. Ubuntu.. ( I really don't want to hear from you BSD guys… really. )

Karmic Koala is out. The day it became available, my torrent client was humming. ( ktorrent )

I bypassed all the dual boot, how to's, and stuck the install disk into my MacBook Pro, and told it to take over the whole disk. Guess what? IT JUST WORKED!!! Hahahahahahaha…

Ok, one confession. The hardware version of the MacBook Pro that I have (5,2) has an issue with the sound driver that Karmic installed. I have it fixed now, by installing the latest alsa driver. Yes, it took some time and research ( 2 hours ) and I know, you Grandma would never do that. I would never suggest to your Gran that she go pay the Apple tax for the hardware, and then put Linux on it. I leave that to geeks like me. I would tell your Granny to buy a Dell, or HP and install linux on that. She will be happy, and it will all work.

I now have Ubuntu 9.10 running on my MacBook Pro. Gnome-desktop, kubuntu-destop, xubuntu-desktop are all installed. I like desktop options, but prefer KDE 4. I can switch between apps, terminals, connect to the network and print. I have not seen one spinning beach ball. I am much more productive. I am so happy to have Amorok back to manage my music, and KDE to manage my desktop, and konsole as a terminal application, and, and, and… I am just so much happier.

The summary. 9 months on OSX were not wasted, but they were not as productive. If I was starting the “switch” experiment today, I would try Windows 7 for 9 months rather than OSX.

Would I buy another Mac for myself, just for the hardware? No. While the trackpad is cool, other companies have caught up on the piece of hardware. The keyboard may be enough to make me come back to the hardware, but I doubt it.

I did buy a Mac ( iMac ) for my wife, and she loves it. But, I think I do as much systems administration task with her on Mac as I did when she was on Linux. My kids still use Linux at home, and Mac at school .

Will I try OSX again? Maybe. Never say never. But, they will have to make some big changes, or, release a cool Mac Tablet. :-)

Final Thoughts.

Linux is a better operating system.

KDE 4 is the best looking window management system.

Linux makes me happy.

I know everyone's been saying it: The economic downturn will drive more people to open source. Because OpenLogic sells support on 500 projects as well as open source governance services and solutions, we get a very broad view of enterprise use of open source. After analyzing our Q3 and 2009 results, I've seen the data, and I'm here to tell you that open source is looking good.

Our press release hits some of the highlights, but I wanted to share some more details here.

Companies are choosing to pay for open source support

Our business has been growing strongly since initial funding, but the current economic downturn has caused an inflection point. In Q3 we've blown away our previous highs for number of new customers and number of transactions. In the first 3 quarters of 2009, we've seen growth in revenue from new customers up over 60% from 2008.

This growth shows that not only are more people using open source, but more people are choosing to pay for open source support or governance solutions. We tend to gain customers as open source usage becomes more accepted, broad and pervasive in an organization. Some have said that companies may choose to self-support open source as they become more familiar with it, but we've seen the opposite in our business. Our results indicate that more and more companies are interested in stepping up to pay for support when it's at the right price and delivered in the right way.

Many more people are proactively looking for open source support & governance

We generate our new customers through a combination of inbound leads (pay per click, organic search), and outbound marketing (webinars, telemarketing). The number of inbound leads is always an interesting number, since it represents prospects that come to us of their own volition and is a good indicator of how many people are looking to buy open source support & governance.

The number of inbound leads has been steadily growing, but starting in Jan 2009 we saw a jump and starting in Jun 2009 we saw an even larger increase. We are now getting 77% of our new customers from inbound leads — up significantly in both numbers and percentages from a year ago. This indicates that more companies are proactively looking for solutions unprompted by our outbound marketing efforts.

Open source is spreading beyond early-adopter industries

We've always had a lot of strength in early adopter industries — financial services and technology being the top two. In 2009, we've seen a striking increase in the breadth of industries in our customer base. We are seeing strong growth in a variety of industries, including some (retail, healthcare, manufacturing, transportation, energy) that are not always known for being on the bleeding edge. This indicates that open source usage is spreading in industries that don't operate on the leading edge of technology.

The data from our results is reinforcing the idea that open source has grown as the economy has struggled — it's use is spreading to new industries and spreading within organizations. Even more importantly for open source vendors, we have not seen a flight toward self-support, but rather an increased willingness to pay for commercial support of open source.

Join the conversation and let us know what you've been seeing in your open source business.

A recent survey we did of enterprises using open source, showed that they are not big fans of the open-core business model.  Recent blogs by Matthew Aslett, Jay Lyman, John Mark Walker center around this issue of the future of the open core business model.

At OpenLogic, we are a VC-backed company that has developed a business using a "services-based" model around open source.  Our definition of services-based matches with Matthew Aslett's.

By “services” we are not simply referring to support services, training, implementation services and consulting. The term also includes software delivered as a service, and features delivered as a managed service – such as via Red Hat Network. It includes anything you can think of, in fact, that can be considered a service, rather than a product.

I wanted to share with you a few of the lessons we've learned as we've developed this services-based model in the hopes that it may help others in that are considering a services model for their open source businesses.

1. Expand your picture of "product"

In the old, proprietary software world, your product was a piece of software. In the world of "open-core", most vendors just split the software into two pieces — the free open source part and the proprietary part.  They then sell the proprietary part just like any proprietary software.  That may be comfortable, but it can also force you to act just like a proprietary software vendor so that you can control and own the IP.

If you consider a model where the software is completely open source, you need to look beyond the software to monetize your business.  If you expand your view to the "whole product", you now have a variety of other options that customers value that you can use to monetize your business  (channels, add ons, partnerships, services, etc). At OpenLogic, we've built our business around several of these "whole product" elements:

• Certified library of open source software
• Notification and updates on open source changes
• Indemnification on open source software
• SLA Support on 500 projects
• Consulting services
• Training
• SaaS Open Source Governance platform

Our value is in being a one-stop shop with expertise across many open source projects.

Other companies have also figured out ways to monetize other "whole product" elements:

• Certification of open source with other products (RedHat, SLES)
• Hosting of open source software (SugarCRM)
• Add-on management tools (SpringSource, MuleSource)
• Commercial licenses (MySQL)
• Backport of patches (RedHat)

When you consider your business model — look broadly at your whole product to find the best way to generate revenue.

2. Learn to live without lock-in

At OpenLogic, we offer support on hundreds of open source projects — some of which have competing support vendors.  At any given point, a customer may decide that one of those vendors offers a better support offering.  When the contract comes up for renewal, if we haven't delivered value or provided outstanding support, we likely won't get a renewal.

Instead of fearing this, we embrace it.  It means that we need to stay focused every day on delivering value, offering competitive pricing, solving customer issues quickly and accurately and ensuring we meet customer needs. 

Instead of agonizing over the fact that customers could switch, we just get on with it.  Lots of other businesses across many industries are in that same situation.  If they can build successful businesses, so can we.

3. Build your business so you can price for value

Open source is typically priced lower than competing proprietary products.  However, when you build a business around completely open source software (not open-core), you likely will have vendors who compete with you on  support, services and training for the product. When you are operating in a competitive landscape, you better make sure your pricing is competitive.

To do that, you need to examine all of the costs associated with traditional, proprietary software and determine how you can lower the costs of your business.  Open community development models (as opposed to a vendor-controlled community) can save on development costs.  Open source can also reduce sales and marketing costs.  However, you need to go beyond these obvious areas to find other ways to operate differently.

At OpenLogic, we developed a unique federated support model that aligns our costs to actual customer issues.  We also have developed lead generation and sales processes that are much lower cost than expensive enterprise sales processes.  The specifics of your business will vary, but there are many opportunities to structure your business in a way that you spend less and can price for value.

4. Re-think your misconceptions about margins

Many people from the proprietary software world, including VCs, have the misconception that "services" businesses have lower margins.  The misconception comes from equating "services" with "professional services".  Once you realize that a "services" business goes above and beyond traditional professional services, the picture on margin changes drastically.

Margins on support business are very good.  Look at RedHat's margin (over 80%) as an example of this.  If you look at proprietary vendors like Oracle, their business is built around making money from their support and maintenance offerings.  

Once you let go of the idea that services always means lower margins, you'll open up many more opportunities for your business model.

I recently wrote a blog post about what what happened when Projity (backers of OpenProj) got acquired by Serena Software.

After months of trying to get attention from the OpenProj community about some missing source code (including forum posts, emails, calls to Serena) I finally resorted to public embarassment in hopes of getting a result.  This is definitely not my preferred means of getting a response, but we had a customer issue that we needed the source code for.  I blogged about it and also twittered (with an @serenasoft) in a last ditch effort to get a response.

The good news is, it worked.  The very next day, the missing source code was posted and our Expert Community member has created a patch that we are testing for the customer.

As I step back and look at this incident, I see a couple of positives and a couple of interesting things to think about.

Positives:

•  Because OpenProj was open source meant that we could resolve an issue for the customer, even when it wasn't a high priority for the OpenProj committers.
• We were able to attempt to contact the committers (even though we didn't get a response).
• Twitter in combination with a blog provided us a way to escalate the issue when we didn't get a response through traditional channels.

Thoughts:

• It's still not clear to me if Serena understands fully the implications of "owning" an open source project.  It's not just about adding code, but also about fostering the community.  I think this could be an issue for other proprietary companies that buy open source vendors as well.
• This also highlights some of the problems with a "vendor controlled community".  When the vendor is no longer focused on the open source project, it may mean that project languishes.
• By opening and developing the OpenProj community, they could build support for OpenProj and those benefits could help their "for pay business".

Although the OpenProj team has now made the missing source code available and continues to add patches,  I'm interested to see if they start participating more actively in the mailing lists and forums.  If the community as continues to languish, we will have to reconsider whether it belongs on our list of certified open source packages.

Update 10/5/09: The day after I wrote this blog and twittered it, the OpenProj committers provided the missing source code.

There has been lots of discussion about what will happen to MySQL once it is acquired by Oracle.  In a generic sense, the question really comes down to this:

What happens to an open source project, when the open source company that acquires it is bought by a proprietary software company.

I thought I would share an example, OpenProj, where an acquisition by Serena Software, a proprietary software company, has not boded well for the open source project.

OpenProj is an open source project management tool that was originally backed by a company called Projity.  Projity offered OpenProj under an open source license, and then sold an "On Demand" hosted version for a subscription fee.

About a year ago, Projity was bought by Serena Software.  Serena said that they would continue to offer OpenProj under an open source license, but would roll the On Demand functionality into another proprietary product — Serena Mariner.

So far so good.

However the committers on OpenProj seem to all be employees of Serena.  Although they continue to add patches to OpenProj, they no longer respond to any questions or issues on the forums or mailing lists.  They have posted nothing to the developer list in the last year. 

We recently were helping a customer to resolve an issue in OpenProj.  To change the code, we needed a particular file.  Unfortunately, the source code for that particular file was not available on the project site.  Only the binary for that file was available.  Source code for other files was available, but this one was missing.  We were apparently not the first ones to notice this, because someone had already posted a question to the mailing list with no response.  Our posts to find the missing source file as well as many attempts to reach out to project committers have been unsuccessful to date.

We're assuming that the lack of source code for this particular file was an oversight.  And, I'm guessing that the project committers are too busy on their Serena work to pay attention to the mailing lists.  However, by not responding to inquiries on this issue or resolving, OpenProj as it stands right now is not fully open source — since it doesn't meet the basic test of making source code available.  We're still working to try and get a response from the OpenProj committers (if anyone can help with this, let us know).

This issue raises a larger question though for open source users — what will happen to other open source projects when the sole company that backs them is bought by a proprietary company whose interests lie elsewhere?  This risk is especially high with projects that have a "closed" list of committers that work for a single vendor backing the project.  I'd be interested in hearing about other examples of similar acquisitions and what happened to the open source project.

We've had some people asking about the sample for our recent survey that asked users about open source business models and license models.  So here's some data on our sample and the respondents.

We sent the survey to about 10,000 people in our database. Some of these are customers, but most are not.  These represent companies in a variety of industries that may use open source at varying levels. We also posted the link on Twitter, but less than 10% of the response came from Twitter.

We asked respondents for their company size, industry and job function.

Company size 

• 66 % of respondents were from companies over 200 employees
• 33% of respondents were from companies under 200 employees.

Industry

Respondents came from a wide range of industries, but here are the top 6 industries.

• 25% Technology
• 10% Telecommunications
• 9%   Banking/Finance
• 8%   Consulting
• 6%   Government
• 5%   Aerospace & Defense

Job function

Respondents tend to be technical.  Here are the top job functions of respondents.

• 13% Developers
• 12% CIO/CTO
• 12% Architects
• 9%   Technical Lead
• 9%   Legal/Compliance
• 8%   IT/Development Manager

Overall we got a good sampling of different job functions and industries.  Check out the press release with survey results.

The “best” open source business model is a topic that has generated lots of discussion.   Unfortunately a lot of the generally accepted conclusions on the “best” business models aren’t in sync with what customers prefer.

In many cases, venture-backed commercial open source companies are gravitating towards open-core models where the core code is available as a community edition under an open source license and the “non-core” items are made available through a subscription to an enterprise edition.  In addition, many COSS companies own the copyrights on all of the code, employ most or all of the committers, and contribute almost all of the code – essentially creating a “company-owned” community. 

However, companies that use open source aren’t thrilled with these business practices and models.  In a recent survey that we conducted, respondents told us that they are least likely to use open source is that backed by a single vendor and their least favorite business model is “open core”.  These survey results align with what we hear from our customers at OpenLogic as we work with them to select open source projects offered under a variety of business models.

Projects that are backed by a single vendor with an open core model start to look a whole lot like proprietary software companies.  Customers feel like they are being locked-in just as they are with proprietary software.  There often isn’t a competitive market for commercial support and they must buy the proprietary enterprise edition to get critical features.

The question then becomes, why would COSS companies gravitate to these business models and practices that customers don’t like?  The answer is that vendors often believe that pure support models or dual license models aren’t viable as a way to build a business.  COSS companies fear that giving up the proprietary code and closed communities by which they create lock-in means that customers can just walk away – or go elsewhere for support.

And they are right.  With pure support models or dual license models, customers can go elsewhere.  If you don’t deliver a valuable service at a good price, the customer can easily switch to another vendor.  However, the solution to this isn’t to revert to the familiar practices of proprietary software companies.  Rather, COSS companies need to think about new ways of doing business.   In industries where there is no opportunity for lock-in, value and service are the levers that businesses use to attract, grow and retain customers.  The COSS vendors who can leverage those models will be the most successful.

COSS vendors need to find ways to develop successful, profitable business models without the security blanket of locking customers in with proprietary technologies.  At OpenLogic, we’ve developed a business model with that in mind.  I’ll blog about the lessons that we have learned in a future blog post.

Recently I’ve seen a lot of references to Gartner’s report  “Predicts 2009: The Evolving Open-Source Software Model” which includes this key finding:

“By 2012, at least 50% of direct commercial revenue attributed to open-source products or services will come from projects under a single vendor's patronage.”

I’m not buying it.

As of right now, the vast majority of open source revenue comes from Linux, which is not under a single vendor’s patronage.  Even with the growth of commercial open source projects that are under a single vendor’s patronage, much of the most used open source (think: most Apache projects) is not.  Many companies, from systems integrators to support providers like OpenLogic, will derive open source revenue from support and services around those “community projects".

I agree with Gartner that the number of new open source projects that are backed by a single vendor is growing, but I think we are a lot more than 3 years away from the point where those projects will represent 50% of all open source revenue.

With news of the SpringSource acquisition by VMWare still reverberating around the blogosphere and twittersphere, many in the open source world are wondering whether VMWare will now be another large open source company.“Being an open source company” is partly about technology (providing products under open source licenses)  and contributing to the open source community.  However, more importantly, being an open source company also means a certain way of doing business.  These open source business practices typically include some of the following:

• Providing an order of magnitude value of advantage over proprietary software
• Selling under a subscription model
• Open communication with users and communities on product roadmaps, bugs, and other business practices
• Avoiding practices that lock customers in to certain technologies

I believe VMWare and SpringSource when they say will continue to contribute to the open source licensed projects, because it will be in their best business interest to keep millions of developers using Spring.

I’m a little more skeptical that they will embrace some or all of the business practices of open source.  It can be very difficult for large companies to make those changes – for both philosophical and financial reasons.  Although the current intent may be to continue some of those open source practices in the “SpringSource division”, over time the demands, complexities and politics of the larger company may start to erode those practices if they remain distinct from the business practices of VMWare as a whole.

I’ll be watching the outcome with interest and hoping that VMWare can take on some of these open source business practices and become an open source company.

We've had a couple customers recently ask us how to synch the timezones for Apache web server and JBoss Application Server.  

The question goes something like this:  

I have servers living in Arizona. Our Linux team has set the native time to AZ. I need to set the apache and JBoss to CT for testing. How can this be done? 

This question has two answers: 

1. Apache uses the operating systems TZ variable to set the timestamp in the log files. Unless you are using any cgi scripts like php or perl on the server you can't change the Apaches TZ. If you have php you would change the TZ in php.ini and perl in the perl.conf but if Apache is just handling static files or it is a mod_jk/proxy server you can't change the apaches TZ unless you change the servers TZ. 

2. JBoss TZ is different. In your JBoss startup script make sure you xport the TZ variable like so: 

export TZ='CST' 

If you want to do this for testing purposes you can just execute the export before you start JBoss.