Our employee and Mayflower Fellow Thorsten Rinne develops and maintains in his sparse free time a popular FAQ management system called phpMyFAQ. Its current release is V1.6 (see press coverage on golem.de) and phpMyFAQ is licensed under MPL. Popular users of phpMyFAQ are: Stanford University, Apple, the German telecommunication company Arcor, some big E-Commerce company, Knorr Bremse AG and others.

The CVS source tree is hosted at our dev platform thinkforge.org which I mentioned in another post.

phpMyFAQ is available in 30 languages, including Chinese, …

At this week's Java One conference, newly appointed Sun CEO Jonathan Schwartz has pledged to open source Java.  This has long been a bugaboo in the open source community and it caused many to question Sun's commitment to open source.  While there have been many reasons Sun has given in the past for not wanting or needing to open source Java, such as risks of incompatibility between forked versions, these concerns have always sounded a bit overstated.

Rich Green, who has rejoined Sun as the head of software, will take responsibility for figuring out the details of how and when Sun will make it happen.  It took Sun many years of internal battles to open source Solaris, but they did it and it's now getting broader adoption than before.  You can argue whether Sun should have done these moves earlier, but lets give them …

mysqlsla v1.2 is finally done. mysqlsla is a statement log analyzer that can read and combine MySQL general and slow logs, and "raw logs." The major update with v1.2 is that it could now replace mysqldumpslow: it does nearly everything mysqldumpslow does and a lot of things mysqldumpslow doesn't. There's even an option (--mysqldumpslow or --mds) to format the results like mysqldumpslow (for nostalgia). And not that mysqldumpslow was too difficult to figure out, but mysqlsla is at least well documented. Also new with 1.2: statement filtering, statement grepping, a --safe option, analysis hiding, and re-written log parsing functions. Please report any bugs/problems.

Most web applications use something like five languages. One of these is a big programming language, like Java or PHP, running on a server, and the other four are HTML, CSS, Javascript, and SQL.

SQL and HTML are "declarative": they let you state what you want, and the browser (for HTML) or database (for SQL) has to decide how to cook it up for you. This makes them easy languages for people to grasp; it also ensures that the browser and database server will be exceptionally large and complex pieces of software. (And apparently programmers are never really satisfied with declarative languages, so database servers grew stored procedures and browsers got Javascript.) CSS is a "little language," a vocabulary for design, more lexicon than grammar. Over the last ten years, a lot of presentation code has moved out of HTML into CSS, while today's HTML is full of DOM signposts ("id" attributes and "div" tags) that didn't used to be there. …

Hey, look! Peter mentioned me in his presentation at the UC this year.

UC2006-MySQL-Performance-Landscape.pdf

I let him use the Sunfire T2000 I borrowed from Sun (which I should return today) to generate some statistics for the talk.

© cjcollier for C.J.'s WordPress of studlyness, 2006. | Permalink | No comment

Add to del.icio.us

Search blogs linking this post with …

dave rosenberg has been doing a series of ?how i work? interviews and asked for more submissions. here is mine.

what is your role? i believe my title is still maintenance engineer, but i?m now actually a proper server developer at mysql. right now i?m doing some falcon-related work, but i hope to get back to working on pluggable authentication and authorization soon.

what is your computer setup? my desktop is a mac mini (powerpc), hooked up to a 20" apple cinema display. my development box, which runs headless and i just access with ssh, is an amd64 running ubuntu. i also have a 12" powerbook that i …

I figure I might as well maintain my status as Resident Inquisitor of Open Source Myths with a discussion on the value of choice. A friend at a Fortune 500 company recently set me to thinking on the problems (and opportunities) that open source affords vis-a-vis choice. (I've opined on open source choice before, in case you're interested.)

I'm very fond of telling enterprises that open source maximizes their choice. I often use one of Larry's graphics to illustrate how much better off they are:

Look at all that choice the CIO now has! She can spend her money in a variety of different ways.

Oddly enough, that can be a problem. In many ways, it's easier to be forced into a decision: if I only have $10 to spend, in some ways I'm glad to have $9.95 in Arsenal tickets staring at me. My choice is made. No need to worry …

Edit: apparently as I was writing this, Dave put out the call for others to write their own. So, I *have* been asked….

I find Dave Rosenberg’s “How I Work” series fascinating, so I thought I would post how I work, and some tips I’ve picked up along the way.

I enjoyed How Brian Aker Works the best, mostly because some of the ideas were new and fresh to me — for example, polling e-mail every 30 minutes (and thinking about moving to once every hour).

Now, most people I know would say “But I MUST respond to e-mail, the faster the better!” To that I say, “What if you were in a meeting?” Most people will call if they want an immediate answer, and if you’re truly in a meeting, they’ll leave a voicemail …