X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9583E3A4987 for ; Thu, 4 Nov 2004 23:22:32 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 65725-06 for ; Thu, 4 Nov 2004 23:22:21 +0000 (GMT) Received: from bayswater1.ymogen.net (host-154-240-27-217.pobox.net.uk [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id 6F5BE3A4983 for ; Thu, 4 Nov 2004 23:22:23 +0000 (GMT) Received: from [82.68.132.233] (82-68-132-233.dsl.in-addr.zen.co.uk [82.68.132.233]) by bayswater1.ymogen.net (Postfix) with ESMTP id F0E68A33CB; Thu, 4 Nov 2004 23:22:22 +0000 (GMT) Message-ID: <418AB9AE.1010009@ymogen.net> Date: Thu, 04 Nov 2004 23:22:22 +0000 From: Matt Clark User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruno Wolff III Cc: =?ISO-8859-1?Q?Pierre-Fr=E9d=E9ric_Caillaud?= , pgsql-performance@postgresql.org Subject: Re: Restricting Postgres References: <003301c4c29a$f052d910$8300a8c0@solent> <418A98C0.9010107@ymogen.net> <418AAF12.8030307@ymogen.net> <20041104231429.GA15541@wolff.to> In-Reply-To: <20041104231429.GA15541@wolff.to> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200411/75 X-Sequence-Number: 9029 >Javascript is too powerful to turn for any random web page. It is only >essential for web pages because people write their web pages to only >work with javascript. > > Hmm... I respectfully disagree. It is so powerful that it is impossible to ignore when implementing a sophisticated app. And it is not dangerous to the user so long as they have a popup blocker. Commercially, I can ignore the people who turn it off, and I can gain a huge benefit from knowing that 95% of people have it turned on, because it gives my users a hugely better experience than the equivalent XHTML only page (which I deliver, and which works, but which is a fairly depressing experience compared to the JS enabled version). It is _amazing_ how much crud you can take out of a page if you let JS do the dynamic stuff (with CSS still in full control of the styling). Nice, clean, semantically sensible XHTML, that can be transformed for multiple devices - it's great. An example: /previews/foo.wmv But we want it to appear in a popup when viewed in certain devices.... Easy - Attach an 'onclick' event handler (or just set the target attribute) when the device has a suitable screen & media player, but leave the markup clean for the rest of the world.