Hacker News new | ask | show | jobs
by airencracken 3669 days ago
If I have to enable javascript to view parts of your website at all, then it isn't anything like 1999.
2 comments

To edit a blog you have to enable JavaScript because the blogging software is written in JS.

It would be possible to create a client that didn't, but that doesn't exist today.

> To edit a blog you have to enable JavaScript because the blogging software is written in JS.

> It would be possible to create a client that didn't, but that doesn't exist today.

I think the client exists: it's a web browser using forms. Not as nice as what we all expected we would have by now back in the 90s, but it works. A blog entry's just a title and some text. Throw in an input field for the title, and a textarea for some Markdown and baby you've got a blog!

You have to enable JavaScript (from fargo.io) to view posts (or at least to view the About page.)
The About page should NOT have required JS. That was a mistake. I'm going to fix it, but not tonight.

Here's an example of a blog post written in 1999.io.

http://scripting.com/2016/06/08/1311.html

You do NOT need JS on to read it, by design.

I feel like a lot of people are harshing on the fact that this is not like, I dunno, geocities or something, but I just want to express some appreciation that an effort is made for those of us who do not want to execute arbitrary code just to read a blog entry.

One note - on that page, it seems that while the content is there independent of Javascript, the navigation is loaded (from three different domains) with Javascript. I suspect there's a more graceful way to fallback there.

> If I have to enable javascript to view parts of your website at all, then it isn't anything like 1999.

JS is older than that, and early uses of it were notorious for not having graceful fallbacks, so, no, I think that description is not at all unlike 1999.

We need the little text+logos at the bottom of the page telling us which browsers we can expect it to work on.