I am convinced there is some kind of long-term drinking game going on in the C standards committee to see how many different uses they can come up with for the word "static".

Amazing that such a large percentage of debugging involves determining exactly what you are debugging. The definition of the problem, many times, is the solution.

Might be a good time to mention Rubber Duck Debuggging. http://en.wikipedia.org/wiki/Rubber_duck_debugging

It's worse than the article describes. Those laid off are terrified to say anything publicly. From what I can gather, the total may be double the quoted number. In addition, morale is at rock bottom, with a number of people leaving on their own. Opera as we knew it is gone.

I worked for Opera for seven years, three of them managing the core testing team. I left a year ago. It breaks my heart to see how the current management treats some of the best engineers I've ever met, loyal to the company for a decade, like disposable rubbish. Here's your ten-year watch, now fuck off.

In the 2010 downsizing (described by the HR VP as "rightsizing"), they at least tried to make the decisions look good internally, blaming the economic downturn. The last two rounds they didn't even bother. No explainations, just individual talks - and a wave of fear.

The only good news is that there's plenty of fantastically skilled engineers available. I've hired one myself. If you need anyone, drop me a line, and I'd be happy to recommend someone for your open position. My loyalty is to my old team and the technology - not the current mismanagement. /c:

Not a commentary on this project per se, but I can't help but think when I see "X in javascript" voted up that the implicit frame is: "isn't it impressive what you can do in javascript now?"

But if you flip that statement on its head, the equivalent is "The web has finally caught up with what we could do on a 1997 desktop!"