sun

Sep 23 2009

"Idle"

For those who wonder why my blogging is so low these days (apart from today) .. I`m actually writing more Lines of Code than Blog Entries the last couple of weeks:)

And when I`m not writing code I`m reading :) Either proofreading an upcoming book on Zabbix or reading some of the other books Packt sent me.

Next to that I`m busy preparing my T-Dose presentation

Oh and did I mention a 40 something questions questionnaire about some merger ?

Apr 06 2009

Dear IBM

When you eventually will buy Sun ..

Oh nooos.. I started this post last week and now it al seems in vain :(

Steven has some clues on what could have happened, I think he is right on the spot on with his Solaris prediction ..

He wonders why IBM would spend even another dime on Solaris, actually even today I can't even see why Sun is spending any more money on developing Solaris. But even with no acquisition his prediction of the future of Open Solaris imvho is spot on:

OpenSolaris will likely live on as a purely community-based operating system. After failing to gain any real traction against Linux, I expect it to become like the BSD operating systems: useful in niches and with a strong, core group of developers, but never to become a major operating system power.

As for Sparc, well I told it before.. and given the Siemens- Fujitsu split, given that Fujitsu has the money (which is where I have no clue) and given 2 Sparc companies with completing markets , both geographically as on hardware and software level.. merging Fujitsu and Sun would make sense ...

Looking around me .. I think Netbeans has already been Eclipsed ages ago .. I once used to work with NetBeans, but today I don't know a lot of people who still use it.

As for MySQL, Jeremey has some good insights.. the fact that different prominent MySQL folks have left Sun will only push the MySQL development model towards more openness.
And towards an even more Redder RedHat alike model, we already have the first CentOS alike rebuilds of MySQL , so a distribution model based on the same kernel with different feature sets or focus indeed might be the future.

Steven has a nice follow up on what can happen with Sun now. But the obvious problem would have been be the culture clash , at least for the MySQL folks.. , I can hardly imagine al that nice code being written with no Liquor :)

Mar 08 2009

Conspiracy Theory

<conspiracy mode>
Claudio , Isn't it obvious, Sun doesn't want you to use Linux, they will do everything in their power to prevent that , such as slowing down releases of software for our preferred platform, so that you might even start to consider choosing for Slowaris
</conspiracy mode>

Feb 11 2009

Open Source does not mean Customization Heaven..

Unless you are doing it wrong.

And sadly I`m seeing more and more people doing it wrong.
To a lot of people Open Source means that they have a piece of software that does almost what they want and which they can modify to their best wishes and use internally.

So they fork locally,, they don't redistribute their code , but they aren't contributing their changes back upstream, chances are these changes wouldn't be accepted upstream anyhow as they are really customizing the code for their specific cases. At first sight this doesn't look so bad , at second sight ..

When weeks or months later the upstream project releases an urgent security fix, the local fork has deviated soo much that it can't upgrade anymore and stays with an insecure version.
Often it's worse.. a feature that could have been accepted upstream has been implemented slightly different in the local fork, the result being that newer features depending on the first one also can't be integrated anymore

Some projects are prepared for local contributions, they have a modular framework that allows you to build on top of the project while not having to touch the core of a project, Drupal and openQRM are great examples of those, but not all projects are that smart. Needless to say that when you have such a modular framework you really shouldn't be modifying the core part of the platform, unless you are fixing a real bug.

But the general rule of thumb is that when you fix bugs, make sure they are inserted upstream , or implement new features.

Now sometimes there is no easy way to get your code accepted upstream, in which case you should announce clearly that you want to contribute but you are blocked and publish the patches somewhere else ...

Don't let the community work for you, but work with the community !

Dec 06 2008

The Eclipse of Sun

If you've been reading this blog for a while you'll know that
for the past decade I've had a love-hate relation ship with Sun.

Sun has done a lot of good things in their open source journey such as MySQL, openOffice , Virtualbox and opensourcing Java. But on the other hand they had troubles with creating really organic opensource.

I've always wondered why a company that bought StarDivision because it was cheaper than buying the MS Office license keeps wasting money on building it's own operating systems, albeit in a pretty open model, but with zero to no relevant community.

Yes I've ranted on their marketing boys and girls when they polluted forums I liked. But no I don't want this to happen. (Slicing up Sun)

However I`m in fear it actually might happen, the funny thing is that I already mentioned the same idea in offline conversations during the last couple of months.

My Advice to Sun. : Stop putting money in things you can co-create with other organisations, if there's only 2 features in your product that count for some people, contribute those 2 features to something bigger.
(That's D-Trace and ZFS and the Linux Kernel I`m talking about in case you didn't realise) Why keep throwing money down the drain ?

Also let Google, Percona and others contribute to MySQL, don't keep it as closed as it is today. As after al it's more Free software than it is Open Source, but it has a great community which I love to be part of .. and I hope for a long time to come..

