22 Jun 2011 vicious   » (Master)

Update fever

Yaikes, Firefox 5 is out and Firefox 4 is EOL. Each time I used Chrome (I had to use chrome to access the webct gradebook at UCSD) it had a different version number. I can’t quite tell the difference between browsing 3 years ago and browsing now, except that Chrome still doesn’t do flash on 64 bits, and in firefox it is by running the 32 bit version of flash in the wrapper.

Whatever people are somking, I want some!

At the same time my laptop (lenovo, not too satisfied anymore, not sure if I will buy one again) turns off about once a week, possibly overheating, but its hard to tell.

Hell I want just something that works! Why do people keep adding new features that break old features, so that no matter which version of software or hardware you use you always end up with something broken.

I don’t care for the fastest hardware, I mean it really isn’t any faster that I can tell anyway than it was a few years ago. But the old hardware dies and you have to buy new hardware that requires new drivers that are broken in new ways, before they get fixed, your hardware dies again.

Software seems the same way. What happened to quality engineering? It’s a known fact that writing a new feature is 5% of the work and making sure it doesn’t break everything is 95%. Now everyone wants to just skip the 95%.

The best example of good software is TeX and LaTeX. They have not changed in … decades. Yes a new version of a macro does come out every once in a while, and a distribution will break the installation once in a while for stupid reason, but the software itself is stable and mature. I can compile a document made 10 or 20 years ago without modification. I don’t have to learn anything new. It works, and it has quirks, but it has the same quirks for everybody, so they are usually well documented quirks.

Syndicated 2011-06-22 20:23:47 from The Spectre of Math

Latest blog entries     Older blog entries

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!