Not permanent is one thing. But not providing any true Heads up and EOL is another. Finding out in Feb of this year because it was that way in the beta is not exactly good.
Dropping support should of been announced when Leapoded was release that 2011ish is when it was going to drop support for it. This gives a lot more time to make sure things are updated and are going to prevent a lot of problems.
For a lot of software devs that is kind of a bomb shell to have to deal with update legacy code in a relatively short time span.
Microsoft for examle with Vista gave noticed what they were going to do and at least gave quite a bit of warning hey the older stuff is not going to work. Now did companies listen no. But they still gave it. Vista took heat for what was beyond MS control and W7 comes out and those problems were fix and MS also gave plenty of warning that in 64 bit version of windows 16 bit programs would not be supported. They gave plenty of warning.
Apple gave no warning and that is the key thing. It is the poor communication that is a problem.
I'll give you the no warning to the users as they do not pay attention to this and there will probably be some "Why doesn't x run in 10.7?" threads here come next month (along with "Where did Java/Flash go?"). They really should be more explicit there.
But I seriously cannot get behind your argument that developers were blindsided here. Rosetta was a transitional technology, just like Classic. It was meant to ease transition and then go away. I could understand your point if this was 2007 or even 2008. This is 2011. Relying on something that is clearly transitional for so long is blatant sticking your fingers in your ears and yelling "I'm lazy, lalalalalal!"
This isn't like Carbon 64 where Apple was supporting it only to pull the rug out (even then there were some hints but it doesn't excuse Apple for faking devs out like that). Over half of Rosetta's webpage back in 2006 talked about talking to your developers about upgrading or sidegrading to a universal version of the app. Isn't that kind of a hint there?
I'd like to think being a good developer is being able to pick up on which direction the wind is blowing so you don't end up in a dead end and out of gas.