just pick up some crackers from out the box just after main door, leave on serviette on hot Macbook (near-left corner is recom ;)), leave to simmer… eat after 5.minutes!!!
a cool new way to use your new Macbook… ;)
just pick up some crackers from out the box just after main door, leave on serviette on hot Macbook (near-left corner is recom ;)), leave to simmer… eat after 5.minutes!!!
a cool new way to use your new Macbook… ;)
more (techie humour) at rubbedcode.com...
"You're the highest paid, but..."

Interesting cycle, isn't it? ;P
Edit: Oh, and btw, this has nothing to do with Spiragram, ok? ;P I just thought to inject some humour into what is ordinarily a rather "dry" and "serious" blog...
It’s been quite confusing reading all the various reports about the issue – but suffice to say that the Enterprise sources will still be available via BitKeeper! I’m just not too sure how this will work out for the Community Version, though! Seems like (and Colin Charles reads this the same way as me) the Community Version is going to take a step back where bug fixes are concerned, since according to Kaj Arnö (MySQL VP Community Relations), bug fixes are only going to be added to the Community Version of MySQL when the next version gets released (which should be like every 3 months)...
So if you’re using Community, no emergency hot fixes, and no timely bug fixes for you!!! The sources for Enterprise, though, will still continue to be available via BitKeeper (watch the linux.com video interview (although there was a point in time during the interview [05:59ff.], where it seemed like this might not be the case)). This will probably have to be the way to go if you want access to all those hot fixes and bug fixes… That is, until (and if) MySQL AB decides to close off access to that too…
But fear not?!! The GPL does allow for customers to redistribute the source code, and as luck would have it, there seem to be 2 willing providers of that service already (mirror.provenscaling.com, and dorsalsource.org)...
One persistent point raised in the Linux.com video interview bugs me though – is the Community Version (as Zack Urlocker, MySQL VP Marketing, says) not going to be any much different in terms of features from the Enterprise version? My my, but how MySQL AB’s official literature says otherwise... Or does the “experimental features” bit refer only to alpha, beta versions of MySQL Community – and not the GA versions???? Are we looking at a marketing message based off of mysql.com that is designed to push people off into buying into the Enterprise edge?
A Side Note:
Reading Mike Kruckenberg (“well-respected community member”) ’s perspectives on the issue was interesting – although I cringe at the fact that he does not yet get “it” (the stand of the FSF with regards to the meaning of the word “free”). Yes, you can sell free software, dude – the “free” in “free software” is about the liberty, not about the price!!!! The FSF has never been about the free price of the software – it has only really been about the freedom of the software…
Freedom is the issue, the whole issue, and the only issue.
(And Back from the Side Note):
So, what will this mean for Spiragram and its projects/clients? Nothing much really, I guess, above what other users of MySQL will be facing as well with this announcement. The only thing that has changed is, since we now have one PostgreSQL pusher on board (in the form of me), we may yet see more PostgreSQL deployments yet! We shall see… :)