Skip to main content

Logos 2006

Intel, AT&T and Kodak, all three changed their logos recently. Even Hutch, provider of GSM mobile services changed its 'orange everything' to 'pink everything'.

I might have found these "swanky" new logos thoroughly disappointing but who's complaining. The corporate suppliers are surely in for some serious money now with new business cards, letter heads, and all the stuff that would have to be done sporting the new logo.

My quick thoughts:

AT&T: Everything lowercase is not always cool.




Intel: The least horrible change of all three, mixing the 'Intel Inside' and the intel original logo.




Kodak: The less said about it, the better.




What next? Which company do we have next going for a new logo, a new image? Microsoft, or Yahoo! with its all new taste for tagging? btw, which logo redesign did you like the most?


Comments

Arpit said…
this poling thing is good.
pass on its link to me as well..
10:56 PM
enginerd said…
Dude! You'll have to register at dpolls.com
11:57 AM
Post a Comment

Popular posts from this blog

Gmail Chat Disabled

The fact that it happened does not surprise me but that it took so long for our network administrators to figure it out does. And if you are wondering how do you disable Gmail's chat features on your network, you only need locking DNS lookups to chatenabled.mail.google.com , by returning 127.0.0.1 .
52 comments
Read more

Advertising Billboards as Rain Covers

Advertising billboards are put to use as Pakistani refugees, left homeless after the October 8 earthquake, set up their tents in Muzaffarabad, Pakistan. [via SFGate ] Technorati Tags: Pakistan Earthquake
1 comment
Read more

Community effort to create a single persistence model for the Java community

A community effort led by Sun Microsystems is aiming to create a single 'Plain Old Java Object' persistence model to provide a single object/relational mapping facility for Java app developers in J2SE and J2EE. Paul Krill writes In a letter to the “Java Technology Community” on Friday, specification leads on Java Specification Request (JSR) 220, which is the proposal for Enterprise JavaBeans 3.0, and JSR-243, for Java Data Objects, state that the two technologies feature divergent persistence models. “This divergence has caused confusion and debates among Java developers, and is not in the best of interest of the Java community,” said JSR-220 leader Linda DeMichiel who also is a Sun employee, and Craig Russell, a staff engineer at Sun who leads JSR-243. “In response to these requests [for an end to the unwanted divide], Sun Microsystems is leading a community effort to create a single POJO (Plain Old Java Object) persistence model for the Java community,” the letter said.
Post a Comment
Read more