Friday, April 13th, 2007

Scriptless Day: July 7th 2007

Category: Fun

Nater Kane pointed us to Scriptless Day, the Web 3.0 CSS Naked Day.

Some have found it ironic that the default banners for Scriptless Day are JavaScript banners, but they responded:

We have been catching a lot of heat lately on our decision to use JavaScript in our Badge to promote Scriptless Day!

However, we see it fit to use JavaScript to promote Scriptless Day because the overall point of SD is to illustrate the importance of Client-Side JavaScript on several popular “Web 2.0” websites. The fact that we chose to use JavaScript only reinforces our positive attitude towards it.

I can’t wait to see HTMLless Day next year.

Posted by Dion Almaer at 6:46 am

2.6 rating from 45 votes


Comments feed TrackBack URI

Why? at least the scriptlessday website should have come up with a reason to do this. I don’t see why people will time updating their websites for no reason. Client-Side scripts are great!!

I’m going to create a website called ‘webpagelessday’ and request that webmasters remove all webpages from their sites. I’m sure that’ll be popular!

Comment by stuart — April 13, 2007

Ahh, ok so the point it ‘…because the overall point of SD is to illustrate the importance of Client-Side JavaScript on several popular’
That makes total sense now, not.

Comment by stuart — April 13, 2007

client-side scripting is something that we all (here) know and love…. however I do believe the point is to make sure that your site’s can run and be presented in a reasonable manner without the use of javascript… and that you use javascript in a responsible manner.
but hey, if you don’t get it, you don’t get it.

Comment by naterkane — April 13, 2007

The client side script on the site is awful, the links send you all over the place.

The worst thing about it is that Nater Kane cites progressive enhancement (and no doubt graceful degradation) as reasons for the day. Even though the site breaks in Opera and the anchors all link to ‘#’. So the site breaks all non javascript browsers and at least one browser that is javascript enabled.

I love client script, but after seeing that site I may never touch it again :)

Comment by Richard Kimber — April 13, 2007

I might have misunderstood, is the site supposed to be ironic?

If so, I apologise. Great job.

Comment by Richard Kimber — April 13, 2007

Richard, I have nothing directly to do with the folks behind Scriptless Day, and I also was not involved with the development of their site. Yes I’m aware that their site does not work with javascript turned off… and yes, I laughed at that ironic fact. However, I’m just taking their idea as an opportunity to ensure that all of my personal and my agency’s current development work doesn’t break with any added javascript removed (currently nothing will break, btw)

Comment by naterkane — April 13, 2007

Sorry, my comments weren’t aimed at you Nater. I agree and respect the reasons you gave in your post. I would just suggest that Scriptless Day is not the best way of illistrating them.

Comment by Richard Kimber — April 13, 2007

Thought this was a joke, really think that this is stupid. I am so annoyed with people demanding rich applications and then telling us to make it degrade! I mean, are people still like my boss at the old job saying “It has to be the same in IE mac”?

When you are a one man web team trying to keep up with the technologies, sometimes you say “forget the people who have js off” because to give rich features that 90% of people will love, you decide… “Hey, if you don’t want to turn on js then just don’t use our site!”. Do all your sites with flash “degrade nicely” when the user has flash turned off? Try to use the adobe site with flash turned off… can you use the exchange? No.

Ok, just tired of everyone being so idealistic when the reality is if you are a developer trying to keep up with the demands of your boss and site users, then maybe “degrading” ain’t so important after all.

Ever thought of it that way???

Comment by Chad — April 13, 2007

Its getting to the point where developing a rich JS enabled site to degrade nicely is just a ridiculous as asking GM or Ford to make sure their next model has the option to hookup a horse in case I don’t want to use gasoline anymore.

Comment by Sean Foushee — April 13, 2007


Thank you for your interest in Scriptless Day. We want to assure all of you that we will have a fully-functional site without JavaScript come July 7th. But that really isn’t the focus here. Our site was just meant to promote the idea of a Day with no client-side scripts, not to serve as a poster-child for Validated Markup & Degradable JS.

Sometimes you just need to go a day without something to realize how much you value it.

Thank you all for your interest and comments.

Kind Regards.

Comment by Scriptless Day — April 13, 2007

The best part is providing a piece of code to copy and paste on your site with some javascript and a document.write() function.

Comment by skateinmars — April 13, 2007

That is the dumbest thing I have ever heard of in my life.

Comment by Jesse — April 13, 2007

Why do we need to stop using something to “value” it?

I already value scripting enough to be writing web-apps that are heavily dependent on it.

So… I cripple my app for a day, realise it was really dumb to do.. then what? I’m supposed to learn something from it??

Comment by Tim Leonard — April 13, 2007

I’ve got a bottle of Midol if any of you guys need some.

Comment by Jordan — April 13, 2007

none of you guys seem to get the point. oh well.

Comment by naterkane — April 14, 2007

So, what’s the point, then?

Looks like just another group that’s trying to get some free advertising by promoting a non-event.

Comment by James — April 15, 2007

I wish the site would work better. As it is now, it is a good display of how NOT to make a site. Why not make real links to real pages? I’m not even going to say something about the irony of your goal vs. your site.

Comment by Teun — April 16, 2007

I agree with naderkane.. none of you guys are catching the point. A site should still be functional without all of the javascript. Preferably 100% functional, but at least the main parts should work.

As noted, links should point to where they’re going – not #, dynamicaly loaded content should have some way of being accessed besides dynamic loading, things that update in the background should also be able to update via clicking a link, etc.

Besides still having a working website when joe blow’s browser plugin breaks your javascript (I’ve seen a spell checker kill some javascript once), it’ll also get better search engine rankings and be more likely to meet accessibility standards.

Comment by Nathan Friedly — April 16, 2007

Leave a comment

You must be logged in to post a comment.