1970: "<i>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 orthodoxy.</i>"<p>1980: "<i>Another part of the necessary art of calling bullshit is to take down good ideas when they become inflated beyond what they can bear. Separating your code in functions that address single concerns is a reasonable idea that I support. But there's just not enough there there to dress it up in models, controllers, views, and all the other -- here's that word again! -- wankery that passes for muster in the MVC orthodoxy.</i>"<p>2010: (and this one's verbatim) "<i>Another part of the necessary art of calling bullshit is to take down good ideas when they become inflated beyond what they can bear. Using URLs instead of IDs in your json responses is a reasonable idea that I support. But there's just not enough there there to dress it up in HATEOAS, HAL, custom mime types, and all the other -- here's that word again! -- wankery that passes for muster in the hypermedia orthodoxy.</i>"<p>I never could understand this attitude of overt antagonism towards people who care about architecture. If you aren't partial to such discussions yourself, at least show some respect for the people who, through years of wankerous discussion and debate, came up with and subsequently refined the pattern that propelled you to fame (or in the case of us mortals, at least gave us the tools to make our programming life a little easier). Now, I understand this particular guy is deeply invested in the MVC architecture. But that doesn't mean history stops here. REST (despite a long but somewhat underground history) and hypermedia are still in their infancy as an architecture. Many, many problems still remain unsolved and the process of debate meant to distill the good from the bad necessarily looks to outsiders as "wankery". Still, show some respect. The next person of Heinemeier's caliber will likely make their fame by bringing REST to the masses.
I agree wholeheartedly with with dhh's stated philosophy on the fact that code talks, bullshit walks and writing "future proof" code is a terrible idea (one that virtually every journeyman developer stupidly clings to for a while at some point in their career). But at the same time I'm not a Ruby fan, in large part due to the monkey patching ability he holds so dear.<p>Given the same philosophical outlook but perhaps less inherent trust in developers (including myself!) to always do the Right Thing, I've come to really appreciate Go as a no-bullshit language that does allow you to hang yourself (eg. the unsafe package, ability to ignore error returns via '_' variables, etc) but it at least makes you tie the rope to the ceiling before you can use it, so you have time to think about whether or not you really want to use it.
He keeps writing "Parsley" instead of "Parely". For other non-native english speakers (like me), here's the defintion:<p>Parley:<p>Parley (/ˈpɑrli/) is a discussion or conference, especially one between enemies over terms of a truce or other matters. For example, in Julius Caesar (a tragedy by William Shakespeare), the respective followers and armies of Brutus and Antony are ready for a truce. The root of the word parley is parler, which is the French verb "to speak"<p>Parsely:<p>Garden parsley is a bright green, hairless, biennial, herbaceous plant in temperate climates, or an annual herb in subtropical and tropical areas.
Some related posts that probably spawned this article. You can find DHH's response in the comments:
<a href="http://gammons.github.com/architecture/2012/12/22/where-the-logic-hides/" rel="nofollow">http://gammons.github.com/architecture/2012/12/22/where-the-...</a><p>This talk (31 min, grab some coffee) also gives a better context. <a href="http://confreaks.com/videos/1125-gogaruco2012-mega-rails" rel="nofollow">http://confreaks.com/videos/1125-gogaruco2012-mega-rails</a>
I think some clarity is in order.<p><i>While Java certainly isn't a pinnacle of language design, it took quite a few years of devolution to go from something relatively simple like servlets to the steaming pile of shit that is J2EE</i><p>I believe he means to say EJB here, and not J2EE, because Servlets are a part of J2EE.