On Sat 24 Oct 2009 at 12:35:36 PDT Uriel wrote:
>writing an http client that will handle all the crap out there is
>*really* hard
Why is this the goal?
Why, when I want to browse a sane website like suckless.org, for
example, should I have to use a browser containing a bunch of convoluted
code designed to handle the kind of "crap" you mean? I'd like to be
able to use a browser that, because it's only intended for use with
non-crappy sites, can be written in a way that's simpler, less buggy and
more secure.
If I'm browsing a suckless webpage in a suckless browser and click a
link to a page that sucks, perhaps the right thing to do is to open that
page in an external browser (which probably also sucks)?
Couldn't we have something like mime types for websites, reflecting
their use (or non-use) of various "crap" and associating them with
appropriately-written browsers?
Received on Sat Oct 24 2009 - 22:01:35 UTC
This archive was generated by hypermail 2.2.0 : Sat Oct 24 2009 - 22:12:02 UTC