| « Prev | Page 1 | Page 2 | Next » |
|
Always funny to read stuff like that in code. Would have been better if it had more swearing and/or name-calling, but what can you do?
P.S. fist! |
|
So is it the programmer or the designer who writes at a first-grade level?
|
|
Whats the site?
|
|
Don't know which site, but there is one other site that also cites this: http://tedivm.livejournal.com/38768.html, but uneditted...
|
|
heaven forfend we handle disputes professionally.
|
Re: Inflammatory Comments
2007-06-29 09:31
•
by
Anonymous!
(unregistered)
|
Disputes? There was no dispute! |
|
forfend \for-FEND\, transitive verb:
1. a. (Archaic) To prohibit; to forbid. b. To ward off; to prevent; to avert. 2. To defend; to protect; to preserve. ahahahahahahahahah Is that guy from the 13th century? |
|
The comment-part doesn't show up in the RSS-feed. Just failure?
|
|
http://tedivm.livejournal.com/38768.html
|
|
This must be what happens when the company refuses to invest in a bug-tracking system.
|
|
I'm sorry - did somebody really say rembeded?
I wouldn't have rembeded anything that person said either. |
Re: Inflammatory Comments
2007-06-29 10:20
•
by
Anonymous Pedant
(unregistered)
|
Pathetic. It should clearly be "reëmbedded". |
|
It's a shame that Google doesn't let you search hidden text (comments, HTML, etc.)
|
Re: Inflammatory Comments
2007-06-29 11:02
•
by
jack-ass
(unregistered)
|
|
THE REAL WTF IS SOMEONE IS USING LIVE JOURNAL!! OOOH LOL!!!
|
Re: Inflammatory Comments
2007-06-29 11:04
•
by
Gabelstaplerfahrer
(unregistered)
|
It HAS to be the designer, all designers I know have serious grammar problems... |
|
Should you not be quoting your source?
http://tedivm.livejournal.com/38768.html |
Re: Inflammatory Comments
2007-06-29 11:15
•
by
ChrisH
(unregistered)
|
No wonder they didn't get on.. it must have been a culture shock. |
Re: Inflammatory Comments
2007-06-29 11:29
•
by
Karl von L.
(unregistered)
|
Agreed; this doesn't look like an argument to me. The third paragraph (the one with the "forfend" comment) seems to be complaining about MSIE, not the other party. |
Re: Inflammatory Comments
2007-06-29 11:34
•
by
Alice
(unregistered)
|
Wow, if you really didn't know that idiom and needed to look it up, you really have no grounds making fun of someone. captcha: darwin? that's telling you something. |
Re: Inflammatory Comments
2007-06-29 11:51
•
by
Sgt. Preston
(unregistered)
|
I have to assume that this is unmarked-up sarcasm, because in my experience programmers speak English that is only slightly less butchered than that of marketing reps. |
Re: Inflammatory Comments
2007-06-29 12:05
•
by
Ynonymous
(unregistered)
|
"remembered", more likely. |
Re: Inflammatory Comments
2007-06-29 12:05
•
by
The Frinton Mafia
(unregistered)
|
Nah, he's just literate. That's what we call it when someone is able to use language to communicate. In this case, by using 'forfend' rather than 'forbid', he's creating a humorous, tongue-in-cheek effect that offsets the otherwise negative tone of his comment. See? That's not so hard, is it? Let's try another example: "Heaven forfend you choose to educate yourself rather than yipping at the ankles of your betters." |
Get thee back to digg, child. |
|
In both the anonymized and the livejournal version, the "Thanks" name and the initial match.
Perhaps it wasn't a flamewar so much as a split personality. Either way, pretty unprofessional. |
Re: Inflammatory Comments
2007-06-29 12:31
•
by
noobnoob
(unregistered)
|
|
riiiighht... forfend, duh. It's such a common word. :|
|
Re: Inflammatory Comments
2007-06-29 12:34
•
by
Les
(unregistered)
|
Whoooooooooooooooooooosh![1] [1] Sound of joke flying overhead[2] [2] Normally I wouldn't bother to explain that, but in the circumstances... |
Well, authorities are made up of human beings, and, as such, can be wrong. In this case, I put it to you that, at least in the case of the idiom "heaven forfend", that the word "forfend" is not archaic, and that I hear it frequently. |
Re: Inflammatory Comments
2007-06-29 12:38
•
by
Jim Bob
(unregistered)
|
you're a fucking faggot |
|
The real WTF is that both web programmer and web designer are the same person
|
Re: Inflammatory Comments
2007-06-29 13:20
•
by
Brad
(unregistered)
|
Woah! Run along now, back to digg. |
Re: Inflammatory Comments
2007-06-29 13:20
•
by
Brad
(unregistered)
|
Woah! Run along now, back to digg. |
Re: Inflammatory Comments
2007-06-29 13:25
•
by
T$
(unregistered)
|
I'm beginning to think you're right
He's thanking brian and his name is B, that's all you need to know. |
|
http://tedivm.livejournal.com/38768.html
We can now see the true extent of the anonymization at work... s/Josh/Brian/; s/-J/-B/; postToWTF(); |
|
It's a common knowledge that source code can only be viewed by developers
|
|
"The problem is that IE just doesn't bother rendering anything outside of an enclosing element. It just doesn't draw the parts that stick out."
Maybe you should try overflow: visible? |
Re: Inflammatory Comments
2007-06-29 14:29
•
by
Harry
(unregistered)
|
A reference to Paula has been removed as well. |
|
This is remeniscent of that scene near the beginning of the movie Airplane where the two (male and female) announcers started arguing over the Public Address system!
|
Re: Inflammatory Comments
2007-06-29 14:36
•
by
Sgt. Preston
(unregistered)
|
Too cool, Jim Bob! You can tell from just his comments both his sexual orientation and what he's doing right now? I am totally impressed! |
Wasn't Jim Bob* just remarking on his surprise at discovering that the being with whom he had been anticipating a deep and meaningful discourse on the vagaries of grammar through the ages *deep breath* turned out, in fact, to be a peculiarly sentient bundle of firewood? ______ * Of "big fat balls" fame...? Shame about the teeny weeny penis, of course. Ah well, I guess we all brag about what we can. |
|
*cough* *cough*
el.style.clip.overflow = "visible"; or maybe even OMFG el.style.position = "absolute"; or el.style.clip = "rect(-1000,-1000,-1000,-1000)"; nah, none of those things could ever work.... |
|
This was called inflammatory and an argument? Hell, they're merely discussing what a messy browser IE is.
The only real WTF (aside from the fact that this was posted) is the "<div><a></div>". I still have some hope that "good" was sarcastically used here, but unfortunately I can imagine very well that it isn't. It's called a tag, folks. You open it, you close it. How hard is that? |
Re: Inflammatory Comments
2007-06-29 15:34
•
by
Jim Bob
(unregistered)
|
I've got big balls and you ain't got shit |
I thought we were here to discuss programming, not elephantiasis and constipation? Ah, the joys of the Intarweb. |
|
Please don't feed the troll.
|
We're not feeding it, we're trying to poison it. Trolls are really funny when they die in screaming agony. |
Re: Inflammatory Comments
2007-06-29 17:23
•
by
Jim Bob
(unregistered)
|
Hey a/s/l? |
I'm not into your kind. /me slaps Jim Bob upside the head with a large trout |
Re: Inflammatory Comments
2007-06-29 18:25
•
by
n/a
(unregistered)
|
|
This discussion is quite funny when you consider the name of the thread is Inflammatory Comments.
|
|
Your templating system no doubt has a way of representing comments that will not go through to the rendered page -- quite possibly <%-- like this --%>. If you use its comments, rather than HTML/SGML comments, then only the developers will be able to read them, not everyone who accesses the site you're building.
|
|
So since some of you found my LJ (yes, I know, I'm pathetic) I thought I would answer some questions-
First off, I didn't change the names, the originals from the LJ are the proper ones. To make matters more confusing, the designer is named Joshua and the programmer Josh. Josh, the programmer, can't spell at all, and Joshua thinks hes god. Neither of them get any work from us anymore (they were both contractors) but when we were editing a site they did we found that tidbit. Robert H. |
| « Prev | Page 1 | Page 2 | Next » |