My Scriptless Day : July 7th … aye or nay?

FireBugScriptless day (July 7th) is an attempt to go in the footsteps of CSS Naked Day. But take a closer look at this before jumping on the bandwagon … at least one can expect their site to validate (68 errors aye?) and above all “just work” (TM) when Javascript is disabled, not? And where can one leave his comment? Nice try, but I say nay!

Published by Bramus!

Bramus is a frontend web developer from Belgium, working as a Chrome Developer Relations Engineer at Google. From the moment he discovered view-source at the age of 14 (way back in 1997), he fell in love with the web and has been tinkering with it ever since (more …)

Join the Conversation


  1. goosh! goosh!.. oh noes!

    I think it’s a great idea actually. It’s losers like you who can’t have any fun because some mystical being has coerced you into believing a website sucks if it doesn’t validate. Grows some balls.

  2. Btw.. I know you are going to edit this comment out… but your website doesn’t validate in realm of relevance… You aren’t even ranked in the top 100k sites of Alexa. You are a failure, you have false hopes, you will never succeed.

  3. Marcus, thank you for your nice comments!

    I’m not one of those that thinks a website sucks if it doesn’t validate (although it’s a nice extra!), but when seeing a tiny onepage site like (and when taking a peek at the source code) it’s no real biggie to fix those errors.

    I myself don’t give my support on the project as I think that if a scriptless day should be organized, it should be to promote the graceful degradation of the used scripts; Just like CSS Naked Day is organized to promote the correct usage of CSS along with a clean, good structural markup (viz. a readable site if CSS is disabled/stripped).

    In my opinion the site totally misses it’s purpose as it doesn’t give the right message. If the site would be to promote the purpose, it should degrade gracefully and provide non-javascript enabled browsers a working site! Right now the site simply “breaks” when JavaScript is disabled. You can’t see any text as the links point to nowhere (they all link to #) and make content visible (or hide content).

    BTW: Calling me names for me expressing my opinion on a subject really is the thing to do! (Should I now increase the Airbag Blog Advisory System Level? :-P). And what’s the relation between not appearing in the top100k and being a failure? If you so seem to get off on the top 100k thing, I’m 900.000 places higher than scriptlessday. Blah!

  4. i know its probably the right thing to do to answer shitbags like markus in such a swell and modest way like you just did, and i totally agree with you bram, not because we are friends, but because you are right. don’t start a thing about code with code that sucks.

    and markus, you fuckstain, go fucking fuck yourself you fucking idiot fucktard. superfucking, fuck fuck fuck!

    btw, they are now down to 33 errors 😀

  5. I think this goes without without qeustion, nor the need for an explanation. My answer is “Nay.” Take one look at the website. No really, take a long look up and down. Read it. What is the real goal and intention of this scriptless day website. That being said, I don’t think there’s a need for an explanation. The website does a good job explaining itself, it’s almost comical.

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.