as almost every sizeable programming team, we have our own half-witted moron who just doest seem to get fired no matter how he screws up. but that's not enough for our idiot. this pest has to annoy everyone every month by telling us how great some crap we are not using really is, and how we should all switch. this month the crap de jour is lisp. the moron i'm talking about read a little bit of slashdot and online tutorials, and thinks we should use it. to my surprise, the management actually got fascinated by the promises of "intelligent web" that they apparently think could be smarter than the customers themselves and somehow tell them what they want to buy (the AI bubble of the '80s all over again) so they started looking into this and asked me to write a report on the feasibility of using lisp for our application to deliver this "intelligent content". (the fact is that i'm the only one who has actual real-world lisp experience) so now, instead of doing actual work in java and c++, because of this local moron, i have to waste my time on this. so to all you slashdot-wielding and usenet-spamming lisp evangelists i have to say this: before preaching something, learn the fucking subject. before you say that lisp is easy, try actually learning it! look at lispers with 10-20 year experience who argue about what a three-line snippet supposed and not supposed to do, what figging variables get bound, unbound, re-bound, shaddowed, what gets unwound, and what doesn't. if you think destructor semantics are obscure when combined with multiple inheritance, or that method overloading coupled with templates attract bugs - you aint seen nothing yet. before you pretend to be an intellectual and proclaim that other languages can be defined on top of lisp, write a hygienic "defmacro" replacement usable with the same syntax, but that isn't vulnerable to variable capture and inadvertant multiple argument evaluations, unless explicitly requested. do this without re-writing half of the compiler. no? you can't? then stfu! even guy steele, the author of lisp standard came to realize the crappiness of the language, so he had to create a new one - scheme (also a pile of shit). paul graham, the celebrated author of lisp books, couldn't help but call lisp "awkward" in On Lisp. is this convincing enough? sorry, i had to vent. i think i finally collected my thoughts for the 'report'.
> as almost every sizeable programming team, we have our own half-witted > moron who just doest seem to get fired no matter how he screws up. but > that's not enough for our idiot. this pest has to annoy everyone every > month by telling us how great some crap we are not using really is, > and how we should all switch. this month the crap de jour is lisp. the > moron i'm talking about read a little bit of slashdot and online > tutorials, and thinks we should use it. to my surprise, the management > actually got fascinated by the promises of "intelligent web" that they > apparently think could be smarter than the customers themselves and > somehow tell them what they want to buy (the AI bubble of the '80s all > over again) so they started looking into this and asked me to write a > report on the feasibility of using lisp for our application to deliver > this "intelligent content". (the fact is that i'm the only one who has > actual real-world lisp experience) so now, instead of doing actual > work in java and c++, because of this local moron, i have to waste my > time on this. so to all you slashdot-wielding and usenet-spamming lisp > evangelists i have to say this: before preaching something, learn the > fucking subject. before you say that lisp is easy, try actually > learning it! look at lispers with 10-20 year experience who argue > about what a three-line snippet supposed and not supposed to do, what > figging variables get bound, unbound, re-bound, shaddowed, what gets > unwound, and what doesn't. if you think destructor semantics are > obscure when combined with multiple inheritance, or that method > overloading coupled with templates attract bugs - you aint seen > nothing yet. before you pretend to be an intellectual and proclaim > that other languages can be defined on top of lisp, write a hygienic > "defmacro" replacement usable with the same syntax, but that isn't > vulnerable to variable capture and inadvertant multiple argument > evaluations, unless explicitly requested. do this without re-writing > half of the compiler. no? you can't? then stfu! even guy steele, the > author of lisp standard came to realize the crappiness of the > language, so he had to create a new one - scheme (also a pile of > shit). paul graham, the celebrated author of lisp books, couldn't help > but call lisp "awkward" in On Lisp. is this convincing enough? sorry, > i had to vent. i think i finally collected my thoughts for the > 'report'.
sca...@yahoo.com (scav50) writes: > so to all you slashdot-wielding and usenet-spamming lisp > evangelists i have to say this: before preaching something, learn the > fucking subject. before you say that lisp is easy, try actually > learning it!
Hmmm. I think I have to adjust my troll- and irony detectors, they freaked out on this article. -- (espen)
> as almost every sizeable programming team, we have our own half-witted > moron who just doest seem to get fired no matter how he screws up. but > that's not enough for our idiot. this pest has to annoy everyone every > month by telling us how great some crap we are not using really is, > and how we should all switch. this month the crap de jour is lisp. the > moron i'm talking about read a little bit of slashdot and online > tutorials, and thinks we should use it. to my surprise, the management > actually got fascinated by the promises of "intelligent web" that they > apparently think could be smarter than the customers themselves and > somehow tell them what they want to buy (the AI bubble of the '80s all > over again) so they started looking into this and asked me to write a > report on the feasibility of using lisp for our application to deliver > this "intelligent content". (the fact is that i'm the only one who has > actual real-world lisp experience) so now, instead of doing actual > work in java and c++, because of this local moron, i have to waste my > time on this. so to all you slashdot-wielding and usenet-spamming lisp > evangelists i have to say this: before preaching something, learn the > fucking subject. before you say that lisp is easy, try actually > learning it! look at lispers with 10-20 year experience who argue > about what a three-line snippet supposed and not supposed to do, what > figging variables get bound, unbound, re-bound, shaddowed, what gets > unwound, and what doesn't. if you think destructor semantics are > obscure when combined with multiple inheritance, or that method > overloading coupled with templates attract bugs - you aint seen > nothing yet. before you pretend to be an intellectual and proclaim > that other languages can be defined on top of lisp, write a hygienic > "defmacro" replacement usable with the same syntax, but that isn't > vulnerable to variable capture and inadvertant multiple argument > evaluations, unless explicitly requested. do this without re-writing > half of the compiler. no? you can't? then stfu! even guy steele, the > author of lisp standard came to realize the crappiness of the > language, so he had to create a new one - scheme (also a pile of > shit). paul graham, the celebrated author of lisp books, couldn't help > but call lisp "awkward" in On Lisp. is this convincing enough? sorry, > i had to vent. i think i finally collected my thoughts for the > 'report'.
> as almost every sizeable programming team, we have our own half-witted > moron who just doest seem to get fired no matter how he screws up. but > that's not enough for our idiot. this pest has to annoy everyone every > month by telling us how great some crap we are not using really is, > and how we should all switch. this month the crap de jour is lisp. the > moron i'm talking about read a little bit of slashdot and online > tutorials, and thinks we should use it. to my surprise, the management > actually got fascinated by the promises of "intelligent web" that they > apparently think could be smarter than the customers themselves and > somehow tell them what they want to buy (the AI bubble of the '80s all > over again) so they started looking into this and asked me to write a > report on the feasibility of using lisp for our application to deliver > this "intelligent content". (the fact is that i'm the only one who has > actual real-world lisp experience) so now, instead of doing actual > work in java and c++, because of this local moron, i have to waste my > time on this. so to all you slashdot-wielding and usenet-spamming lisp > evangelists i have to say this: before preaching something, learn the > fucking subject. before you say that lisp is easy, try actually > learning it! look at lispers with 10-20 year experience who argue > about what a three-line snippet supposed and not supposed to do, what > figging variables get bound, unbound, re-bound, shaddowed, what gets > unwound, and what doesn't. if you think destructor semantics are > obscure when combined with multiple inheritance, or that method > overloading coupled with templates attract bugs - you aint seen > nothing yet. before you pretend to be an intellectual and proclaim > that other languages can be defined on top of lisp, write a hygienic > "defmacro" replacement usable with the same syntax, but that isn't > vulnerable to variable capture and inadvertant multiple argument > evaluations, unless explicitly requested. do this without re-writing > half of the compiler. no? you can't? then stfu! even guy steele, the > author of lisp standard came to realize the crappiness of the > language, so he had to create a new one - scheme (also a pile of > shit). paul graham, the celebrated author of lisp books, couldn't help > but call lisp "awkward" in On Lisp. is this convincing enough? sorry, > i had to vent. i think i finally collected my thoughts for the > 'report'.
You used two capital letters on the third-from-last line. Are you slipping?
-- /-- Joona Palaste (pala...@cc.helsinki.fi) ---------------------------\ | Kingpriest of "The Flying Lemon Tree" G++ FR FW+ M- #108 D+ ADA N+++| | http://www.helsinki.fi/~palaste W++ B OP+ | \----------------------------------------- Finland rules! ------------/ "Stronger, no. More seductive, cunning, crunchier the Dark Side is." - Mika P. Nieminen
> You might also want to collect a few capital letters > to use in your report. (Or maybe insist on using > a language where case isn't that important.)
> as almost every sizeable programming team, we have our own half-witted > moron who just doest seem to get fired no matter how he screws up. but > that's not enough for our idiot. this pest has to annoy everyone every > month by telling us how great some crap we are not using really is, > and how we should all switch. this month the crap de jour is lisp. the
<<big snip of more complaints>>
Let's assume this is for real (survey says....) Write a report. Add some capitals. Suggest that this guy (your nemesis) is assigned to do a pilot project using Lisp and (oh, say) Linux. Set a reasonable time-limit of six months and suggest he be given an office off-site where he can really concentrate on the work.
Now he's out of your hair for six months!
(BTW, that little line between the e and s of the last line is an apostrophe. Look it up.) -- Gary
Ian Wild <i...@cfmu.eurocontrol.be> writes: > scav50 wrote:
> > as almost every sizeable programming team, we have our own half-witted > > moron who just doest seem to get fired ...
> "Doest"? Too much reading of the KJV, I'd guess.
> > sorry, > > i had to vent. i think i finally collected my thoughts for the > > 'report'.
> You might also want to collect a few capital letters > to use in your report. (Or maybe insist on using > a language where case isn't that important.)
Forget the capital letters, I want a paragraph break!
sca...@yahoo.com (scav50) wrote in message <news:e0a34273.0305132049.51a2dad9@posting.google.com>... > and how we should all switch. this month the crap de jour is lisp. the > moron i'm talking about read a little bit of slashdot and online > tutorials, and thinks we should use it. to my surprise, the management > actually got fascinated by the promises of "intelligent web" that they > apparently think could be smarter than the customers themselves and > somehow tell them what they want to buy (the AI bubble of the '80s all > over again) so they started looking into this and asked me to write a > report on the feasibility of using lisp for our application to deliver > this "intelligent content". (the fact is that i'm the only one who has
You should actually thank your local moron. You can just write a half page report where you mention the "AI bubble" (be sure not to forget the AI winter). It will take a few minutes. He spared you the trouble of doing actual research and, God forbid, use your brain.
> but call lisp "awkward" in On Lisp. is this convincing enough? sorry,
scav50 wrote: > to my surprise, the management > actually got fascinated by the promises of "intelligent web" that they > apparently think could be smarter than the customers themselves and > somehow tell them what they want to buy (the AI bubble of the '80s all > over again) so they started looking into this and asked me to write a > report on the feasibility of using lisp for our application to deliver > this "intelligent content".
You'll be doing your management a big favor if you tell them that the notion is silly that writing a program in Lisp makes it more likely to deliver "intelligent" anything. It's just a programming language, for chrissake! Be sure to take a couple of Valium before trying to talk to them, though.
