Text 11800, 127 rader
Skriven 2006-06-26 16:46:20 av /m (1:379/45)
  Kommentar till text 11774 av Geo (1:379/45)
Ärende: Re: PCI hardware ID
===========================
From: /m <mike@barkto.com>


Microsoft wouldn't do that because then IE would not always work.  Far too many
websites rely on IE to be in an insecure configuration in order for the website
to work at all.

 /m


On Fri, 23 Jun 2006 21:18:37 -0400, "Geo" <georger@nls.net> wrote:

>It's really simple to do, you just put a "strict" meter on IE so that users
can set it to very strict, pretty strict, somewhat strict, fuckit make it work.
And then set pretty strict as the default. Now let the websites explain to
users they have to set it to the fuckit setting.
>
>Geo.
>  "Rich" <@> wrote in message news:449993de@w3.nls.net...
>     Users can't see why something doesn't work but do see that it doesn't.
If you want clients to enforce the types returned by the sittes you should
start by getting sites to return correct info.  You could do this on your own.
Write or grab a crawler and start crawling the internet.  Send email to the
webmasters for any sites with mistakes.  Good luck.
>
>  Rich
>
>    "Geo" <georger@nls.net> wrote in message news:449764b9@w3.nls.net...
>    Rich,
>
>    I didn't say there weren't a dozen different excuses for why things are
the way they are now.  I just think it's wrong to perpetuate the mistakes by
supporting what is obviously the wrong way to do things. Look at how much lame
hardware NT cleaned up. That's because it didn't allow the level of "cheating"
that DOS and Win9x did, it enforced the rules better and we are better off now.
>
>    Same thing should happen with all the other cases where past mistakes have
created a situation that the computer must guess. Break the damn websites that
aren't working right, enforce strict file types for text files. Stop accepting
the excuses that it MUST guess to be compatible and enforce some rules.
>
>    Things have a habit of getting real complicated all by themselves, we
don't need to be helping confusion get a grip on our computer environments.
Just because some programmer decided he CAN divide by zero doesn't mean every
programmer should now support that till the end of time.
>
>    Geo.
>      "Rich" <@> wrote in message news:449720d7@w3.nls.net...
>         Two different issues.  IE has to apply heuristics to file types
because the servers that return this content often return bogus, both incorrect
or invalid, types.  It's not easy to fix.  IE had to do this because netscape
didn't enforce types and to be compatible IE couldn't either.  Because the
types aren't enforced lots of servers still do this wrong.  Because they do
types can't be enforced.
>
>         Text and Unicode is first a false distinction.  It's all text.  In
the case of Notepad, you mean UTF-16 text vs. UTF-8 text vs. ANSI text as this
is the distinction that Notepad makes on load.  Even that misses the complexity
as what people call ANSI is actually any of 14 distinct and incompatible ANSI
encodings and is often one of many OEM encodings which may be distinct from any
of the ANSI ones.  It is complicated because for many of the ANSI encodings
including the one used in the U.S. and Western Europe, anything could be valid.
Because of this it is not always possible to make a distinction between UTF-16
and ANSI as a file could validly be either.  UTF-8 is restrictive so it is easy
to tell if something is valid UTF-8.  That could still be a problem as valid
UTF-8 could be valid ANSI too.  Instead some heuristics are applied.  For
example if you see 0D 00 0A 00 then the file is probably UTF-16 while if you
see 0D 0A it may be ANSI though U+0A0D might be a valid
>Unicode character.  I didn't look.
>
>      Rich
>
>        "Geo" <georger@nls.net> wrote in message news:449444fd$2@w3.nls.net...
>        That's not what I meant when I said computers today guess. I meant how
>        computers today guess at the answer when the problem doesn't have a
unique
>        solution. Example would be how IE guesses file types or how notepad
guesses
>        between text and unicode.
>
>        Geo.
>
>        "Antti Kurenniemi" <NOantti@SPAManttikPLEASE.com> wrote in message
>        news:449392b8$1@w3.nls.net...
>        > It was equally bad having people guess things. "I'll switch this dip
here
>        > and that there, and then those jumpers that I just dropped and have
no
>        clue
>        > about where they should go... I'll just make a neat row of them
here,
>        > that'll do it". I remember a lot of hardware having huge manuals for
just
>        > configuring the stupid dip switches and whatnots, and that it was
possible
>        > to fry things by misconfiguring them. No thanks to that - nowadays,
at
>        least
>        > you don't have to get your hands dirty to break your computer <g>
>        >
>        >
>        > Antti Kurenniemi
>        >
>        > "Geo" <georger@nls.net> wrote in message
news:44938e6a$2@w3.nls.net...
>        > I kind of prefer the days when computers didn't "guess" at things.
We used
>        > to have a saying "computers don't make mistakes" but all that
changed
>        now..
>        >
>        > Geo.
>        >   "Rich" <@> wrote in message news:4493558b$1@w3.nls.net...
>        >      You don't expect a mainframe to automatically detect any off
the
>        shelf
>        > adapter that is plugged in.  The PC could go back to the dark ages
too as
>        > this is how things used to be when the PC first came to be.
>        >
>        >   Rich
>        >
>        >
>        >

--- BBBS/NT v4.01 Flag-5
 * Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)