While it is no problem for the slashdot crowd, less tech-savvy users have huge problem with even the smallest change.

Here is one example:
I have a friend in his 50ties who just started to use computers and the internet. He barely known what a search engine is, and often has problems reading the small font of tool tips etc. He used IE8 and was used to type into the "Google Box" to search. Along comes the change to IE 9 and all of a sudden he has to use the URL bar to search. He has problems with that. This is not what he learned and how he expects things to work.

He also had problems when his mail client changed the Icon to write e-mails from "Mail" to "Compose".

A Hammer is a hammer is a hammer. In the real world tools do not change how they are operated.
Even cars did not change their UI in the past 100 years. And the elements that did change, are often not used by everyone. How many people do you know who do not know how to set their clock correctly? Who do not use their GPS? VCRs are/were known hard to use, because each and every one has a different way to program a recording.

While *I* love new UIs and shiny things in general, there are lots of people out there who cannot abstract computers and are lost when small things change.

I have no idea if you work in development or system administration, but generally improving the situation depends on two things:
1) Do what you agree to do on time and within budget
2) Say no to anything else

There are lots of books on the subject of time management, project management or the software development processes and they all boil down to these two rules. If you work in a company that does not allow you to say no, read one of those books and then explain to management why working with $method would greatly improve everything (including the coffee). As soon as you get them to agree to $method you can use $method to say no (i.e. $feature is not in our sprint, $task is on the KanBan board and blocked by $actually_important_task, etc).

If you have no support from management, consider updating you resume.
Here are three books that I found worth reading:
Kanban: Successful Evolutionary Change for Your Technology Busines by David J. Anderson
Time Management for System Administrators by Thomas A. Limoncelli
Agile Software Development with Scrum by Ken Schwaber and Mike Beedle (Author)

The most interesting part are the case studies and how the authors manage to say "no" in a management-compatible way.

>Or since everyone skips 13

Slackware 13.37 begs to differ!

I am relieved that sliverlight will never support such harmful technology!

As long as rain forests are stubbed for easier access to copper mines
As long as local people are poisoned by the toxic byproducts of metal refinement
As long as people in Africa or Eastern Europe dissable old computers without any protective clothing
As long as children assemble computers for $1/hour in Asia

I refuse to equal "green computing" and enviromental friendly.

In truth it is just another catchy phrase to sell you yet a new computer. Buying a new computer does nature more harm than just keeping your old computer.