I agree. I migrated from a Palm device to a Compaq Ipaq with PocketPC 2002 and still like to use the graffiti alphabet because I've gotten so proficient with it. I wonder if future version of PocketPC will continue to support graffiti (it supports graffiti, a handwriting recognizer, jot and a onscreen keyboard for input) or will drop it in favor of graffiti2?
I agree with you wholeheartedly that the top ten document is a great approach. And it is something I'm going to bookmark and I may even send out to my co-workers and associates.
However, I don't think it would be that big an effort to write a checklist of things to look for (things to avoid) for most, if not all popular web scripting languages, cgi languages, servlet containers, etc., for the top ten document. If everyone picks their favorite (I've got two of 'em) and gets together with other enthusiasts, I would be willing to bet that every language worth using will be covered. Then developers can share these documents on various development sites to inform those of us who may not be as familiar with the caveats or gotchas in languages that we don't use all the time.
Even if I know the top ten list by heart, and am familiar with all the general things to look for, I may or may not know that the use of one function or method in any particular language is preferred over another because of security concerns, reliablity, efficiency, etc.
It's a nice start and definately points out some things developers should be aware of.
But how about someone puts together a more specific checklist/tutorial for each point and write it around their favorite development language (PHP, ASP (cough), etc.).
Who's not busy?
Re:But, did you know the net is only for commerce?
on
Dow vs. Parody
·
· Score: 2, Informative
What gets me here is that, get this, from Dow's own web site:
Actually, that is not from 'Dow's own web site'. It's from a site that is set up to look almost exactly like one sponsored, maintained or supported by DOW. It's not. It's an example of parody gone too far. There doesn't even seem to be a disclaimer about the entire site being parody.
The original post does however mention that the submitter was fooled as you were. It seems you did a good job and RTFA, but should have spent a little more time to RTFP more carefully.
Slashdot Mirror
I agree. I migrated from a Palm device to a Compaq Ipaq with PocketPC 2002 and still like to use the graffiti alphabet because I've gotten so proficient with it. I wonder if future version of PocketPC will continue to support graffiti (it supports graffiti, a handwriting recognizer, jot and a onscreen keyboard for input) or will drop it in favor of graffiti2?
I agree with you wholeheartedly that the top ten document is a great approach. And it is something I'm going to bookmark and I may even send out to my co-workers and associates.
However, I don't think it would be that big an effort to write a checklist of things to look for (things to avoid) for most, if not all popular web scripting languages, cgi languages, servlet containers, etc., for the top ten document. If everyone picks their favorite (I've got two of 'em) and gets together with other enthusiasts, I would be willing to bet that every language worth using will be covered. Then developers can share these documents on various development sites to inform those of us who may not be as familiar with the caveats or gotchas in languages that we don't use all the time.
Even if I know the top ten list by heart, and am familiar with all the general things to look for, I may or may not know that the use of one function or method in any particular language is preferred over another because of security concerns, reliablity, efficiency, etc.
It's a nice start and definately points out some things developers should be aware of. But how about someone puts together a more specific checklist/tutorial for each point and write it around their favorite development language (PHP, ASP (cough), etc.). Who's not busy?
Actually, that is not from 'Dow's own web site'. It's from a site that is set up to look almost exactly like one sponsored, maintained or supported by DOW. It's not. It's an example of parody gone too far. There doesn't even seem to be a disclaimer about the entire site being parody.
The original post does however mention that the submitter was fooled as you were. It seems you did a good job and RTFA, but should have spent a little more time to RTFP more carefully.
And let us not forget: If it weren't for all the money the U.S. poured into the arms race, we'd probably all be eating borsch (wait for it....)
IN SOVIET RUSSIA!