The Science of Web Art, Design and Development

It is not difficult to comprehend Payday loans Ownership of a bank account

View posts for » Category "Web Development"

IE6 is dead. Who should applaud?

Last week Google announced they are phasing out support of IE6. This follows the attacks to gmail accounts of Human Rights Activists originated in China, apparently consequence of a security flaw in IE.

Even before Google, the German government decided to advice against the use of IE6 and a the French government followed. The UK hasn’t joined yet bt there is a petition to discourage an discontinue the use of IE6.

Web developers consistently dislike IE6 for its many bugs, it’s lack of technology even for the date when it was launched but mostly because 9 years down the line even the best browser on earth should have long been retired. For a web developer, dealing with IE6 has been a major pain for years and it’s a source of frustration that great technology is deterred by having to support an ancient browser.

IE6 is not dead yet, but it’s terminal. Without Google support, with governments advocating against, with awareness spreading it is a matter of time, and not much of it, for IE6 to be largely abandoned.

Yay! We web developers applaud!

Now, how about the users? The user that has been using the same browser that came with their computer when it was bought. The user who has never upgraded software before and is afraid to start doing it. The user that is used to its piece of software and doesn’t want to change.

Do they have to upgrade just because some developers say so? Should they applaud too?

Ultimately, developers and users have a common objective: An open, accessible and usable web, so if we can applaud as informed developers the only thing that could prevent the user from applauding is the information itself.

IE6 has been around since 2001. If you consider that the web itself had only come to life in the early 90ies, this is as modern for web years as a car from the 50ties for the history of automobiles. For as lovely as 50ies models may be it’s hardly reasonable to argue that our streets and roads have to be build with these cars in mind.

Yes, some people still driving today learned to drive in those models and it may also be true that if roads had been build encouraging them to keep these cars, by now they’d be struggling to accept a more modern model and they’d be upset if they were now told by engineers that their cars are too big, consume to much petrol, emit too much carbon, are accident prone and overly not suitable for modern city life.

And rightly so because engineers would had failed to make the transition smooth but not necessarily because they should be entitled to drive anything they’d fancy on the streets.

A system chosen from the combinatory explosion of different browsers, different operating systems and different hardware(*) should ideally be tailored to the user’s needs and reflect their preferences on how to interact with the web and in this sense, it’s only fair that we, as developers, build a web the users can, though the technology they’ve chosen, reassemble the pieces in the way that suit them best.

In practice, many of the systems the users have are not built this way but instead are commodities and so are guided by price and availability.

It may well be that us, developers, had failed to make this transition smooth during the years. It may also be that the browser wars and Microsoft being next to a monopoly for many years had left us in a situation where not much could have been done other than support IE6 for so long.

But surely this is not to say a browser that is used by a minority of people that find challenging to update software should be artificially maintained in detriment of being able to fully use technology that may help people who are challenged in ways that are more difficult to overcome (e.g., physical and cognitive impairments).

If IE6 users mostly use that browser because it’s available to them, then is up to developers (web developers, browser developers and other developers alike) to make available for them better technology and allow them to change their game. And we should do it in the most helpful way we can but we should not feel forced to support old technology cluttering the roads for the fear of upgrading. Is the fear that must be removed, not the upgrade.

And if we are to learn something from the last decade of web and browser development, then I’d say it should be to work on educate and help users to continuously move forward to better technology rather to artificially maintain a fairy tale with chewing gum and strings.

Comments (2)

The ultimate answer to screen resolutions for web design

When I started working on the web, ten years ago, sites should be done to be visible with a resolution of 640x480px, otherwise a good part of visitors would be blocked out. As resolutions increased the minimum size increased to 800×600 and today it is believed that designing towards 1024×768 is safe.

Will this number increase in the future? Should we still concern about low resolutions? What is The ultimate answer to screen resolutions for web design?

I really don’t think the ultimate answer for screen resolutions is a number, no matter what the number is. I think the answer is a process by which websites are developed.

read full post…

Comments (11)

Non-breaking space is to join things, not to separate

Among the almost infinite list of html entities, the non-breaking space ( ) is one of the most popular but very little understood.

The correct place for a   is, for instance, in “Mr. Smith”. The   will avoid a line break between Mr. and Smith, while leaving a space between them.

The non-breaking space earned its fame because in the dark days of the table layouts people needed to put content on certain elements without visual rendering.

As the normal space is discarded by the browser in most situations an entity like the non-braking space, which is always considered and yet has no shape was very welcome to leave a gutter.

Yet, the   should not be used to leave gutters. While it is quick and easy to put them, is really a nightmare to upgrade, because markup and presentation are all mixed. The role of the non-breaking space is actually to bind things together and not so separate them.

Comments (4)

Web Standards design and how to be a Gourmet Chef

Have you seen Jamie Oliver‘s shows on the “telly”? Sure you did.

Put the flour on the table, open a hole, pour water, add yeast, oops… spilled on the floor. No problem, let’s put it away and make some more.

…for this dish, let’s put this on a big pan, while we cook that on the small one. Chop this, chop that, use your hands, wonderful!

read full post…

Comments (6)

Transcending CSS, the fine art of web design

Transcending CSS

I have just finished reading Transcending CSS by Andy Clarke, one of the best readings I had so far on Web-related matters.

The book does assume you know a good amount of CSS, not a single paragraph is spent explaining how selectors and rules work, so it is not suitable for beginners keen to wet their feet on the waters of CSS. Yet, as the most part of the book is not quite technical, it also doesn’t requires you to be a CSS wizard.

Transcending CSS, as the title properly says, is not about CSS, it is about going beyond, it is about Web Design, a term that is in everybody’s mouth, but not necessarily in a meaningful way. It is about getting to the end of the road and start paving where Web Design will follow in the future.

read full post…

Comments (3)

Internet explorer deserves graceful degradation, but nothing more

I think most good web developers know how a bad browser Internet Explorer is.

Web development has an inherent difficulty because code you write is only an outline of what you want done, an intention. Is really up to the browser what is actually going to happen.

Some browsers don’t support some features and web developers should treat this with graceful degradation. Explorer is no exception.

One of the beauties of the web is that the user is in control. Browser choice and options are there to ensure that and sites should support that.

As a web publisher one want primarily to deliver information to public, not layout. The layout is support, meant to enhance the usability of the page. Not only for eye pleasure and reinforce brand indentity.
read full post…

Comments (0)

Paulo Gazela site design by Guilherme – Content first

Paulo Gazela is a talented musician living in Campinas, Brazil. He sings, plays the harmonica and composes for several musical projects he runs, mostly on Blues.

He has a very rich experience playing with leading musicians like Brazil-wide famous Flavio Guimarães, harmonica player of Blues Etílicos and American harmonica player R.J. Mischo.

Paulo Gazela mic
Also, Paulo Gazela happens to be an old friend if mine, and I was seriously honored when he chose me to rebuild his whole site from the scratch.

read full post…

Comments (5)

Multilayered web layouts

CloudsA few weeks ago I came up with the idea of having a web page with images composed of multiple layers and the layers could move differently when the object is resized.

And here it is.

Of course we all see web 2.0 pages with a lot of resizable and draggable menus, images and all imaginable things, but I decided to do it very clean and very easy to understand, after all is just a proof of concept.
read full post…

Comments (3)