{"id":636,"date":"2009-07-05T13:07:56","date_gmt":"2009-07-05T17:07:56","guid":{"rendered":"http:\/\/blog.jedbrubaker.com\/?p=636"},"modified":"2009-07-05T01:50:21","modified_gmt":"2009-07-05T05:50:21","slug":"javascript-and-dead-frogs","status":"publish","type":"post","link":"https:\/\/www.whatknows.com\/blog\/2009\/07\/05\/javascript-and-dead-frogs\/","title":{"rendered":"JavaScript and Dead Frogs"},"content":{"rendered":"<p><a href=\"http:\/\/www.flickr.com\/photos\/36073601@N00\/55605114\"><img decoding=\"async\" class=\"alignright\" title=\"A frog on my Camera Bag\" src=\"http:\/\/farm1.static.flickr.com\/32\/55605114_16a77dbee6_m.jpg\" border=\"0\" alt=\"A frog on my Camera Bag\" hspace=\"5\" \/><\/a>There is a debate at work right now. Granted, it is a bit ideological, but it is one of those classic web developer debates we feel compelled to return to every couple of years:<\/p>\n<p>Should we expect our users to have JavaScript enabled?<\/p>\n<p>Perhaps more importantly, what should we do when they don&#8217;t?<\/p>\n<p>Ever since Google Maps ripped open the possibilities of web-based development (with turn-by-turn directions no less), we have been stuck with this bizarre requirement: JavaScript. Sure, it makes the web go round, but I still have nightmares of trying to get the University of Utah labs to upgrade to Flash v7, and our web analytics show a stunningly high level of Netscape v4.<\/p>\n<p><!--more Frogs at risk after the jump... -->Right now I am building a fancy fan-dangled address widget for the Association (as fancy as an address widget can be), but through this process am also authoring\/encoding into existence a fairly large number of front-end standards for our new Java\/Spring architecture. Of course we are required to have some &#8220;lo-fi&#8221; version of what ever Dojo-steroided-monster I create, but when I ask my peers what possible message I could place between some &lt;noscript&gt; tags, they typically respond with a string of expletives.<\/p>\n<p>Leave it to my colleague Patrick to find the perfect solution: A gentle message from <a href=\"http:\/\/mibbit.com\/\" target=\"_blank\">mibbit<\/a> that gets right to the point.<\/p>\n<p style=\"text-align: center;\"><a href=\"http:\/\/blog.jedbrubaker.com\/wp-content\/uploads\/2009\/07\/nojskillsfrogs.png\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-638 aligncenter\" style=\"border: 0pt none; margin: 0px;\" title=\"Disabled JavaScript Kills Frogs\" src=\"http:\/\/blog.jedbrubaker.com\/wp-content\/uploads\/2009\/07\/nojskillsfrogs.png\" alt=\"Why do you hate the web? Why do you hate frogs? Turn on your Javascript.\" width=\"448\" height=\"176\" srcset=\"https:\/\/www.whatknows.com\/blog\/wp-content\/uploads\/2009\/07\/nojskillsfrogs.png 567w, https:\/\/www.whatknows.com\/blog\/wp-content\/uploads\/2009\/07\/nojskillsfrogs-300x117.png 300w\" sizes=\"auto, (max-width: 448px) 100vw, 448px\" \/><\/a><\/p>\n<p style=\"text-align: left;\">I kid you not. They are that awesome. I would tell you to go check it out yourself, but you would have to disable your JavaScript to see the message and I don&#8217;t want to be responsible for any more frogs. Consider this a public service.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There is a debate at work right now. Granted, it is a bit ideological, but it is one of those classic web developer debates we feel compelled to return to every couple of years: Should we expect our users to have JavaScript enabled? Perhaps more importantly, what should we do when they don&#8217;t? Ever since [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[6],"tags":[47,63,49,59,58,45,46,54,62,55,56,53,48,32,51,60,61,52,64,44,57,43,50],"class_list":["post-636","post","type-post","status-publish","format-standard","hentry","category-technology","tag-address","tag-address-widget","tag-bit","tag-classic-web","tag-colleage","tag-debate","tag-developer","tag-fancy-fan","tag-frogs","tag-gentle-message","tag-google","tag-google-maps","tag-granted","tag-javascript","tag-message","tag-new-java","tag-noscript","tag-patrick","tag-perfect-solution","tag-web","tag-web-based-development","tag-widget","tag-work"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pJP4m-ag","_links":{"self":[{"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/posts\/636","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/comments?post=636"}],"version-history":[{"count":12,"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/posts\/636\/revisions"}],"predecessor-version":[{"id":646,"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/posts\/636\/revisions\/646"}],"wp:attachment":[{"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/media?parent=636"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/categories?post=636"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.whatknows.com\/blog\/wp-json\/wp\/v2\/tags?post=636"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}