4 ms·

For those of you who didn't get it (I had to google what w3m was), his point is that the site context is all rendered by JS, without any fallback static text co

For those of you who didn't get it (I had to google what w3m was), his point is that the site context is all rendered by JS, without any fallback static text content. Besides the obvious accessibility issues, it's also not good for SEO.

lhorie 13y ago
If you rely on SEO to get work as a software engineer, you're probably doing it wrong. Know your target audience, yadayada. Just sayin' :)
- PavlovsCat 13y ago
  If you make a website solely to advertise yourself, and not also to make cool stuff you made or found or said accessible to the people who might be looking for it, you may not be doing it wrong, but you are still missing out a bit :) Not that I have any beef with javascript only stuff or this site, the web is big enough for everything - please don't read my comment as complaining in any shape or form, really. I just want to say that successfully targeting an audience is nice, but people finding stuff at your site(s) you couldn't possibly have imagined they'd be looking for is also nice, and if you go the javascript only route, you might never find out. Just as a general point that doesn't really have anything to do with the site at hand.
nick2021 13y ago
Correction, a software engineer from the 80's who never progressed with technology website.
coldtea 13y ago
Actually it's damn fine for SEO. Google, the only SE that matters, handles Javascript only websites just fine (actually uses a full browser as the google crawler bot). I'd make a bet that Bing does too. And most accessibility software works with Javascript sites too, as they use the full DOM and can even handle events. It needs a little care to show changes to content and such, but they definitely don't need static fallback to read a site. The rest is old wives tales.