clintjhill

It is way to easy to do "manager drive-by" and get absolutely no sense of reality from employees.

This is on both sides to get right. The manager waiting, and the employee taking the time to "look them in the eye".

Thank you for that. I've been looking for this concise a statement to make in debates I've had in the past.

"To allow developers to choose the best language for the job, Twitter has invested a lot of effort in writing internal frameworks which encapsulate common concerns."

The single best investment companies can make is to allow developers to choose their specialty, and their language. Otherwise you have a huge overhead of skill set mismatch. And your talent pool can be bigger if you're open to more than one language.

It's a refreshing view.

But ... there are good reasons to decompose and expose these things in your API. While maybe not for Public consumption but certainly for Private.

It's my opinion that the way REST beats SOAP in the enterprise is that in almost all cases it's much quicker to build decomposed services. And then likewise composition of said services is also much easier.

But to the extent that they are all "lame database serialization" layers, I'd have to say "well - ya". REST is kind of just that.

I think that what you're really trying to say is that implementations you have found don't do HATEOAS.

On that topic, to rely on an 'Accept' header is pretty risky. That presumes the client will always have control over the headers. It is in my opinion always wiser to make the API determine mime type by extension (.html, .xml, .json etc).

Never do this with absolutely private data, but then again.

I would only respond with that in particular, GWT is more than a compiler - it is as much a JRE as anything. So there is more to it. I personally don't see Google doing much public interaction with the development of the GWT compiler. If it's left to Google and its own time then my point remains.

JavaScript on the other hand really doesn't have a single organization leading it's development. Maybe this is an argument to be made about its perceived slow progress. Language design by committee is pretty slow.

More choice is good. Always. But right tool for the job should always win.

GWT could be really strong. But it's this single maintainer problem that I think prevents it's penetration into the market.

Sadly when I hear people talk about the "strengths" of GWT, debugging and IDE debuggers is what I hear most. If that is the core reason for using GWT it seems shortsighted.

And for me personally I find that using Java (static typed system) to compile down to JavaScript (dynamic function system) is too big a paradigm switch for developers to maintain. Other languages, specifically functional type languages are far better for maintaining language paradigms in compiler situations.

Then punk became accepted. Then it even became commercial. Now you can't recognize punk.

AZ is the state where a guy died doing his job in a photo radar vehicle. He was shot by a guy who felt the man in the vehicle was "the government". These families and homes are now targets.

EDIT: Sincerely - sorry. I get the sarcasm.

My curiosity is why do people really hate Zed? Is it because he says things that hit at the core of their insecurities? Or is it simple jealousy?

I honestly don't think it's because he's wrong.

I wish I had a solution to provide to the larger discussion - but I'm not that smart.

Yours is much better.

There is no magic means. Simply lack of appreciation for children from other countries compound with a reversed process of quality.