Archive for September, 2008
New Features of Adobe’s Creative Suite 4 (CS4 Webcast)
Wednesday, September 24th, 2008Tuesday morning, Adobe followed through on a webcast that was alerted via email subscribers informing previous Adobe software customers of the newest release of Adobe Creative Suite, specifically CS4. The graphic designers and front end developers at the company I currently work for got together to watch the web cast. Here is my summary:
It was a good hour of information, with probably the most intriguing aspects relating to Dreamweaver and Illustrator. I’m working strictly from memory here, but I’ll try to summarize some of the features that were mentioned.
Dreamweaver will now be including a preview window that displays web content based on the webkit rendering engine (used by Safari and Google Chrome). So, for example, AJAX-generated dynamic content can be displayed in the preview window directly inside Dreamweaver. Also, Dreamweaver will have the ability to recognize all files associated with a particular (X)HTML document, and will have links to those files in tabs next to the open (X)HTML file. CSS files, server-side include files, and external JavaScript files will all be easily accessible instantly from tab-like links. This doesn’t mean the related files are actually open — just easier to access.
Also impressive was the capability to link an Illustrator file with Flash. I can’t remember all the details on this one, but it definitely looks interesting. One of the things that was mentioned was that Illustrator and/or Flash would allow easy editing of Flash animations similar to Adobe AfterEffects. This seems like a nice step forward, however it could easily become similar to previous features inside Flash that later were one-upped by developers who found cleaner and more customizible solutions to the exact same problems that the aforementioned features were attempting to solve.
And finally, Photoshop will have a new feature that allows an image to be scaled while the image’s most important parts would not be distorted. Thus, Photoshop figures out what pixels are important, and which ones are negligible, and it scales the image from landscape to portrait without making it look distorted. A very interesting feature, but not necessarily something that would be used very often.
It was a nice preview to another powerful developer suite (soon to be?) released by Adobe. At the time of writing this entry, Adobe still seemed to be replaying the webcast here. I’ll be researching the new features in the coming weeks, and hopefully be able to use some of the new tools in the not-too-distant future.
Why IE6 is the Greatest Browser Ever Made
Monday, September 8th, 2008How would you react if I told you that I had released a piece of software on August 27, 2001 that was deemed (at the time) to be of high standards and quality by its users and reviewers, and that, although it is unstable and buggy by today’s standards, currently holds a 25% market share (2nd only to its successor)*, despite similar competitive releases by other companies?
You would probably immediately conclude that this piece of software was/is a huge success. But once I told you that I was talking about Internet Explorer Version 6, you would immediately conclude that I was out of my mind (as you already concluded when you saw the headline for this article).
But let’s be honest with ourselves. Success is not necessarily dependent on quality and feature-richness. IE6 has done exactly what Microsoft intended for it to do: Help users browse the internet with minimal supervision via a clean, easy-to-use interface.
Web developers need to face up to the fact that the average web user today wants to read, shop, and browse. And all of that can be done quite easily without Firefox, Opera, Safari, or even IE7. The overused motto “if it ain’t broke, don’t fix it” certainly applies here — and this is especially true when you factor in Microsoft’s poor history when it comes to software upgrades. People know that Microsoft has a habit of releasing unnecessarily complicated and bloated software upgrades, so why should the users bother to upgrade a perfectly functional browser?
I know what you’re thinking: It’s not perfectly functional! It’s buggy, it does not adhere to standards, it doesn’t display web pages properly… I could go on. But that is evident from the perspective of a web developer, not a novice computer user that has no clue what CSS stands for. And 98% of the time, the user is not even going to notice the bugs and incompatibility issues. Even if IE6 crashes twice a day (which is probably a very high estimate), that still would not be enough reason to upgrade if the only thing you use a browser for is reading email, facebooking, and shopping online.
And if you still don’t believe that IE6 is the greatest browser ever made, go back and read the first release of Designing With Web Standards by Jeffrey Zeldman. At the time that book was released, IE6 was viewed as the most standards-compliant browser, and Zeldman talks about it throughout the book.
I don’t like IE6 — I never use it, except to ensure cross-browser compatibility for sites I code — and I think anyone who uses it should upgrade immediately, or else switch to Firefox (any version). But my opinion means nothing to Microsoft, and it certainly means nothing to the facts of the past 7 years, in which IE6 has virtually dominated the Web Browser market despite incredible amounts of competition, and constant (often web developer-biased) criticism.
* Note: I made an error, which I’ve corrected. IE6 holds about 25%, and IE7 is at around 50%.