Ha ha. No that anyone cares or will probably even read this, but I happen to think the ending of the Dark Tower series was damn good. And without spoiling anything, how could a tale like that, which revolves around so much metaphysics and conceptual versions of God have a standardized, cookie cutter ending? I think, give the subject matter, King took what was probably one of the best options he had.
With that argument aside, the Dark Tower series did get progressively worse over time, but nowhere near as bad as the Wheel of Time. I started reading book six and just said fuck it. Too boring, too much detail, too many "main" characters.
I disagree. I do web programming everyday, 8 to 14 hours a day. I do understand your point, but there's a time and place for everything, including client side scripting. There's a ton of stuff that can't be done on the server side, and the DOM is a wonderful thing to work with if you don't go overboard.
For example, I've written a few web applications per client spec that required various effects, animation, windowing, and tab features. These are all things which are better left to Javascript, and in my preference, the jquery and interface libraries. In fact, there's no real way to accomplish most of those effects without client side scripting. Hell, even Slashdot uses Javascript in their comment system, Firehose, etc. Or look at Google Apps, GMail, YouTube. Not even possible without client side scripting. A well programmed client side script (like anything Google's coded) runs great on even a 500MHz Pentium 3.
Anyway, my point is that while I can understand minimizing client side programming, it shouldn't, and can't really be avoided completely. I personally love mixing client and server side programming to draw out the strengths in both methods. Just because the idiots at Digg can't program, doesn't mean the whole thing should be thrown out.
I failed a polygraph when I was telling the truth. I was looking at 14 years in prison, so the pressure was intense and I was nervous as fuck. The end result: The polygraph said I was lying about not shooting some guy I had never met in the face.
I can't even imagine what would've happened if that would've been considered "evidence" admissible in court. I'd probably be in prison right now.
All my pirat... err, I mean all my friend's pirated versions of Windows activate just fine. However, I've seen some people actually buy Windows and then get a false positive. Ha ha. WGA works great.
Well, I for one have run Vista, and quite extensively, and I can speak from experience that turning off the search indexing in Vista is a trivial task that can be accomplished through disabling the service, which as many have noted, is a relatively simple task for any human and/or installer to do.
I'm not trying to defend Microsoft, it's just that in this case, Google are being complete idiots.
I'm playing devil's advocate here, because honestly the blog post is trash to begin with. However, the post is obviously not meant to illustrate "truth", but merely the authors position, much like an editorial. Plenty of news has come directly from blogs, for example, last week's story about the MPAA violating a software license, which broke directly from the software author's blog. It seems to have been around 2004 (to me) that blogs started actually breaking news. Like I said though, I'm just playing devil's advocate here, and I too fail to see how this blog post constitutes "news." I just don't agree with the blanket statement that blog posts can't be informative and newsbreaking, which is what I construed from your initial post, whether that was your intended connotation or not.
Well, I must say I'm surprised;to after getting no response to my previous emails to the MPAA about their use of Forest Blog at the tail end of last year I got a result within five hours this time, unless they were just replying to the original email?
Anyway, thanks to Paul Egge and Richard Kroon the situation has now been resolved and they've removed Forest Blog from their web server.
I'm writing this movie about a dude named Phreedom O'speech. He's a good guy, tries to be fair to everyone, and the common people seem to really like him. However a group of terrorist find him to be a threat to their goal of world domination and decide to chop him up into pieces with an axe: first they chop off his fingers. Blood, bones, and flesh spew everywhere. They rip off his eyelids just to torture the poor guy, but they don't stop there. Off go his balls in one fell swoop of the terrorists knife. The people that respected poor Phreedom O'Speech mourn his death, but did nothing to prevent it, merely sat and watched... too busy writing shitty analogies at 3:30am that are bound to get modded as off-topic, flamebait, or my personal favorite: Insightful:(
Wow. That's odd. I would've figured IT workers who sabotage corporate systems would be the workers who are happy, secure, generally show up on time, work well with colleagues, and generally perform superbly. Goes to show you that logic doesn't always pay off. (I'm ready for the Troll/Flamebait mod guys:)
A delicious blend of flavors will keep this super salad on the top of your list!
Cook noodles according to package directions, but do not add flavor packets. Drain and cool. Cut noodles up slightly. Combine with other salad ingredients in a large bowl. In a small bowl, mix flavor packets, garlic and lemon juice and let stand at least 15 minutes. Add oil and mayonnaise and whisk until smooth. Pour dressing over salad and toss until thoroughly mixed. Garnish with red pepper rings and small grape clusters if desired. Quick and delicious!
Ingredients:
* 2 packages Chicken Flavor Top Ramen
* 8 cups spinach leaves, torn
* 1-1/2 cups turkey or chicken, cooked and diced
* 1 cup red or green grapes, halved
* 1 cup red pepper, slivered
* 1/2 cup cashews, chopped
* 1/2 cup gorgonzola or blue cheese, crumbled
Dressing:
* 2 Flavor packets from Chicken Flavor Top Ramen
* 4 cloves garlic, minced
* Juice from 1 small lemon
* 1/3 cup olive oil
* 1/4 cup light mayonnaise
I have a Toyota and I wouldn't dare trust my car to tell me if it's alright drive. What about false positives? What if I'm on the freeway and the car turns itself off? Wouldn't Toyota be liable for any damages? What if this results in people loosing their lives? What if I have a friend in the passenger seat who pukes on the drivers seat. What if, what if? There's too many variables in this. This is a horrible idea, and I will never buy a car that has this "feature"
Ha ha. Did you even read the piece you quoted? First you say: "No, they can't 'imitate' the feature" and then you quote directly from Microsoft where the spec says: "To faithfully replicate this behavior, applications must imitate the behavior of that application." Come on. Obviously Microsoft doesn't expect the general public to have the source code to old versions of Office. And for the millionth time, there are several applications that can already handle and correctly format legacy.doc files including WordPerfect and OpenOffice, so the programming work is largely done to imitate those features. And again for the upteenth time, I'm not endorsing this as a standard, I'm with everyone else who opposes this. However, the examples in the article do not appear to be the huge "standard breaking" ace card that every witch hunter here seems to be making it out to be. I hate Microsoft as much as the next guy, but the article doesn't present anything newsworthy, just FUD.
Ha ha. This seems to be the thread where everyone tells me I'm missing the point.
Quite honestly I understand this. I read the whole article, the format is a POS, everyone's life will be ruined. Yada yada yada. However, I believe you're missing a point here, in that some documents require consistent formatting, whether it's military, legal, scholarly, specs, drafts, you name it. By "updating" these pages by not supporting the old format you will breaking the layout of some documents that need a consistent layout. Is this going to affect a lot of documents? Of course not, but it is still a consideration, and I am playing devil's advocate after all.
Second, for the third time in this thread I'd like to mention that both WordPerfect and OpenOffice already have legacy support for old implementations of Word documents. Oh, and it likes the DOC format specs are published in full up to Word 97.
Now look, I understand this format is Microsoft's best interests and not the end user, but the entire time all I've been trying to say is that the fundamental points of this article are over hyped, they're going to effect a small number of users, and that WordPerfect and OpenOffice already have the programming to deal with legacy Word format problems. That's it. That's my point. My point is not that OpenXML is good, it sucks.
Damnit, I wasn't even close to done typing that and I hit submit when I meant to hit preview. Ha ha. Now I'm really going to get flamed.
Anyway, what I was going to say was that they simply need to "imitate" the feature, which OpenOffice/WordPerfect already do with their legacy Word doc support, making the point of this article moot. Now, don't get me wrong, this standard sucks, it's a bunch of floof, but so is the basis for this article.
I see everyone's point with this, I really do, but as long as companies support these tags the spec provided they would be in full compliance, would they not be? Here's a quote from the article/spec:
2.15.3.6 autoSpaceLikeWord95 (Emulate Word 95 Full-Width Character Spacing)
This element specifies that applications shall emulate the behavior of a previously existing word processing application (Microsoft Word 95) when determining the spacing between full-width East Asian characters in a document's content.
[Guidance: To faithfully replicate this behavior, applications must imitate the behavior of that application, which involves many possible behaviors and cannot be faithfully placed into narrative for this Office Open XML Standard. If applications wish to match this behavior, they must utilize and duplicate the output of those applications. It is recommended that applications not intentionally replicate this behavior as it was deprecated due to issues with its output, and is maintained only for compatibility with existing documents from that application. end guidance]
I thought this was announcing that it was released today. I was about to call in sick.
With that argument aside, the Dark Tower series did get progressively worse over time, but nowhere near as bad as the Wheel of Time. I started reading book six and just said fuck it. Too boring, too much detail, too many "main" characters.
For example, I've written a few web applications per client spec that required various effects, animation, windowing, and tab features. These are all things which are better left to Javascript, and in my preference, the jquery and interface libraries. In fact, there's no real way to accomplish most of those effects without client side scripting. Hell, even Slashdot uses Javascript in their comment system, Firehose, etc. Or look at Google Apps, GMail, YouTube. Not even possible without client side scripting. A well programmed client side script (like anything Google's coded) runs great on even a 500MHz Pentium 3.
Anyway, my point is that while I can understand minimizing client side programming, it shouldn't, and can't really be avoided completely. I personally love mixing client and server side programming to draw out the strengths in both methods. Just because the idiots at Digg can't program, doesn't mean the whole thing should be thrown out.
I can't even imagine what would've happened if that would've been considered "evidence" admissible in court. I'd probably be in prison right now.
All my pirat... err, I mean all my friend's pirated versions of Windows activate just fine. However, I've seen some people actually buy Windows and then get a false positive. Ha ha. WGA works great.
Signed In Love,
Captain Obvious
I'm not trying to defend Microsoft, it's just that in this case, Google are being complete idiots.
and I thought my cascading errors were bad!
With that said, feel free to mod me off-topic.
Mod parent up!
I'm playing devil's advocate here, because honestly the blog post is trash to begin with. However, the post is obviously not meant to illustrate "truth", but merely the authors position, much like an editorial. Plenty of news has come directly from blogs, for example, last week's story about the MPAA violating a software license, which broke directly from the software author's blog. It seems to have been around 2004 (to me) that blogs started actually breaking news. Like I said though, I'm just playing devil's advocate here, and I too fail to see how this blog post constitutes "news." I just don't agree with the blanket statement that blog posts can't be informative and newsbreaking, which is what I construed from your initial post, whether that was your intended connotation or not.
I'm thinking 2004 onwards.
Well, I must say I'm surprised;to after getting no response to my previous emails to the MPAA about their use of Forest Blog at the tail end of last year I got a result within five hours this time, unless they were just replying to the original email?
Anyway, thanks to Paul Egge and Richard Kroon the situation has now been resolved and they've removed Forest Blog from their web server.
I'm writing this movie about a dude named Phreedom O'speech. He's a good guy, tries to be fair to everyone, and the common people seem to really like him. However a group of terrorist find him to be a threat to their goal of world domination and decide to chop him up into pieces with an axe: first they chop off his fingers. Blood, bones, and flesh spew everywhere. They rip off his eyelids just to torture the poor guy, but they don't stop there. Off go his balls in one fell swoop of the terrorists knife. The people that respected poor Phreedom O'Speech mourn his death, but did nothing to prevent it, merely sat and watched... too busy writing shitty analogies at 3:30am that are bound to get modded as off-topic, flamebait, or my personal favorite: Insightful :(
Wow. That's odd. I would've figured IT workers who sabotage corporate systems would be the workers who are happy, secure, generally show up on time, work well with colleagues, and generally perform superbly. Goes to show you that logic doesn't always pay off. (I'm ready for the Troll/Flamebait mod guys :)
ahh, good eye. I missed that. Thanks.
ha ha. What are you talking about? Everything looks in order to me.
I'm available for hire. Please send me a Ferrari notebook, Office 2007, and a contract to sign away my soul. Did I mention I also blog?
A delicious blend of flavors will keep this super salad on the top of your list!
Cook noodles according to package directions, but do not add flavor packets. Drain and cool. Cut noodles up slightly. Combine with other salad ingredients in a large bowl. In a small bowl, mix flavor packets, garlic and lemon juice and let stand at least 15 minutes. Add oil and mayonnaise and whisk until smooth. Pour dressing over salad and toss until thoroughly mixed. Garnish with red pepper rings and small grape clusters if desired. Quick and delicious!
Ingredients:
* 2 packages Chicken Flavor Top Ramen
* 8 cups spinach leaves, torn
* 1-1/2 cups turkey or chicken, cooked and diced
* 1 cup red or green grapes, halved
* 1 cup red pepper, slivered
* 1/2 cup cashews, chopped
* 1/2 cup gorgonzola or blue cheese, crumbled
Dressing:
* 2 Flavor packets from Chicken Flavor Top Ramen
* 4 cloves garlic, minced
* Juice from 1 small lemon
* 1/3 cup olive oil
* 1/4 cup light mayonnaise
Serves 2
Ha. I thought he was just confused because everyone there ate his prosperity food.
I have a Toyota and I wouldn't dare trust my car to tell me if it's alright drive. What about false positives? What if I'm on the freeway and the car turns itself off? Wouldn't Toyota be liable for any damages? What if this results in people loosing their lives? What if I have a friend in the passenger seat who pukes on the drivers seat. What if, what if? There's too many variables in this. This is a horrible idea, and I will never buy a car that has this "feature"
Ha ha. Did you even read the piece you quoted? First you say: "No, they can't 'imitate' the feature" and then you quote directly from Microsoft where the spec says: "To faithfully replicate this behavior, applications must imitate the behavior of that application." Come on. Obviously Microsoft doesn't expect the general public to have the source code to old versions of Office. And for the millionth time, there are several applications that can already handle and correctly format legacy .doc files including WordPerfect and OpenOffice, so the programming work is largely done to imitate those features. And again for the upteenth time, I'm not endorsing this as a standard, I'm with everyone else who opposes this. However, the examples in the article do not appear to be the huge "standard breaking" ace card that every witch hunter here seems to be making it out to be. I hate Microsoft as much as the next guy, but the article doesn't present anything newsworthy, just FUD.
Quite honestly I understand this. I read the whole article, the format is a POS, everyone's life will be ruined. Yada yada yada. However, I believe you're missing a point here, in that some documents require consistent formatting, whether it's military, legal, scholarly, specs, drafts, you name it. By "updating" these pages by not supporting the old format you will breaking the layout of some documents that need a consistent layout. Is this going to affect a lot of documents? Of course not, but it is still a consideration, and I am playing devil's advocate after all.
Second, for the third time in this thread I'd like to mention that both WordPerfect and OpenOffice already have legacy support for old implementations of Word documents. Oh, and it likes the DOC format specs are published in full up to Word 97.
Now look, I understand this format is Microsoft's best interests and not the end user, but the entire time all I've been trying to say is that the fundamental points of this article are over hyped, they're going to effect a small number of users, and that WordPerfect and OpenOffice already have the programming to deal with legacy Word format problems. That's it. That's my point. My point is not that OpenXML is good, it sucks.
Damnit, I wasn't even close to done typing that and I hit submit when I meant to hit preview. Ha ha. Now I'm really going to get flamed. Anyway, what I was going to say was that they simply need to "imitate" the feature, which OpenOffice/WordPerfect already do with their legacy Word doc support, making the point of this article moot. Now, don't get me wrong, this standard sucks, it's a bunch of floof, but so is the basis for this article.
2.15.3.6 autoSpaceLikeWord95 (Emulate Word 95 Full-Width Character Spacing)
This element specifies that applications shall emulate the behavior of a previously existing word processing application (Microsoft Word 95) when determining the spacing between full-width East Asian characters in a document's content.
[Guidance: To faithfully replicate this behavior, applications must imitate the behavior of that application, which involves many possible behaviors and cannot be faithfully placed into narrative for this Office Open XML Standard. If applications wish to match this behavior, they must utilize and duplicate the output of those applications. It is recommended that applications not intentionally replicate this behavior as it was deprecated due to issues with its output, and is maintained only for compatibility with existing documents from that application. end guidance]