←back to thread

1114 points namukang | 1 comments | | HN request time: 0.192s | source
Show context
azangru ◴[] No.43679631[source]
I've skimmed through the comments; and seen that most people have commented on the cog in the machine thing, or on layoffs in general and how they suck.

To me, the shock from this blog post was about seeing a Chrome developer relations engineer whom I have grown to admire and who has been doing a stellar job educating web developers on new html and css features, get the sack. He was one of the best remaining speakers on web topics at the Chrome team (I am still sad about the departure of Paul Lewis and Jake Archibald); and produced a lot of top-notch educational materials (the CSS podcast; the conference talks; the demos).

What does this say about Google's attitude to web and to Chrome? What does this say about Google's commitment to developer excellence?

I understand that this is a personal tragedy for Adam; but for me personally, this is also a huge disillusionment in Google.

replies(13): >>43679884 #>>43679890 #>>43679922 #>>43679964 #>>43680265 #>>43680397 #>>43680859 #>>43681914 #>>43682871 #>>43683096 #>>43683779 #>>43684115 #>>43684150 #
atotic ◴[] No.43682871[source]
Agreed, Adam really is one of the best at what he does. His talks, demos, were always so interesting. My guess is that he'll be at Microsoft shortly.

What Google is saying with this layoff is that they no longer care about web developer relations. Chrome has not been well funded for years.

Firefox did the same thing five years ago, when they fired David Baron, who was one of the top 5 engineers in the world that understood how HTML layout works. He got instantly hired by Chrome.

It is kind of crazy that the core group that moves web standards forward is around 150 people. And most of them did not get rich off it, and have been doing it for decades.

replies(3): >>43683009 #>>43683194 #>>43694035 #
1. azangru ◴[] No.43683194[source]
> Chrome has not been well funded for years.

Hasn't it? It has still been developing quite rapidly; and used to lead in interop scores (reflecting how well a browser conforms to the specs).