I`m going to try to keep my mouth shut on this for a while.. as I think Jonathan is listening anyhow. If he was, he would have known that at some point in time when you step out of the shower and there is too much hair dropping from your skull every morning, it's time to cut off the ponytail.. , not opensource it. I did that years ago.. and it's growing much thicker again now.

My hair that is ..

Oct 31 2008

How Sun Will be rescued

I probably ranted a bit too much on the marketing push that Sun has been trying to make into the Open Source community.
The economical situation isn't really perfect so Sun does deserve some credit too.

Yesterday Techcrunch published an exclusive interview with Jonathan Schwartz on the future of Sun and how Sun will be rescued .

[YouTube Movie Embedded]

More details are here

Oct 28 2008

Virtualizing MySQL , are you stupid ?

or timebound ? or don't you have any load on your DB at all ?

I personally don't see many reasons to virtualize your database, apart from the , we plan to start small and scale out, or the we need it now and we don't have the hardware yet , putting your database on a virtual platform where you have to share resources with other virtual machines doesn't really sound like a tempting proposition to me. Small, almost idle databases , maybe. But enterprise production level databases no thnx.

Sheeri Cabral also mentions the above reasons .. and there also .. Enterprise Production use isn't listed.

Databases typically require a good amount of memory , and steady disk access.
So if you are in a production environment with a fairly loaded database, would you want a 4Gb machine with full direct memory access, Or 3.5Gb of virtual memory that can be ballooned to 3 if underused. My pick is at the 4Gb real memory.

The original article at Sun argues the use of Virtual Harddisk to move around workloads between different servers or even Virtualization platforms. But it fails to describe the guaranteed performance penalty of not using raw disks but a filesystem on top of a loopback device. How many layers do you want before actually write to the disks. Good practice in a virtual environment is to dedicate full disks or LVM parts to the virtual machine hence lowering the overhead, but most (default) setups do the opposite.

And don't get me started about the myth of using virtualization for high-availability :)

Now can somebody please remove all the clueless marketing people from planetmysql.org , thnx. (they can be identified with by a blogs.sun.com source and posts that mainly talk about Sun products including only a slight hint to MySQL)

(PS. What's a Market Development Engineer's job description anyhow ? , that's just a different name for Marketing Assistant right ?)

Oct 19 2008

Why did sun really buy MySQL ?

To save Solaris from a certain death ?

Reading Planet MySQL the last couple of hours I'm trying really hard to convince myselve the Solaris offensive there is not orchestrated.. but I can't.
It might ofcourse be the fresh MySQL users that Sun brought in on their platform that started out blogging but hey .. I`m paranoia right :)

Are they really trying to get at least a fraction of the MySQL community on Solaris. Do they really think they can ? Yes they lost a zillion of Solaris customers that were running a proprietary database to MySQL on Linux users ,, but why would they want to move back to a semi proprietary setup ?

According to Linuxjournal Alan Cox seems to think that ZFS is the only thing that is keeping Solaris alive. I don't think DTrace was a bigg mass tool that would convince the crowds to suddenly move to an other operating system.

So is Sun trying to Lock In a community ? Other people would call it a Jail, altough I wouldn't consider this particular type of jail a Luxury one :)

Why can't Sun just drop the whole idea of building its own OS and contribute more , they are slowly learning in some other fields , but in the Operating System field they still haven't realised they should up the fight ... but then again .. I overheard someone say recently "The best fights to watch, are the ones that can't be won anymore .."

So just remember .. the L in LAMP still stands for Linux,

Mar 16 2008

Helping Sun to figure out what it wants to do when it grows up

I have to admit I`m lagging a bit on my Linux Journal reading.
So just now I read Maddog's article titled Navigating by the Sun

Bull's Eye .. I loved reading every second of it as it is so true ... I told you folks earlier that we'd love to help, but it really is time for Sun to figure out what it wants to be when it grows up :)

It's fear it's either that or down the drain with the other bunch of companies that are on the road to obsoletion.

Feb 25 2008

Teaching Sun the Open Source Dance

Over the past couple of days Sun has been getting a lot of feedback on it's behaviour with open source.

So there is Amanda McPherson trying to teach Sun that the L in LAMP really stands for Linux.

And then there was Roy T. Fielding quiting the Open Solaris community.
I'm still wondering why a company that once bought StarDivision because it was cheaper to buy the company than to pay licenses for similar functionality, keeps maintining their own kernel stack rather than contributing to one that is way more popular and as a much larger userbase.
Its not like they have a die hard community they will loose, it's not like they will loose customers over it. When Sun says that Linux is the new Solaris their customers will just follow.

Personally I stopped working with Solaris ages ago... when we ocasionally run into a customer that wants us to deploy things on Solaris we always have to spend extra time GNUifying the box, which is yet another pain.

Sun had to learn the hard way from the JAVA crowd that they do care about Licensing and a community only starts to build when they like what they see. and it's exactly that community that Solaris is still lacking.

Virtualbox also is in the same boat, they have a good user community, but they don't have a lot of contributers as they require contributors so use the MIT license and even sign some papers.

In a way MySQL used to be the same , altough lots changed during the last couple of years , but back a couple of years ago nobody outside of MySQL was contributing code, there was a gigantic user community, but not really a developer community.

The big difference here is in community.. not customer base, these people are actually using MySQL because they are freely choosing so. Not because their boss or corporate policy tells them to.
But MySQL learned, and is changing, it currently has also non employees contributing .. often ex employees but also other people , people that form a real community.

Today .. if you really want to cash out ... create an product open source it ,create a user community around it but don't allow contributors, my bet is Sun will buy you :)

I told it before.. I really really hope one day Sun will understand .. but from the past couple of acquisitions.. they seem to be taking the same path over and over again.