Skip to main content

Why Firefox 3.1 can wait

The FOSS community is rejoicing another release of FF - 3.1beta. Mozilla released FF3.1beta on tuesday. I was one of those beta-ers last time around during FF3 release. I even did countdown to the release. I even got my own download certificate :). However, I don't want to eager myself to it this time. Here is why its different this time.

Firstly, its not a major release, meaning nothing changed BIG! If at all, The only thing that will get me motivated is the CTRL+Tab feature. But my existing Tab-Mix Plus plugin gives a tab list that is adequate. A 3D preview is nice to have but not so much to hurry to.

All the goodies are unused, The geocoding, Video, Audio, HTML5 and CSS3 support have nothing to offer until there are some REAL websites that start utilizing them. Especially the Geocoding, As much as it sounds cool, until it becomes a standard - it would be another browser specific dumb-a$$-nerdy feature I would refrain myself as a webmaster. The others follow the same rationale.

The much boasted JIT javascript is not enabled by default. WHAT? Why? I think 3.0 has a huge performance improvement from 2.0 that I only doubt this is going to matter for an end user. Would I like to try this out? Yeah sure! But it can wait until my Ubuntu auto updater hits the new update!

Mozilla needs to start a different approach for distributing betas. The default beta should always be an independent zip or tar file. Like one of those Portable Apps. This will make me go out there and check it out. Right out of box, No - doubt, fear or uncertainty. You know what I mean..

Finally, I was more interested in the private browsing to come. I am disappointed it dint make it in this beta. I will wait. So will the betas :)

Popular posts from this blog

Javascript: Convert Strings to Binary (and representing in a nerdy way!)

I follow those GoogleDevelopers Videos . Sometime back, in one of the presentations on GoogleIO, there was this interesting string of dots at the bottom of each page of the presentation . They looked like random big and small dots. A similar bunch of dots were also on the T-shirt of a presenter was wearing in another presentation . While it seemed something in the pattern, I could not find what it was. Finally, another presenter cleared the matter that those dots are just binary representation of "GOOGLEIO" (So much for advertizing Google IO, Impressive!). So I wanna do it. Takes me back to days of those DSP classes at school. Nerdy me had to churn some old brain cells. I remember those first programming language classes in Pascal and C when you were asked to do fibonacci series and converting a binary string to ascii codes. That *experience* came handy here: Check it out! Text to Binarize: For those who came to copy the javascript code to convert string to binary,

MySql Copying Table Structures.

Some times you need to copy only table structures across databases. This article describes two ways of doing it. If the whole database schema need to be exported, mysqldump is very effective. A --nodata flag will dump all tables' schema. Like this. mysqldump --nodata -p -u username databaseName But if you want to copy a specific table, individually, you could use "create table like" feature. You could create it even from a different database. However it must be on the same mysqld instance. Like this. create table newtable like oldtable; --Or from a table in other database create table mytable like otherdatabase.tablename;

javascript maxlength for textarea with \r\n breaks in java (esp Firefox)

Textareas allow new lines to enter. These are represented by \n (1) or \r\n (2) characters. But when you save to DB you have a limit to certain length of chars. There is no maxlength attribute in HTML that will stop you from entering data. This is generally acomplished by Javascript. You do a onkeyup hook and stop event or trim after textarea.value.length > maxlength. There are many other solutions out there.. But.. Here is the problem that most of those solutions overlook, How do you deal with the count on \n and \r\n representations. Lets first see how it matters. If the text entered has new lines, the length is calculated differently in Firefox and IE. When you enter a Text like 01234 567890 You expect the textarea.value.length to be 11. (10 chars + new line).On the backend, however, java would recieve it as 12 chars (10 chars + \r\n) (this is irrespective of FF or IE). So you are effectively saving 12 chars to DB. Worse yet, IE seems to figure textarea.value.length as 12 (