31–40 of 50 posts
1970: " Another part of the necessary art of calling bullshit is to take down good ideas when they become inflated beyond what they can bear. Organizing your instructions in a clear way is a reasonable idea that I support. But there's just not enough there there to dress it up in function calls, machine optimization, and all the other -- here's that word again! -- wankery that passes for muster in the compilers ortho…
Earlier quoted context omitted.
You know, this strikes me as very sane and cogent essay into maintainability and rails. Where does the drama come form?
To DHH credit, he always has fair points in his opinions, but the way he expresses these points is never diplomatic. For example, he couldn't resist making some blanket statements about java world and rspec. I am not sure about how intentional that is, but it surely is dramatical in 'flame war eliciting' sense of word.
Earlier quoted context omitted.
Let me translate it for you, then. Wankery: Complexity brought on by the love of an abstract idea without meaningful practical benefit. By definition I don't see the point in architectural exploits that can be labelled wankery.
I know, you've repeated that several times. "Without meaningful practical benefit" is what I'm referring to when I say you keep stating that you're missing the point. Just because you happen to not see the meaningful practical benefit doesn't mean there isn't one.
Earlier quoted context omitted.
You know, this strikes me as very sane and cogent essay into maintainability and rails. Where does the drama come form?
To DHH credit, he always has fair points in his opinions, but the way he expresses these points is never diplomatic. For example, he couldn't resist making some blanket statements about java world and rspec. I am not sure about how intentional that is, but it surely is dramatical in 'flame war eliciting' sense of word.
Earlier quoted context omitted.
Let me translate it for you, then. Wankery: Complexity brought on by the love of an abstract idea without meaningful practical benefit. By definition I don't see the point in architectural exploits that can be labelled wankery.
I know, you've repeated that several times. "Without meaningful practical benefit" is what I'm referring to when I say you keep stating that you're missing the point. Just because you happen to not see the meaningful practical benefit doesn't mean there isn't one.
I made it a ton as a youth. I had to have about a thousand, "Oh, now I see what they're talking about" moments before I learned to keep my mouth shut long enough to actually learn something.
Earlier quoted context omitted.
To DHH credit, he always has fair points in his opinions, but the way he expresses these points is never diplomatic. For example, he couldn't resist making some blanket statements about java world and rspec. I am not sure about how intentional that is, but it surely is dramatical in 'flame war eliciting' sense of word.
DH2 critique in the Paul Graham pyramid: http://www.paulgraham.com/disagree.html
Earlier quoted context omitted.
J2EE's sins include far more than just EJB. See http://en.wikipedia.org/wiki/Java_Platform,_Enterprise_Editi... . Servlets got just started running with a bad crowd, even though deep down it was a good kid.
Personally I wouldn't let servlets off that easily. One of the basic design choices they made was one request handling function per class (the service method, delegating to doGet/doPost/etc for http requests). As a result, most applications actually needed another framework on top of servlets to do routing based on request URL and mapping on to some model of server side components, like MVC. See for example struts, s…
The Servlet spec was finalized more than 15 years ago, when CGI scripts were the mainstream server-side tech and browsers were circa version 3. The domain "google.com" wasn't registered until 3 months later. I think Servlets were reasonably well done for the time. The web was obviously dominant, but FTP was still widely used, and it certainly wasn't clear that newer protocols wouldn't be important as well. Rails didn't turn up until 8 years later.
One could certainly blame the java folks for stopping there, but there wasn't a lot of advantage to be gained from redoing the foundations in a way that forced everybody to rework all of their existing servlet code. And as you say, the community was making solid progress on their own, so it's probably better that Sun didn't interfere.
Earlier quoted context omitted.
The JAva point I felt was truly fair here. Servlets were good, but then it became the huge EJB which was bad. His rspec opinion - as expressed here that is - was "I dont like the DSL". Those seem fine really.
Just as a pointer I would recommend to get up to date with latest JEE specs and standards before making judgement What I see is most people base their opinion on EJB2 from past and they keep ranting about that. Also java ecosystem doesn't start and end with JEE
OTOH, the servlet API is nice.
Earlier quoted context omitted.
DH2 critique in the Paul Graham pyramid: http://www.paulgraham.com/disagree.html
Nope. He is criticizing based on consequence, which is the generation of pointless flame wars.
I guess we need a new entry in http://rubydramas.com