No thank you. If I want interactivity, I'll build/buy a client app that
Well, I find it funny that you say that, when in fact you have some
JavaScript on your site as well.
There's also the accessibility issues
Well, as I've said, I've worked pretty hard to remove the reliance upon
JavaScript. I think there are only a couple of cases
ahh - I see. have you considered a 'go' link set within <noscript> ?
Yes, of course. And, believe it or not, it's already implemented for two
scenarios I briefly mentioned. When a search results in exactly one option
(e.g. search for "array simulate procedure" without the quotes) or a request
for a specific article (e.g. search for "2248" without the quotes).
and the search engine spiders to consider.
To put it bluntly, I could give a rat's ass about search engines. Most of
them can't deal with ASP pages anyway; and I'm not going to start touting an
ASP site that's published as plain HTML or some such nonsense. This is
going come across as quite pretentious, but I'm sure a very large percentage
of ASP developers have at least heard of my URL. And I've worked pretty
hard on my search engine too, so anyone who knows about it shouldn't need to
search the web for articles on my site.
I find it pretty funny when companies pay good money to "search engine
submission" services. This is not the way to advertise, and using a search
engine is quite an ineffective way, IMHO, to find answers about technical
problems. Google is about the only one that does things right, and I find
it much more valuable to use it for searching the groups than the web.
Let's face it, when you find something on a web site like mine, you're
almost guaranteed the information is going to be biased to some degree.
You're also likely to find some potentially misleading information, or just
plain bad advice. When you look at conversations, at least you can be sure
to have a minimum of two inputs (comments about single posts with no replies
to dev/null, thanks).
As with most subjective topics, YMMV.
