The Parley Letter
david.heinemeierhansson.com
The Parley Letter
1–10 of 50 posts
Re: The Parley Letter
#2He keeps writing "Parsley" instead of "Parely". For other non-native english speakers (like me), here's the defintion:
Parley:
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"
Parsely:
Garden parsley is a bright green, hairless, biennial, herbaceous plant in temperate climates, or an annual herb in subtropical and tropical areas.
Re: The Parley Letter
#3Some related posts that probably spawned this article. You can find DHH's response in the comments:
http://gammons.github.com/architecture/2012/12/22/where-the-...
This talk (31 min, grab some coffee) also gives a better context. http://confreaks.com/videos/1125-gogaruco2012-mega-rails
Re: The Parley Letter
#4He keeps writing "Parsley" instead of "Parely". For other non-native english speakers (like me), here's the defintion: Parley: 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…
My guess is that iOS autocorrect strikes again. :)
Re: The Parley Letter
#5I guess we need a new entry in http://rubydramas.com
Re: The Parley Letter
#6He keeps writing "Parsley" instead of "Parely". For other non-native english speakers (like me), here's the defintion: Parley: 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…
My guess is that iOS autocorrect strikes again. :)
Autocorrect is a bad idea. The kind of spelling error that iOS corrects (At least as far as I know.) is a syntactic error. Whereas the kind of error that autocorrect introduces is a semantic error. A semantic error is much worse than a syntactic one. At worst, a syntactic error leaves your meaning ambiguous. At worst, a semantic error leaves your meaning incorrect or inverted.
Usually you can read past a syntactic error, but a semantic error could change the tone or meaning of your entire message.
Re: The Parley Letter
#7I think some clarity is in order.
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 believe he means to say EJB here, and not J2EE, because Servlets are a part of J2EE.
Re: The Parley Letter
#8Some related posts that probably spawned this article. You can find DHH's response in the comments: http://gammons.github.com/architecture/2012/12/22/where-the-... This talk (31 min, grab some coffee) also gives a better context. http://confreaks.com/videos/1125-gogaruco2012-mega-rails
My understanding is that this article was in response to various questions that were asked of him on the Ruby Rogues Parley list (all guests are on the list, and others can pay to be on the list). Of course, recent topics he covered like hypermedia were colored by those recent discussions.
Re: The Parley Letter
#9I guess we need a new entry in http://rubydramas.com
You know, this strikes me as very sane and cogent essay into maintainability and rails. Where does the drama come form?
Re: The Parley Letter
#10I think some clarity is in order. 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 believe he means to say EJB here, and not J2EE, because Servlets are a part of J2EE.
Yeah, and I don't think he's been keeping up with Java EE 6 - EJBs are dead, long live JPA annotations. Of course, Spring is likely on borrowed time too. Just maybe we can lose the whole concept of a "framework", lightweight or not, that has kept those architects in business for so long.