I have so many things to write about, but not the time, so I am combining my past week into a single post. Hopefully, everyone finds something beneficial in here.
First of all, my flight to Austin was indeed canceled on Thursday. Luckily, I was smart enough to have a backup plan. I booked a flight to Austin via Southwest Airlines late Wednesday night. This was my first flight on Southwest. I always avoided it because I heard people bash it so much. The reality for was totally different. Their new seating assignment process is very cool. I was the 6th one on the plane and got my exit row aisle seat. Even my buddy who got on much later in the process got his coveted window seat. The flight bounced through Nashville on its way to Austin. I have to tell you, they load a plane faster than USAirways. Way faster. And the luggage comes out quickly as well. All in all, I have to say that I am now a fan of Southwest Airlines and will make that my new first choice for flying.
This was my first trip to Austin and it did not completely disappoint. However, it seems to me that all this town does is drink and listen to live music. I got to tour the capital building and see some of the sites while I was there. Unfortunately, work called, so I spent most of Friday working and missed out on seeing my buddy's house and his rental properties.
I also learned that just about everyone who goes to Austin gets allergies because of the cedar there. They call it the Austin allergy or the cedar sickness. Cute, huh? But, what a pain in the ass. I was loaded up on Sudafed or allergy medicine the whole weekend and went through a box of tissues.
On to Denver
By Sunday morning, I was back on the clock full-time, flying to Denver for Collaborate 2008. The weather on Monday and Tuesday was fantastic. It was 80 degrees both days. I was shocked. But, reality crept back in Wednesday and by lunch time it was snowing again. The Denver air cleared my allergies from Austin but left me so dry that I felt like a walking lizard. Even the blue bear wanted to come inside.
This was the third year that EnterpriseDB went to Collaborate and the first time we did it right. There were 7500 people at this show and we had a 20x20 booth. Granted, the booth was in the back, but we nailed it. The magician got their attention and we wowed with a laundry list of customers, awards , demos and free books (autographed by Lewis Cunningham).
All in all, we brought home over 400 leads and gave away 200 books. These books are great viral marketing tools. Every book will go back to an office and sit on a desk or bookshelf. Every time someone sees it, they will ask about us or, better yet, grab the book and read it.
We will not miss this show again!
MySQL Goes Closed Source... Thanks for nuthin, Sun
Wow, I get on a plane to come home yesterday and I land in Chicago (layover) and my cell phone goes ballistic. Sun just closed MySQL's source code. I couldn't believe it, either. So, I had to dig a little deeper.
First, this was, I believe, the plan for MySQL all along, so don't blame Sun. This started when MySQL split between a Community Version and an Enterprise Edition. That was over a year ago in my book. Second, MySQL is NOT closed source.
What MySQL is doing is becoming a lot more like EnterpriseDB, actually. Its the hybrid model that actually allows open source businesses to make money. Though you can succeed with a product that is completely open source, you are limited to support and services dollars only and only from those who need it. The potential revenue in that model is modest and does not favor long term success or fast innovation. But, by keeping some of the product closed source, like MySQL's online backup module, or EnterpriseDB's Oracle Compatibility, you create a way to generate revenue from the software itself. This allows the company to grow faster, to add more to the product more quickly, etc. And, eventually, this stuff will more than likely make to open source sooner or later.
Of course, what I find funny about this whole thing is the module itself. MySQL says that Online backups are so cool and important that it is closed source and available for enterprises only. It just goes to show you how immature and lightweight MySQL really is. Online backup is a staple of any REAL database and has been a part of Postgres for years.
I can just see MySQL's next "hot" (and obviously closed-source) module now: data integrity. LOL