• Another EV goes haywire!

    From Cursitor Doom@21:1/5 to All on Fri Oct 6 14:12:20 2023
    Ban them!

    https://tinyurl.com/2cjun8v7

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to Cursitor Doom on Fri Oct 6 06:52:54 2023
    On Saturday, October 7, 2023 at 12:12:31 AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.

    Taking out the ignition key usually seems to work when my ( internal combustion-engined) car decides to turn it's cruise control on. One has to wonder why the driver didn't try it.

    Perhaps Cursitor Doom hasn't had to cope with a modern car yet. Mine is about ten years old, so it isn't all that modern, but it did come with all kinds of programmed bells and whistles

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred Bloggs@21:1/5 to Cursitor Doom on Fri Oct 6 07:16:48 2023
    On Friday, October 6, 2023 at 9:12:31 AM UTC-4, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    If it was an ICE, it would have ran him up to 80 MPH minimum. He's lucky the EV settled on 15. People can get killed at 15 MPH. That's over 20 fps which is quite an impact upon abrupt collision stop.

    See 'unintended acceleration toyota' .

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred Bloggs@21:1/5 to Anthony William Sloman on Fri Oct 6 07:25:48 2023
    On Friday, October 6, 2023 at 9:52:59 AM UTC-4, Anthony William Sloman wrote:
    On Saturday, October 7, 2023 at 12:12:31 AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.

    Taking out the ignition key usually seems to work when my ( internal combustion-engined) car decides to turn it's cruise control on.

    Another woman-designed subsystem...


    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Clive Arthur@21:1/5 to Anthony William Sloman on Fri Oct 6 16:00:20 2023
    On 06/10/2023 14:52, Anthony William Sloman wrote:
    On Saturday, October 7, 2023 at 12:12:31 AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.

    He like the attention, that's all.

    Taking out the ignition key usually seems to work when my ( internal combustion-engined) car decides to turn it's cruise control on. One has to wonder why the driver didn't try it.

    On many (most?) cars, that would lock the steering.

    Perhaps Cursitor Doom hasn't had to cope with a modern car yet. Mine is about ten years old, so it isn't all that modern, but it did come with all kinds of programmed bells and whistles

    Mines coming up to 20 years old. The central locking hasn't worked for
    years and one door won't lock at all. The dashboard display sometimes spontaneously starts using German, and the rear wiper has a mind of its
    own. It's a Citroen, of course.

    --
    Cheers
    Clive

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Larkin@21:1/5 to All on Fri Oct 6 08:12:32 2023
    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <cd@notformail.com>
    wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my
    apartment in San Francisco, across the Golden Gate Bridge, with no
    clutch.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Larkin@21:1/5 to bloggs.fredbloggs.fred@gmail.com on Fri Oct 6 08:15:11 2023
    On Fri, 6 Oct 2023 07:25:48 -0700 (PDT), Fred Bloggs <bloggs.fredbloggs.fred@gmail.com> wrote:

    On Friday, October 6, 2023 at 9:52:59?AM UTC-4, Anthony William Sloman wrote: >> On Saturday, October 7, 2023 at 12:12:31?AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.

    Taking out the ignition key usually seems to work when my ( internal combustion-engined) car decides to turn it's cruise control on.

    Another woman-designed subsystem...


    --
    Bill Sloman, Sydney

    More likely "programmer designed."

    The programmers that I know, mostly male, can type way faster than
    they can think.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Fred Bloggs on Fri Oct 6 16:03:14 2023
    XPost: free.spam

    The arsehole Fred Bloggs <bloggs.fredbloggs.fred@gmail.com> persisting in being an Off-topic troll...

    --
    Fred Bloggs <bloggs.fredbloggs.fred@gmail.com> wrote:

    X-Received: by 2002:a05:620a:8d10:b0:773:f669:bc26 with SMTP id rb16-20020a05620a8d1000b00773f669bc26mr100483qkn.11.1696602349758;
    Fri, 06 Oct 2023 07:25:49 -0700 (PDT)
    X-Received: by 2002:a05:6830:84a:b0:6bc:ce86:20bd with SMTP id
    g10-20020a056830084a00b006bcce8620bdmr2310094ott.7.1696602349302; Fri, 06 Oct
    2023 07:25:49 -0700 (PDT)
    Path: not-for-mail
    Newsgroups: sci.electronics.design
    Date: Fri, 6 Oct 2023 07:25:48 -0700 (PDT)
    In-Reply-To: <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com> Injection-Info: google-groups.googlegroups.com; posting-host=2601:5cc:4701:5250:d9b8:a94e:6bd5:f27;
    posting-account=iGtwSwoAAABNNwPORfvAs6OM4AR9GRHt
    NNTP-Posting-Host: 2601:5cc:4701:5250:d9b8:a94e:6bd5:f27
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <492c43ea-3a3b-41c5-b963-70ecb1558e63n@googlegroups.com>
    Subject: Re: Another EV goes haywire!
    From: Fred Bloggs <bloggs.fredbloggs.fred@gmail.com>
    Injection-Date: Fri, 06 Oct 2023 14:25:49 +0000
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable
    X-Received-Bytes: 2031

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Cursitor Doom on Fri Oct 6 16:03:32 2023
    XPost: free.spam

    The idiot Cursitor Doom <cd@notformail.com> persisting in being an Off-topic troll...

    --
    Cursitor Doom <cd@notformail.com> wrote:

    Path: not-for-mail
    From: Cursitor Doom <cd@notformail.com>
    Newsgroups: sci.electronics.design
    Subject: Another EV goes haywire!
    Date: Fri, 06 Oct 2023 14:12:20 +0100
    Organization: A noiseless patient Spider
    Lines: 3
    Message-ID: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Injection-Info: dont-email.me; posting-host="ab8e02080b2374a6e165f66e58e74c60";
    logging-data="1646928"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX181BiTaZAYvoiuoY59X03eN7xW5LBGdUfg="
    User-Agent: ForteAgent/8.00.32.1272
    Cancel-Lock: sha1:SemJ5Gw0w+101XqNQoDESy6gbD8=
    X-Received-Bytes: 918

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to John Larkin on Fri Oct 6 16:03:40 2023
    XPost: free.spam

    The idiot John Larkin <jl@997arbor.com> persisting in being an Off-topic troll...

    --
    John Larkin <jl@997arbor.com> wrote:

    Path: not-for-mail
    NNTP-Posting-Date: Fri, 06 Oct 2023 15:15:19 +0000
    From: John Larkin <jl@997arbor.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Fri, 06 Oct 2023 08:15:11 -0700
    Message-ID: <h090ii58b0arigrj4s45bq9pgfv8qhsso0@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com> <492c43ea-3a3b-41c5-b963-70ecb1558e63n@googlegroups.com>
    X-Newsreader: Forte Agent 3.1/32.783
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Lines: 24
    X-Trace: sv3-qr40LQ8ihH+yT+ZGP6nwMw+zytg7PLV1g0VLgIrklry9GkCUtUj3UI2FbzHXdedNkRzB6POWAc6Xxmj!P4SN2u3VBugVHbHSrf9q5TTxuo+6DntD56ly1ykdD6blhH8rp7ehdf5CLvvRjCl61ZtqruHgV40H!NRU/pA==
    X-Complaints-To: www.supernews.com/docs/abuse.html
    X-DMCA-Complaints-To: www.supernews.com/docs/dmca.html
    X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
    X-Postfilter: 1.3.40
    Bytes: 2000
    X-Received-Bytes: 2200

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Clive Arthur on Fri Oct 6 16:03:46 2023
    XPost: free.spam

    The idiot Clive Arthur <clive@nowaytoday.co.uk> persisting in being an Off-topic troll...

    --
    Clive Arthur <clive@nowaytoday.co.uk> wrote:

    Path: not-for-mail
    From: Clive Arthur <clive@nowaytoday.co.uk>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Fri, 6 Oct 2023 16:00:20 +0100
    Organization: A noiseless patient Spider
    Lines: 25
    Message-ID: <ufp7e5$1jbn0$1@dont-email.me>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    Reply-To: clive@nowaytoday.co.uk
    MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit
    Injection-Date: Fri, 6 Oct 2023 15:00:22 -0000 (UTC)
    Injection-Info: dont-email.me; posting-host="5f03efb55c0f4675d65fc4bab41aca9b"; logging-data="1683168"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/9LNaCMz/GoDosY0e4cWZfKAiMr+hhTy8="
    User-Agent: Mozilla Thunderbird
    Cancel-Lock: sha1:JBmomb38KBnszd44+zS3gZau9PQ=
    Content-Language: en-GB
    In-Reply-To: <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com> X-Received-Bytes: 2258

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cursitor Doom@21:1/5 to All on Fri Oct 6 18:00:19 2023
    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <jl@997arbor.com>
    wrote:

    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <cd@notformail.com>
    wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my
    apartment in San Francisco, across the Golden Gate Bridge, with no
    clutch.

    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained
    regularly. Perhaps it's harder to get the proper spares for them in
    the US.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cursitor Doom@21:1/5 to bill.sloman@ieee.org on Fri Oct 6 18:01:52 2023
    On Fri, 6 Oct 2023 06:52:54 -0700 (PDT), Anthony William Sloman <bill.sloman@ieee.org> wrote:

    On Saturday, October 7, 2023 at 12:12:31?AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.

    Taking out the ignition key usually seems to work when my ( internal combustion-engined) car decides to turn it's cruise control on. One has to wonder why the driver didn't try it.

    Perhaps Cursitor Doom hasn't had to cope with a modern car yet. Mine is about ten years old, so it isn't all that modern, but it did come with all kinds of programmed bells and whistles

    My ICE car won't allow me to take the key out whilst it's in motion,
    Bill, and it's 20 years old. This is nothing new. Your car must be a
    bit like you: peculiar.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cursitor Doom@21:1/5 to bill.sloman@ieee.org on Fri Oct 6 18:12:23 2023
    On Fri, 6 Oct 2023 06:52:54 -0700 (PDT), Anthony William Sloman <bill.sloman@ieee.org> wrote:

    On Saturday, October 7, 2023 at 12:12:31?AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.

    Perhaps not, but when they do go wrong, the results can be
    catestrophic because of the huge amount of energy in the battery. It's
    curious how Teslas have the propensity to burst into flame then lock
    all the doors. I suppose that *could* somehow happen with an ICE car,
    but I've never heard of such an incident involving one. And the
    charging infrastructure just isn't there. EV sales as a proportion of
    overall car sales are falling now in the UK and Europe because of all
    sorts of mounting concerns. I personally would give EVs another 10
    years, so all the issues surrounding them can be ironed out. I for one certainly won't be wasting my money on one any time soon and by the
    time I am I'll probably be to old to safely get behind a wheel anyway.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Cursitor Doom on Fri Oct 6 17:53:50 2023
    XPost: free.spam

    The idiot Cursitor Doom <cd@notformail.com> persisting in being an Off-topic troll...

    --
    Cursitor Doom <cd@notformail.com> wrote:

    Path: not-for-mail
    From: Cursitor Doom <cd@notformail.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Fri, 06 Oct 2023 18:01:52 +0100
    Organization: A noiseless patient Spider
    Lines: 17
    Message-ID: <j9f0ii9det62bkqf4spuojqnruvem8r617@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Injection-Info: dont-email.me; posting-host="ab8e02080b2374a6e165f66e58e74c60";
    logging-data="1732831"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/saP2TrCLyEIWGpcN14/idcMTs167C5iI="
    User-Agent: ForteAgent/8.00.32.1272
    Cancel-Lock: sha1:ofAXmyJB5B8a1RyTGh+fhQDe9pc=
    X-Received-Bytes: 1862

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Larkin@21:1/5 to All on Fri Oct 6 10:53:42 2023
    On Fri, 06 Oct 2023 18:00:19 +0100, Cursitor Doom <cd@notformail.com>
    wrote:

    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <jl@997arbor.com>
    wrote:

    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <cd@notformail.com> >>wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my
    apartment in San Francisco, across the Golden Gate Bridge, with no
    clutch.

    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained
    regularly.

    Like weekly?

    I had a Sprite and a Midget, which were great fun and mechanically
    awful. All the fluids leaked, including rainwater from above. DGMS on
    Lucas electrics.

    Perhaps it's harder to get the proper spares for them in
    the US.

    I could get parts. Lots of them.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Cursitor Doom on Fri Oct 6 17:54:02 2023
    XPost: free.spam

    The arsehole Cursitor Doom <cd@notformail.com> persisting in being an Off-topic troll...

    --
    Cursitor Doom <cd@notformail.com> wrote:

    Path: not-for-mail
    From: Cursitor Doom <cd@notformail.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Fri, 06 Oct 2023 18:00:19 +0100
    Organization: A noiseless patient Spider
    Lines: 23
    Message-ID: <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <5m80iit7i02me0ebcd9atci7laijvr64pt@4ax.com>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Injection-Info: dont-email.me; posting-host="ab8e02080b2374a6e165f66e58e74c60"; logging-data="1732831"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/mstBWqKdnC1P36Ijyh9+JksLpgDP0AWE="
    User-Agent: ForteAgent/8.00.32.1272
    Cancel-Lock: sha1:uweT5xO2ARJwnFv0yUUrvBhYwIw=
    X-Received-Bytes: 1634

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Anthony William Sloman on Fri Oct 6 19:30:42 2023
    On 06/10/2023 14:52, Anthony William Sloman wrote:
    On Saturday, October 7, 2023 at 12:12:31 AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.

    Taking out the ignition key usually seems to work when my ( internal combustion-engined) car decides to turn it's cruise control on. One has to wonder why the driver didn't try it.

    Perhaps Cursitor Doom hasn't had to cope with a modern car yet. Mine is about ten years old, so it isn't all that modern, but it did come with all kinds of programmed bells and whistles

    I can't tell which URL the fuckwit Doom has pointed at, but this one
    does look like a massive software MFU. The police got him to throw his
    key fob out of the window and then do a hard reset by holding the
    ignition button in for 10s - the result was every indicator on the dash
    lit up. But the car kept on going. Unlike the usual foot on the wrong
    pedal game this one looks to be a car with software that was total crap
    (but then it was an MG so what do you expect?).

    They finally stopped it by running him into a soft matched speed
    collision with a police van and then applying their brakes.

    The car still tried to move forward but was constrained. They could only disable it by switching off the main supply and the repair man wasn't
    keen to do anything other than take it away on a trailer. The error
    messages in the log file ran into many pages. It is a pretty good
    example of why fly by wire isn't sensible in consumer grade items.

    I always insisted on having physical interlocks when I was in the firing
    line for high powered lasers. I don't trust electronics not to glitch
    and I certainly don't trust firmware or software!

    I do trust a big heavy physical beam stop with a huge heat sink
    especially when my padlock is locked on it and the key in my pocket.

    ISTR the US lost a very expensive stealth aircraft due to similar coding problems or an unspecified and classified malfunction fairly recently
    and had to appeal to the public to help find its wreckage.

    https://www.bbc.co.uk/news/world-us-canada-66841194

    Software is usually the cause of such malfunctions in high end kit.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joe Gwinn@21:1/5 to All on Fri Oct 6 14:27:43 2023
    On Fri, 06 Oct 2023 10:53:42 -0700, John Larkin <jl@997PotHill.com>
    wrote:

    On Fri, 06 Oct 2023 18:00:19 +0100, Cursitor Doom <cd@notformail.com>
    wrote:

    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <jl@997arbor.com>
    wrote:

    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <cd@notformail.com> >>>wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my
    apartment in San Francisco, across the Golden Gate Bridge, with no >>>clutch.

    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained
    regularly.

    Like weekly?

    Yeah. In the 1970s, I had a girlfriend with a MG Sprite. and she
    loved how it drove. I was always fixing something. Don't recall what
    happened to it. I think it was totaled, but not by her.


    I had a Sprite and a Midget, which were great fun and mechanically
    awful. All the fluids leaked, including rainwater from above. DGMS on
    Lucas electrics.

    Lucas, Prince of Darkness


    Perhaps it's harder to get the proper spares for them in
    the US.

    I could get parts. Lots of them.

    As could I. I recall the parts lady at the local British Cars dealer
    in Baltimore. She had perfect memory. You could roughly describe
    what you needed, and she would pause, then say that that's a
    <27-character part number>, run off into the back, and come out with
    the correct part. Every time.

    Joe Gwinn

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cursitor Doom@21:1/5 to All on Fri Oct 6 19:34:07 2023
    On Fri, 06 Oct 2023 10:53:42 -0700, John Larkin <jl@997PotHill.com>
    wrote:

    On Fri, 06 Oct 2023 18:00:19 +0100, Cursitor Doom <cd@notformail.com>
    wrote:

    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <jl@997arbor.com>
    wrote:

    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <cd@notformail.com> >>>wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my
    apartment in San Francisco, across the Golden Gate Bridge, with no >>>clutch.

    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained
    regularly.

    Like weekly?

    I had a Sprite and a Midget, which were great fun and mechanically
    awful. All the fluids leaked, including rainwater from above. DGMS on
    Lucas electrics.

    Perhaps it's harder to get the proper spares for them in
    the US.

    I could get parts. Lots of them.

    I think you'd have had a much, much better experience with a pre-1976*
    MG B or possibly a TF. The MGB roadster is highly-regarded. There were
    so many of them made they're easy to find for sensible prices and
    spares are plentiful. A TF is more pricey but a really classic sports
    car with wonderful styling.
    * pre '76 'cos after that they had those hideous rubber safety
    fenders. Get a chrome bumper model if you can.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Martin Brown on Fri Oct 6 13:33:34 2023
    On 10/6/2023 11:30 AM, Martin Brown wrote:
    ISTR the US lost a very expensive stealth aircraft due to similar coding problems or an unspecified and classified malfunction fairly recently and had to appeal to the public to help find its wreckage.

    https://www.bbc.co.uk/news/world-us-canada-66841194

    Software is usually the cause of such malfunctions in high end kit.

    And the cause of the software fault is often a sloppy specification.

    High end kit is often coded by large crews from meticulous specifications. Getting the specification right is considerably harder than coding
    the portions doled out to individual coders. *Noticing* flaws in
    a specification is also more difficult than noticing a bug in a
    reified module against its spec.

    [I've been given specs with obvious incompatibilities -- that the
    author hadn't seen just because he was too close to the problem
    and had too many baked in assumptions: "Here, imagine THIS happening..."]

    Sadly, no one teaches folks how to write (and challenge) good
    specifications (hardware, software, system). And, few folks have
    an interest in developing that skillset.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Don Y on Fri Oct 6 13:39:29 2023
    On 10/6/2023 1:33 PM, Don Y wrote:
    [I've been given specs with obvious incompatibilities -- that the
    author hadn't seen just because he was too close to the problem
    and had too many baked in assumptions:  "Here, imagine THIS happening..."]

    Sadly, no one teaches folks how to write (and challenge) good
    specifications (hardware, software, system).  And, few folks have
    an interest in developing that skillset.

    A colleague was designing a video scaler. And the design was almost
    ready to head off to the foundry! I pointed out that RS170 video
    scaled to a *smaller* image in the "enlarged" setting than in the
    "normal" setting. (WTF?)

    How did the design get that far along without anyone challenging
    it with real-life situations??

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Larkin@21:1/5 to All on Fri Oct 6 13:41:40 2023
    On Fri, 06 Oct 2023 14:27:43 -0400, Joe Gwinn <joegwinn@comcast.net>
    wrote:

    On Fri, 06 Oct 2023 10:53:42 -0700, John Larkin <jl@997PotHill.com>
    wrote:

    On Fri, 06 Oct 2023 18:00:19 +0100, Cursitor Doom <cd@notformail.com> >>wrote:

    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <jl@997arbor.com>
    wrote:

    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <cd@notformail.com> >>>>wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my >>>>apartment in San Francisco, across the Golden Gate Bridge, with no >>>>clutch.

    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained >>>regularly.

    Like weekly?

    Yeah. In the 1970s, I had a girlfriend with a MG Sprite. and she
    loved how it drove. I was always fixing something. Don't recall what >happened to it. I think it was totaled, but not by her.


    I had a Sprite and a Midget, which were great fun and mechanically
    awful. All the fluids leaked, including rainwater from above. DGMS on
    Lucas electrics.

    Lucas, Prince of Darkness


    Perhaps it's harder to get the proper spares for them in
    the US.

    I could get parts. Lots of them.

    As could I. I recall the parts lady at the local British Cars dealer
    in Baltimore. She had perfect memory. You could roughly describe
    what you needed, and she would pause, then say that that's a
    <27-character part number>, run off into the back, and come out with
    the correct part. Every time.

    Joe Gwinn

    When I moved from New Orleans to San Francisco I drive my Midget all
    the way. It started pulling to the right pretty hard and was getting
    worse. Turns out a stamped thing in the front suspension was tearing.
    Good thing I made it through the Grand Canyon; it's a long way down.

    I met my wife at a gay bar, Hamburger Mary's. She told me that she had
    a Midget that was running badly. We went outside and opened the hood.
    It was idling at 3000 RPM, so I whipped out my swiss army knife and
    cranked down the idle screw on the SU carb.

    "Women have no use for engineers except to marry them."


    I sold my Midget to an artist who painted the ocean on it.

    https://adrianruyle.com/3-d-art/art-cars/

    No seagulls. I insisted on no seagulls.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Larkin@21:1/5 to All on Fri Oct 6 13:46:55 2023
    On Fri, 06 Oct 2023 19:34:07 +0100, Cursitor Doom <cd@notformail.com>
    wrote:

    On Fri, 06 Oct 2023 10:53:42 -0700, John Larkin <jl@997PotHill.com>
    wrote:

    On Fri, 06 Oct 2023 18:00:19 +0100, Cursitor Doom <cd@notformail.com> >>wrote:

    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <jl@997arbor.com>
    wrote:

    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <cd@notformail.com> >>>>wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my >>>>apartment in San Francisco, across the Golden Gate Bridge, with no >>>>clutch.

    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained >>>regularly.

    Like weekly?

    I had a Sprite and a Midget, which were great fun and mechanically
    awful. All the fluids leaked, including rainwater from above. DGMS on
    Lucas electrics.

    Perhaps it's harder to get the proper spares for them in
    the US.

    I could get parts. Lots of them.

    I think you'd have had a much, much better experience with a pre-1976*
    MG B or possibly a TF. The MGB roadster is highly-regarded. There were
    so many of them made they're easy to find for sensible prices and
    spares are plentiful. A TF is more pricey but a really classic sports
    car with wonderful styling.
    * pre '76 'cos after that they had those hideous rubber safety
    fenders. Get a chrome bumper model if you can.

    The Midget was fun but not a good ski car.

    2wd and no place for skis and insane oversteer. Fun to spin if there
    were no trees nearby.

    We had to turn the heater off when it was really cold, or the engine
    would get too cold.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Martin Brown on Fri Oct 6 21:58:13 2023
    XPost: free.spam

    The idiot Martin Brown <'''newspam'''@nonad.co.uk> persisting in being an Off-topic troll...

    --
    Martin Brown <'''newspam'''@nonad.co.uk> wrote:

    Path: not-for-mail
    From: Martin Brown <'''newspam'''@nonad.co.uk>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Fri, 6 Oct 2023 19:30:42 +0100
    Organization: A noiseless patient Spider
    Lines: 47
    Message-ID: <ufpjoj$1rduc$1@dont-email.me>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit
    Injection-Date: Fri, 6 Oct 2023 18:30:43 -0000 (UTC)
    Injection-Info: dont-email.me; posting-host="10dbc6ca8e43b2d076aaab3b9e82f55b"; logging-data="1947596"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18wwyMWl1g1BbRdX13cTqfwukQEUMVC7ZqPW+HDFLmrTw=="
    User-Agent: Mozilla Thunderbird
    Cancel-Lock: sha1:sB/SzadtseV7V6+NddM4gYNRJN4=
    In-Reply-To: <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com> Content-Language: en-GB
    X-Received-Bytes: 3531

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Don Y on Fri Oct 6 21:58:19 2023
    XPost: free.spam

    The arsehole Don Y <blockedofcourse@foo.invalid> persisting in being an Off-topic troll...

    --
    Don Y <blockedofcourse@foo.invalid> wrote:

    Path: not-for-mail
    From: Don Y <blockedofcourse@foo.invalid>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Fri, 6 Oct 2023 13:33:34 -0700
    Organization: A noiseless patient Spider
    Lines: 25
    Message-ID: <ufpqv8$1so3a$3@dont-email.me>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com>
    <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    <ufpjoj$1rduc$1@dont-email.me>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit
    Injection-Date: Fri, 6 Oct 2023 20:33:45 -0000 (UTC)
    Injection-Info: dont-email.me; posting-host="c3a9d9e643a9f109e179ae15926080de";
    logging-data="1990762"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX184D0Z8z1UipPJ4/CahhHTh"
    User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101
    Thunderbird/102.2.2
    Cancel-Lock: sha1:2UIrqKQ4J6tNenzV8gKmNfVS8SM=
    Content-Language: en-US
    In-Reply-To: <ufpjoj$1rduc$1@dont-email.me>
    X-Received-Bytes: 2277

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to John Larkin on Fri Oct 6 21:58:45 2023
    XPost: free.spam

    The arsehole John Larkin <jl@997PotHill.com> persisting in being an Off-topic troll...

    --
    John Larkin <jl@997PotHill.com> wrote:

    Path: not-for-mail
    NNTP-Posting-Date: Fri, 06 Oct 2023 20:41:39 +0000
    From: John Larkin <jl@997PotHill.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Fri, 06 Oct 2023 13:41:40 -0700
    Organization: Highland Tech
    Reply-To: xx@yy.com
    Message-ID: <3oq0iitv1rgk3k6nbm6722trtveu8b1sko@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <5m80iit7i02me0ebcd9atci7laijvr64pt@4ax.com> <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com> <g5i0iid15j3c0pqms8ns2mheofcbrilmme@4ax.com> <arj0ii5hpmd7t0k48d710k5ci032co991u@4ax.com>
    X-Newsreader: Forte Agent 3.1/32.783
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Lines: 80
    X-Trace: sv3-JDgGN6wTDkEk4jul4ZcarBj4NTZA/qpkGN704U2L5wAc8eoxQLq8Rv7znFKpJC/BYShN/5X9G0VVTdb!Pj5G8g79ojPIu2ORi17Jaq7PlufsJzaLhUuHIqcayuvJwgejuj9zUMQPH76rqxMPaXSkL2n2Bvqc!mAYzWw==
    X-Complaints-To: www.supernews.com/docs/abuse.html
    X-DMCA-Complaints-To: www.supernews.com/docs/dmca.html
    X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
    X-Postfilter: 1.3.40
    X-Received-Bytes: 4005

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Cursitor Doom on Fri Oct 6 21:58:51 2023
    XPost: free.spam

    The idiot Cursitor Doom <cd@notformail.com> persisting in being an Off-topic troll...

    --
    Cursitor Doom <cd@notformail.com> wrote:

    Path: not-for-mail
    From: Cursitor Doom <cd@notformail.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Fri, 06 Oct 2023 19:34:07 +0100
    Organization: A noiseless patient Spider
    Lines: 47
    Message-ID: <7ck0iihs573mg7eq0v9jinefvqmua0s44m@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <5m80iit7i02me0ebcd9atci7laijvr64pt@4ax.com> <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com> <g5i0iid15j3c0pqms8ns2mheofcbrilmme@4ax.com>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Injection-Info: dont-email.me; posting-host="ab8e02080b2374a6e165f66e58e74c60";
    logging-data="1948857"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18poj9fkAXYxpD02nOexbt9OjwH2RY1hNY="
    User-Agent: ForteAgent/8.00.32.1272
    Cancel-Lock: sha1:0Hm0sic5evzfHePm2KKP9esMACU=
    X-Received-Bytes: 2535

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Joe Gwinn on Fri Oct 6 21:58:38 2023
    XPost: free.spam

    The arsehole Joe Gwinn <joegwinn@comcast.net> persisting in being an Off-topic troll...

    --
    Joe Gwinn <joegwinn@comcast.net> wrote:

    Path: not-for-mail
    NNTP-Posting-Date: Fri, 06 Oct 2023 18:27:44 +0000
    From: Joe Gwinn <joegwinn@comcast.net>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Fri, 06 Oct 2023 14:27:43 -0400
    Message-ID: <arj0ii5hpmd7t0k48d710k5ci032co991u@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <5m80iit7i02me0ebcd9atci7laijvr64pt@4ax.com> <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com> <g5i0iid15j3c0pqms8ns2mheofcbrilmme@4ax.com>
    User-Agent: ForteAgent/8.00.32.1272
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Lines: 55
    X-Usenet-Provider: http://www.giganews.com
    X-Trace: sv3-AxjD/g/Gqm1x6bhtwKFaNuVV6SnxN5bt79h4NqamSeCGnv3g2peFyozrgW2VeoqBcrZ3noZ+YKCMcqQ!il8nA8xdUw8jVqP7DRnmSCaULzEesPcffmlnylSDWzhFWdCFj4rMbVQp91D63ee5mTpZ/j8=
    X-Complaints-To: abuse@giganews.com
    X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
    X-Postfilter: 1.3.40
    Bytes: 2841
    X-Received-Bytes: 2979

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ricky@21:1/5 to John Larkin on Fri Oct 6 17:18:22 2023
    On Friday, October 6, 2023 at 11:15:37 AM UTC-4, John Larkin wrote:
    On Fri, 6 Oct 2023 07:25:48 -0700 (PDT), Fred Bloggs <bloggs.fred...@gmail.com> wrote:

    On Friday, October 6, 2023 at 9:52:59?AM UTC-4, Anthony William Sloman wrote:
    On Saturday, October 7, 2023 at 12:12:31?AM UTC+11, Cursitor Doom wrote: >> > Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.

    Taking out the ignition key usually seems to work when my ( internal combustion-engined) car decides to turn it's cruise control on.

    Another woman-designed subsystem...


    --
    Bill Sloman, Sydney
    More likely "programmer designed."

    The programmers that I know, mostly male, can type way faster than
    they can think.

    That's not unique to programmers.

    --

    Rick C.

    + Get 1,000 miles of free Supercharging
    + Tesla referral code - https://ts.la/richard11209

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ricky@21:1/5 to Cursitor Doom on Fri Oct 6 17:16:39 2023
    On Friday, October 6, 2023 at 9:12:31 AM UTC-4, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    It was an MG, for Christ's sake!!! No one expects them to work without failure!!!

    --

    Rick C.

    - Get 1,000 miles of free Supercharging
    - Tesla referral code - https://ts.la/richard11209

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Ricky on Sat Oct 7 02:53:02 2023
    XPost: free.spam

    The idiot Ricky <gnuarm.deletethisbit@gmail.com> persisting in being an Off-topic troll...

    --
    Ricky <gnuarm.deletethisbit@gmail.com> wrote:

    X-Received: by 2002:a05:622a:1482:b0:418:14ee:ac54 with SMTP id t2-20020a05622a148200b0041814eeac54mr148588qtx.12.1696637903513;
    Fri, 06 Oct 2023 17:18:23 -0700 (PDT)
    X-Received: by 2002:a9d:68da:0:b0:6b9:99ab:7f25 with SMTP id
    i26-20020a9d68da000000b006b999ab7f25mr2979365oto.6.1696637903209; Fri, 06 Oct
    2023 17:18:23 -0700 (PDT)
    Path: not-for-mail
    Newsgroups: sci.electronics.design
    Date: Fri, 6 Oct 2023 17:18:22 -0700 (PDT)
    In-Reply-To: <h090ii58b0arigrj4s45bq9pgfv8qhsso0@4ax.com>
    Injection-Info: google-groups.googlegroups.com; posting-host=63.114.57.174; posting-account=I-_H_woAAAA9zzro6crtEpUAyIvzd19b
    NNTP-Posting-Host: 63.114.57.174
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    <492c43ea-3a3b-41c5-b963-70ecb1558e63n@googlegroups.com> <h090ii58b0arigrj4s45bq9pgfv8qhsso0@4ax.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <6c1fffa2-d6aa-48d1-ba27-5cabd21dfc0cn@googlegroups.com>
    Subject: Re: Another EV goes haywire!
    From: Ricky <gnuarm.deletethisbit@gmail.com>
    Injection-Date: Sat, 07 Oct 2023 00:18:23 +0000
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable
    X-Received-Bytes: 2584

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to Clive Arthur on Fri Oct 6 20:25:37 2023
    On Saturday, October 7, 2023 at 2:00:30 AM UTC+11, Clive Arthur wrote:
    On 06/10/2023 14:52, Anthony William Sloman wrote:
    On Saturday, October 7, 2023 at 12:12:31 AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.

    He like the attention, that's all.

    He clearly does, who in their right mind would want to get attention for endorsing a string of fatuous ideas?

    Taking out the ignition key usually seems to work when my ( internal combustion-engined) car decides to turn it's cruise control on. One has to wonder why the driver didn't try it.

    On many (most?) cars, that would lock the steering.

    Didn't in mine. And you shouldn't have to take it out for long to reset the control processor.

    Perhaps Cursitor Doom hasn't had to cope with a modern car yet. Mine is about ten years old, so it isn't all that modern, but it did come with all kinds of programmed bells and whistles.

    Mine's coming up to 20 years old. The central locking hasn't worked for years and one door won't lock at all. The dashboard display sometimes spontaneously starts using German, and the rear wiper has a mind of its own. It's a Citroen, of course.

    Never owned one. I liked Peugeot's and the current car is a Merc (wife's choice). Citroens always seems to be a bit too idiosyncratic - one of my mates lost his when his garage put regular brake fluid into the hydraulic system, which utterly wrecked it (
    for all practical purposes - you'd have had to dismantled the car to replace all the individual parts that it wrecked and the car wasn't worth the cost of the labour involved).

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to John Larkin on Fri Oct 6 20:29:39 2023
    On Saturday, October 7, 2023 at 2:15:37 AM UTC+11, John Larkin wrote:
    On Fri, 6 Oct 2023 07:25:48 -0700 (PDT), Fred Bloggs <bloggs.fred...@gmail.com> wrote:

    On Friday, October 6, 2023 at 9:52:59?AM UTC-4, Anthony William Sloman wrote:
    On Saturday, October 7, 2023 at 12:12:31?AM UTC+11, Cursitor Doom wrote: >> > Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.

    Taking out the ignition key usually seems to work when my ( internal combustion-engined) car decides to turn it's cruise control on.

    Another woman-designed subsystem...

    More likely "programmer designed."

    The programmers that I know, mostly male, can type way faster than they can think.

    If they could think, they wouldn't be working for John Larkin. The ones I knew, of both sexes, were pretty bright.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to Cursitor Doom on Fri Oct 6 20:34:21 2023
    On Saturday, October 7, 2023 at 4:02:01 AM UTC+11, Cursitor Doom wrote:
    On Fri, 6 Oct 2023 06:52:54 -0700 (PDT), Anthony William Sloman <bill....@ieee.org> wrote:
    On Saturday, October 7, 2023 at 12:12:31?AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.

    Taking out the ignition key usually seems to work when my ( internal combustion-engined) car decides to turn it's cruise control on. One has to wonder why the driver didn't try it.

    Perhaps Cursitor Doom hasn't had to cope with a modern car yet. Mine is about ten years old, so it isn't all that modern, but it did come with all kinds of programmed bells and whistles
    My ICE car won't allow me to take the key out whilst it's in motion, Bill, and it's 20 years old. This is nothing new. Your car must be a bit like you: peculiar.

    It's a Mercedes 180B. If it's peculiar, it peculiar in a positive way.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to Cursitor Doom on Fri Oct 6 20:47:24 2023
    On Saturday, October 7, 2023 at 4:12:33 AM UTC+11, Cursitor Doom wrote:
    On Fri, 6 Oct 2023 06:52:54 -0700 (PDT), Anthony William Sloman <bill....@ieee.org> wrote:
    On Saturday, October 7, 2023 at 12:12:31?AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.
    Perhaps not, but when they do go wrong, the results can be catastrophic because of the huge amount of energy in the battery.

    Internal combustion-engined cars have exactly the same amount of energy stored in the petrol tank, and have been invoolved i catastrophic fires since they were first introduced.

    It's curious how Teslas have the propensity to burst into flame then lock all the doors.

    Ask any source of misleading information and they will repeat this story. It doesn't make it true.

    I suppose that *could* somehow happen with an ICE car, but I've never heard of such an incident involving one.

    The ICE car industry doesn't pay people to spread that partiuclar bit of misleading misinformation.

    And the charging infrastructure just isn't there.

    Yet.

    EV sales as a proportion of overall car sales are falling now in the UK and Europe because of all sorts of mounting concerns.

    https://www.reuters.com/business/autos-transportation/european-car-sales-rise-15-july-evs-up-nearly-61-2023-08-30/

    Since they aren't, my only concern is where you got your misinformation. Perhaps you invented it.

    I personally would give EVs another 10 years, so all the issues surrounding them can be ironed out.

    So now we known what a gullible idiot would do.

    I for one certainly won't be wasting my money on one any time soon and by the time I am I'll probably be to old to safely get behind a wheel anyway.

    You are driving a twenty-year-old car. Clearly you haven't got any money to waste. If your driving is as confused as your thinking, you shouldn't be allowed to control a shopping trolley, let alone a car.

    --
    Bill Slkoman, sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to John Larkin on Fri Oct 6 20:50:52 2023
    On Saturday, October 7, 2023 at 4:54:00 AM UTC+11, John Larkin wrote:
    On Fri, 06 Oct 2023 18:00:19 +0100, Cursitor Doom <c...@notformail.com> wrote:

    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <j...@997arbor.com>
    wrote:

    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <c...@notformail.com> >>wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my apartment in San Francisco, across the Golden Gate Bridge, with no clutch.

    Are you talking about MGs - or "MGs" (the ones made nowadays in China).

    Classic MGs rarely give any trouble provided they're maintained regularly.

    Like weekly?

    I had a Sprite and a Midget, which were great fun and mechanically awful. All the fluids leaked, including rainwater from above. DGMS on Lucas electrics.

    Perhaps it's harder to get the proper spares for them in the US.

    I could get parts. Lots of them.

    Just couldn't work out how to fit them in where they were supposed to go.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cursitor Doom@21:1/5 to bill.sloman@ieee.org on Sat Oct 7 11:58:13 2023
    On Fri, 6 Oct 2023 20:47:24 -0700 (PDT), Anthony William Sloman <bill.sloman@ieee.org> wrote:

    On Saturday, October 7, 2023 at 4:12:33?AM UTC+11, Cursitor Doom wrote:
    On Fri, 6 Oct 2023 06:52:54 -0700 (PDT), Anthony William Sloman
    <bill....@ieee.org> wrote:
    On Saturday, October 7, 2023 at 12:12:31?AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.
    Perhaps not, but when they do go wrong, the results can be catastrophic because of the huge amount of energy in the battery.

    Internal combustion-engined cars have exactly the same amount of energy stored in the petrol tank, and have been invoolved i catastrophic fires since they were first introduced.

    It's curious how Teslas have the propensity to burst into flame then lock all the doors.

    Ask any source of misleading information and they will repeat this story. It doesn't make it true.

    I suppose that *could* somehow happen with an ICE car, but I've never heard of such an incident involving one.

    The ICE car industry doesn't pay people to spread that partiuclar bit of misleading misinformation.

    And the charging infrastructure just isn't there.

    Yet.

    EV sales as a proportion of overall car sales are falling now in the UK and Europe because of all sorts of mounting concerns.

    https://www.reuters.com/business/autos-transportation/european-car-sales-rise-15-july-evs-up-nearly-61-2023-08-30/

    Since they aren't, my only concern is where you got your misinformation. Perhaps you invented it.

    I personally would give EVs another 10 years, so all the issues surrounding them can be ironed out.

    So now we known what a gullible idiot would do.

    I for one certainly won't be wasting my money on one any time soon and by the time I am I'll probably be to old to safely get behind a wheel anyway.

    You are driving a twenty-year-old car. Clearly you haven't got any money to waste. If your driving is as confused as your thinking, you shouldn't be allowed to control a shopping trolley, let alone a car.

    It's been very well looked after. I have a lot of servicing and
    maintentance invested in it and I hate to waste anything (shadow of
    WW2 rationing) so I plan to run it for as long as it can safely keep
    going. I've been very pleased with it and nothing out there today
    appeals in the least.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cursitor Doom@21:1/5 to All on Sat Oct 7 12:00:12 2023
    On Fri, 06 Oct 2023 13:46:55 -0700, John Larkin <jl@997PotHill.com>
    wrote:

    On Fri, 06 Oct 2023 19:34:07 +0100, Cursitor Doom <cd@notformail.com>
    wrote:

    On Fri, 06 Oct 2023 10:53:42 -0700, John Larkin <jl@997PotHill.com>
    wrote:

    On Fri, 06 Oct 2023 18:00:19 +0100, Cursitor Doom <cd@notformail.com> >>>wrote:

    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <jl@997arbor.com> >>>>wrote:

    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <cd@notformail.com> >>>>>wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my >>>>>apartment in San Francisco, across the Golden Gate Bridge, with no >>>>>clutch.

    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained >>>>regularly.

    Like weekly?

    I had a Sprite and a Midget, which were great fun and mechanically
    awful. All the fluids leaked, including rainwater from above. DGMS on >>>Lucas electrics.

    Perhaps it's harder to get the proper spares for them in
    the US.

    I could get parts. Lots of them.

    I think you'd have had a much, much better experience with a pre-1976*
    MG B or possibly a TF. The MGB roadster is highly-regarded. There were
    so many of them made they're easy to find for sensible prices and
    spares are plentiful. A TF is more pricey but a really classic sports
    car with wonderful styling.
    * pre '76 'cos after that they had those hideous rubber safety
    fenders. Get a chrome bumper model if you can.

    The Midget was fun but not a good ski car.

    2wd and no place for skis and insane oversteer. Fun to spin if there
    were no trees nearby.

    We had to turn the heater off when it was really cold, or the engine
    would get too cold.

    Dear me, John. Any self-respecting classic car owner knows that's what
    radiator blinds are for!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to Cursitor Doom on Sat Oct 7 05:16:46 2023
    On Saturday, October 7, 2023 at 9:58:23 PM UTC+11, Cursitor Doom wrote:
    On Fri, 6 Oct 2023 20:47:24 -0700 (PDT), Anthony William Sloman <bill....@ieee.org> wrote:
    On Saturday, October 7, 2023 at 4:12:33?AM UTC+11, Cursitor Doom wrote:
    On Fri, 6 Oct 2023 06:52:54 -0700 (PDT), Anthony William Sloman
    <bill....@ieee.org> wrote:
    On Saturday, October 7, 2023 at 12:12:31?AM UTC+11, Cursitor Doom wrote: >> >> Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.
    Perhaps not, but when they do go wrong, the results can be catastrophic because of the huge amount of energy in the battery.

    Internal combustion-engined cars have exactly the same amount of energy stored in the petrol tank, and have been invoolved i catastrophic fires since they were first introduced.

    It's curious how Teslas have the propensity to burst into flame then lock all the doors.

    Ask any source of misleading information and they will repeat this story. It doesn't make it true.

    I suppose that *could* somehow happen with an ICE car, but I've never heard of such an incident involving one.

    The ICE car industry doesn't pay people to spread that partiuclar bit of misleading misinformation.

    And the charging infrastructure just isn't there.

    Yet.

    EV sales as a proportion of overall car sales are falling now in the UK and Europe because of all sorts of mounting concerns.

    https://www.reuters.com/business/autos-transportation/european-car-sales-rise-15-july-evs-up-nearly-61-2023-08-30/

    Since they aren't, my only concern is where you got your misinformation. Perhaps you invented it.

    I personally would give EVs another 10 years, so all the issues surrounding them can be ironed out.

    So now we known what a gullible idiot would do.

    I for one certainly won't be wasting my money on one any time soon and by the time I am I'll probably be to old to safely get behind a wheel anyway.

    You are driving a twenty-year-old car. Clearly you haven't got any money to waste. If your driving is as confused as your thinking, you shouldn't be allowed to control a shopping trolley, let alone a car.

    It's been very well looked after. I have a lot of servicing and maintentance invested in it and I hate to waste anything (shadow of WW2 rationing) so I plan to run it for as long as it can safely keep going. I've been very pleased with it and
    nothing out there today appeals in the least.

    And you couldn't afford it if it did.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cursitor Doom@21:1/5 to bill.sloman@ieee.org on Sat Oct 7 14:07:01 2023
    On Sat, 7 Oct 2023 05:16:46 -0700 (PDT), Anthony William Sloman <bill.sloman@ieee.org> wrote:

    On Saturday, October 7, 2023 at 9:58:23?PM UTC+11, Cursitor Doom wrote:
    On Fri, 6 Oct 2023 20:47:24 -0700 (PDT), Anthony William Sloman
    <bill....@ieee.org> wrote:
    On Saturday, October 7, 2023 at 4:12:33?AM UTC+11, Cursitor Doom wrote:
    On Fri, 6 Oct 2023 06:52:54 -0700 (PDT), Anthony William Sloman
    <bill....@ieee.org> wrote:
    On Saturday, October 7, 2023 at 12:12:31?AM UTC+11, Cursitor Doom wrote: >> >> >> Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.
    Perhaps not, but when they do go wrong, the results can be catastrophic because of the huge amount of energy in the battery.

    Internal combustion-engined cars have exactly the same amount of energy stored in the petrol tank, and have been invoolved i catastrophic fires since they were first introduced.

    It's curious how Teslas have the propensity to burst into flame then lock all the doors.

    Ask any source of misleading information and they will repeat this story. It doesn't make it true.

    I suppose that *could* somehow happen with an ICE car, but I've never heard of such an incident involving one.

    The ICE car industry doesn't pay people to spread that partiuclar bit of misleading misinformation.

    And the charging infrastructure just isn't there.

    Yet.

    EV sales as a proportion of overall car sales are falling now in the UK and Europe because of all sorts of mounting concerns.

    https://www.reuters.com/business/autos-transportation/european-car-sales-rise-15-july-evs-up-nearly-61-2023-08-30/

    Since they aren't, my only concern is where you got your misinformation. Perhaps you invented it.

    I personally would give EVs another 10 years, so all the issues surrounding them can be ironed out.

    So now we known what a gullible idiot would do.

    I for one certainly won't be wasting my money on one any time soon and by the time I am I'll probably be to old to safely get behind a wheel anyway.

    You are driving a twenty-year-old car. Clearly you haven't got any money to waste. If your driving is as confused as your thinking, you shouldn't be allowed to control a shopping trolley, let alone a car.

    It's been very well looked after. I have a lot of servicing and maintentance invested in it and I hate to waste anything (shadow of WW2 rationing) so I plan to run it for as long as it can safely keep going. I've been very pleased with it and
    nothing out there today appeals in the least.

    And you couldn't afford it if it did.

    Yeah, whatever.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred Bloggs@21:1/5 to Cursitor Doom on Sat Oct 7 07:49:40 2023
    On Friday, October 6, 2023 at 1:00:27 PM UTC-4, Cursitor Doom wrote:
    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <j...@997arbor.com>
    wrote:
    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <c...@notformail.com> >wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my
    apartment in San Francisco, across the Golden Gate Bridge, with no
    clutch.
    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained
    regularly. Perhaps it's harder to get the proper spares for them in
    the US.

    English automotive design is excellent, it's the manufacturing that's problematic. And that seems to be the case with a lot of UK industry.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Larkin@21:1/5 to All on Sat Oct 7 08:29:19 2023
    On Sat, 07 Oct 2023 12:00:12 +0100, Cursitor Doom <cd@notformail.com>
    wrote:

    On Fri, 06 Oct 2023 13:46:55 -0700, John Larkin <jl@997PotHill.com>
    wrote:

    On Fri, 06 Oct 2023 19:34:07 +0100, Cursitor Doom <cd@notformail.com> >>wrote:

    On Fri, 06 Oct 2023 10:53:42 -0700, John Larkin <jl@997PotHill.com> >>>wrote:

    On Fri, 06 Oct 2023 18:00:19 +0100, Cursitor Doom <cd@notformail.com> >>>>wrote:

    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <jl@997arbor.com> >>>>>wrote:

    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <cd@notformail.com> >>>>>>wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my >>>>>>apartment in San Francisco, across the Golden Gate Bridge, with no >>>>>>clutch.

    Are you talking about MGs - or "MGs" (the ones made nowadays in >>>>>China).
    Classic MGs rarely give any trouble provided they're maintained >>>>>regularly.

    Like weekly?

    I had a Sprite and a Midget, which were great fun and mechanically >>>>awful. All the fluids leaked, including rainwater from above. DGMS on >>>>Lucas electrics.

    Perhaps it's harder to get the proper spares for them in
    the US.

    I could get parts. Lots of them.

    I think you'd have had a much, much better experience with a pre-1976*
    MG B or possibly a TF. The MGB roadster is highly-regarded. There were
    so many of them made they're easy to find for sensible prices and
    spares are plentiful. A TF is more pricey but a really classic sports
    car with wonderful styling.
    * pre '76 'cos after that they had those hideous rubber safety
    fenders. Get a chrome bumper model if you can.

    The Midget was fun but not a good ski car.

    2wd and no place for skis and insane oversteer. Fun to spin if there
    were no trees nearby.

    We had to turn the heater off when it was really cold, or the engine
    would get too cold.

    Dear me, John. Any self-respecting classic car owner knows that's what >radiator blinds are for!

    Was there a thermostat in the radiator loop? Lucas?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to John Larkin on Sat Oct 7 08:41:29 2023
    On Sunday, October 8, 2023 at 2:29:46 AM UTC+11, John Larkin wrote:
    On Sat, 07 Oct 2023 12:00:12 +0100, Cursitor Doom <c...@notformail.com> wrote:
    On Fri, 06 Oct 2023 13:46:55 -0700, John Larkin <j...@997PotHill.com> wrote:
    On Fri, 06 Oct 2023 19:34:07 +0100, Cursitor Doom <c...@notformail.com> wrote:
    On Fri, 06 Oct 2023 10:53:42 -0700, John Larkin <j...@997PotHill.com> wrote: ]
    On Fri, 06 Oct 2023 18:00:19 +0100, Cursitor Doom <c...@notformail.com> wrote:
    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <j...@997arbor.com> wrote:
    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <c...@notformail.com> wrote:

    <snip>

    Was there a thermostat in the radiator loop? Lucas?

    https://savree.com/en/encyclopedia/engine-thermostat

    That looks like the sort of thermostat I remember from back when I worked on my own car. They were pretty much standard.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Cursitor Doom on Sat Oct 7 16:25:28 2023
    XPost: free.spam

    The idiot Cursitor Doom <cd@notformail.com> persisting in being an Off-topic troll...

    --
    Cursitor Doom <cd@notformail.com> wrote:

    Path: not-for-mail
    From: Cursitor Doom <cd@notformail.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Sat, 07 Oct 2023 11:58:13 +0100
    Organization: A noiseless patient Spider
    Lines: 47
    Message-ID: <lae2iihjb4oo6ldsfuh7fglcmm1kjmiu9s@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com> <8jf0ii9jl85b0vudo98mvme728novrvhmi@4ax.com> <5b33a4f3-cf41-44dc-9fc3-d77e540356c4n@googlegroups.com>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Injection-Info: dont-email.me; posting-host="37a766b973e4fdeda972184558f5c56f";
    logging-data="2459264"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18W1dzycZr1ZR5WwuxZC9po9EHMh7EzRTc="
    User-Agent: ForteAgent/8.00.32.1272
    Cancel-Lock: sha1:gLri3y0CUD/+ubaAEFJkC6teV/k=
    X-Received-Bytes: 3779

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to John Larkin on Sat Oct 7 16:25:46 2023
    XPost: free.spam

    The arsehole John Larkin <jl@997arbor.com> persisting in being an Off-topic troll...

    --
    John Larkin <jl@997arbor.com> wrote:

    Path: not-for-mail
    NNTP-Posting-Date: Sat, 07 Oct 2023 15:29:28 +0000
    From: John Larkin <jl@997arbor.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Sat, 07 Oct 2023 08:29:19 -0700
    Message-ID: <p8u2iidbk012bdjbhdtfojs22qrf4a198i@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <5m80iit7i02me0ebcd9atci7laijvr64pt@4ax.com> <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com> <g5i0iid15j3c0pqms8ns2mheofcbrilmme@4ax.com> <7ck0iihs573mg7eq0v9jinefvqmua0s44m@4ax.com> <
    r9s0iila3mbml68vh0acfibicc95coba38@4ax.com> <1ge2iilcgeu84lrhncoeceett4kmi1rmdq@4ax.com>
    X-Newsreader: Forte Agent 3.1/32.783
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Lines: 70
    X-Trace: sv3-hT8ctpGDijDbX0hwQ10hBEbq7UZg6g6OMswJpCYXm8hmLE2wopPlTNkD1bOOWsYMmUc6qbVJAzLZPzo!R/1jeHtICTXWOwTTBdAIqOETu8oMUNvHM5glS6Zub2FoVj+LSJVM3s+fr2DITmcI+CVzS3n9QTI4!xcxTRA==
    X-Complaints-To: www.supernews.com/docs/abuse.html
    X-DMCA-Complaints-To: www.supernews.com/docs/dmca.html
    X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
    X-Postfilter: 1.3.40
    X-Received-Bytes: 3844

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cursitor Doom@21:1/5 to bloggs.fredbloggs.fred@gmail.com on Sat Oct 7 23:23:19 2023
    On Sat, 7 Oct 2023 07:49:40 -0700 (PDT), Fred Bloggs <bloggs.fredbloggs.fred@gmail.com> wrote:

    On Friday, October 6, 2023 at 1:00:27?PM UTC-4, Cursitor Doom wrote:
    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <j...@997arbor.com>
    wrote:
    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <c...@notformail.com>
    wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my
    apartment in San Francisco, across the Golden Gate Bridge, with no
    clutch.
    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained
    regularly. Perhaps it's harder to get the proper spares for them in
    the US.

    English automotive design is excellent, it's the manufacturing that's problematic. And that seems to be the case with a lot of UK industry.

    Fair comment. But you could easily say the same thing about American manufacturing in that same period.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ricky@21:1/5 to Cursitor Doom on Sat Oct 7 17:14:08 2023
    On Saturday, October 7, 2023 at 6:58:23 AM UTC-4, Cursitor Doom wrote:
    On Fri, 6 Oct 2023 20:47:24 -0700 (PDT), Anthony William Sloman <bill....@ieee.org> wrote:
    On Saturday, October 7, 2023 at 4:12:33?AM UTC+11, Cursitor Doom wrote:
    On Fri, 6 Oct 2023 06:52:54 -0700 (PDT), Anthony William Sloman
    <bill....@ieee.org> wrote:
    On Saturday, October 7, 2023 at 12:12:31?AM UTC+11, Cursitor Doom wrote: >> >> Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.
    Perhaps not, but when they do go wrong, the results can be catastrophic because of the huge amount of energy in the battery.

    Internal combustion-engined cars have exactly the same amount of energy stored in the petrol tank, and have been invoolved i catastrophic fires since they were first introduced.

    It's curious how Teslas have the propensity to burst into flame then lock all the doors.

    Ask any source of misleading information and they will repeat this story. It doesn't make it true.

    I suppose that *could* somehow happen with an ICE car, but I've never heard of such an incident involving one.

    The ICE car industry doesn't pay people to spread that partiuclar bit of misleading misinformation.

    And the charging infrastructure just isn't there.

    Yet.

    EV sales as a proportion of overall car sales are falling now in the UK and Europe because of all sorts of mounting concerns.

    https://www.reuters.com/business/autos-transportation/european-car-sales-rise-15-july-evs-up-nearly-61-2023-08-30/

    Since they aren't, my only concern is where you got your misinformation. Perhaps you invented it.

    I personally would give EVs another 10 years, so all the issues surrounding them can be ironed out.

    So now we known what a gullible idiot would do.

    I for one certainly won't be wasting my money on one any time soon and by the time I am I'll probably be to old to safely get behind a wheel anyway.

    You are driving a twenty-year-old car. Clearly you haven't got any money to waste. If your driving is as confused as your thinking, you shouldn't be allowed to control a shopping trolley, let alone a car.
    It's been very well looked after. I have a lot of servicing and
    maintentance invested in it and I hate to waste anything (shadow of
    WW2 rationing) so I plan to run it for as long as it can safely keep
    going. I've been very pleased with it and nothing out there today
    appeals in the least.

    Where will you get gasoline? It's not like gas stations will be staying open for people like you. By 2040 EVs will be over 95% of the cars on the road, which means only 1 in 20 gas stations will be open. Soon after that, it will be none.

    --

    Rick C.

    + Get 1,000 miles of free Supercharging
    + Tesla referral code - https://ts.la/richard11209

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ricky@21:1/5 to Cursitor Doom on Sat Oct 7 17:19:54 2023
    On Saturday, October 7, 2023 at 6:23:27 PM UTC-4, Cursitor Doom wrote:
    On Sat, 7 Oct 2023 07:49:40 -0700 (PDT), Fred Bloggs <bloggs.fred...@gmail.com> wrote:
    On Friday, October 6, 2023 at 1:00:27?PM UTC-4, Cursitor Doom wrote:
    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <j...@997arbor.com>
    wrote:
    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <c...@notformail.com> >> >wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my
    apartment in San Francisco, across the Golden Gate Bridge, with no
    clutch.
    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained
    regularly. Perhaps it's harder to get the proper spares for them in
    the US.

    English automotive design is excellent, it's the manufacturing that's problematic. And that seems to be the case with a lot of UK industry.
    Fair comment. But you could easily say the same thing about American manufacturing in that same period.

    And they would both be wrong. The US stopped any real improvements of the cars they made until they were forced to by the Japanese. They designed crappy cars and they built crappy cars, both British and US.

    --

    Rick C.

    -+ Get 1,000 miles of free Supercharging
    -+ Tesla referral code - https://ts.la/richard11209

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ricky@21:1/5 to Fred Bloggs on Sat Oct 7 17:17:37 2023
    On Saturday, October 7, 2023 at 10:49:45 AM UTC-4, Fred Bloggs wrote:
    On Friday, October 6, 2023 at 1:00:27 PM UTC-4, Cursitor Doom wrote:
    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <j...@997arbor.com>
    wrote:
    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <c...@notformail.com> >wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my >apartment in San Francisco, across the Golden Gate Bridge, with no >clutch.
    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained
    regularly. Perhaps it's harder to get the proper spares for them in
    the US.

    English automotive design is excellent, it's the manufacturing that's problematic. And that seems to be the case with a lot of UK industry.

    British automotive design was terrible pretty much anytime after WWII. They lost the financial base to invest in research. So a 1970 British car was pretty much the same as a 1950 British car. Same for the US, except they had the money, just not the
    motivation until the Japanese started eating their lunch because of the reliability problems. The US improved greatly, the British sold their car companies to the real automakers.

    --

    Rick C.

    -- Get 1,000 miles of free Supercharging
    -- Tesla referral code - https://ts.la/richard11209

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Ricky on Sun Oct 8 15:19:04 2023
    XPost: free.spam

    The arsehole Ricky <gnuarm.deletethisbit@gmail.com> persisting in being an Off-topic troll...

    --
    Ricky <gnuarm.deletethisbit@gmail.com> wrote:

    X-Received: by 2002:ac8:5314:0:b0:41a:3e99:d233 with SMTP id t20-20020ac85314000000b0041a3e99d233mr138639qtn.0.1696724049380;
    Sat, 07 Oct 2023 17:14:09 -0700 (PDT)
    X-Received: by 2002:a05:6870:9552:b0:1e1:82c6:33f1 with SMTP id
    v18-20020a056870955200b001e182c633f1mr4869097oal.2.1696724049098; Sat, 07 Oct
    2023 17:14:09 -0700 (PDT)
    Path: not-for-mail
    Newsgroups: sci.electronics.design
    Date: Sat, 7 Oct 2023 17:14:08 -0700 (PDT)
    In-Reply-To: <lae2iihjb4oo6ldsfuh7fglcmm1kjmiu9s@4ax.com>
    Injection-Info: google-groups.googlegroups.com; posting-host=65.207.89.54; posting-account=I-_H_woAAAA9zzro6crtEpUAyIvzd19b
    NNTP-Posting-Host: 65.207.89.54
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    <8jf0ii9jl85b0vudo98mvme728novrvhmi@4ax.com> <5b33a4f3-cf41-44dc-9fc3-d77e540356c4n@googlegroups.com>
    <lae2iihjb4oo6ldsfuh7fglcmm1kjmiu9s@4ax.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <ea84c32e-5b45-427a-9879-b1768a3053c0n@googlegroups.com>
    Subject: Re: Another EV goes haywire!
    From: Ricky <gnuarm.deletethisbit@gmail.com>
    Injection-Date: Sun, 08 Oct 2023 00:14:09 +0000
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable
    X-Received-Bytes: 4748

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cursitor Doom@21:1/5 to gnuarm.deletethisbit@gmail.com on Sun Oct 8 18:03:06 2023
    On Sat, 7 Oct 2023 17:14:08 -0700 (PDT), Ricky
    <gnuarm.deletethisbit@gmail.com> wrote:

    On Saturday, October 7, 2023 at 6:58:23?AM UTC-4, Cursitor Doom wrote:
    On Fri, 6 Oct 2023 20:47:24 -0700 (PDT), Anthony William Sloman
    <bill....@ieee.org> wrote:
    On Saturday, October 7, 2023 at 4:12:33?AM UTC+11, Cursitor Doom wrote:
    On Fri, 6 Oct 2023 06:52:54 -0700 (PDT), Anthony William Sloman
    <bill....@ieee.org> wrote:
    On Saturday, October 7, 2023 at 12:12:31?AM UTC+11, Cursitor Doom wrote: >> >> >> Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.
    Perhaps not, but when they do go wrong, the results can be catastrophic because of the huge amount of energy in the battery.

    Internal combustion-engined cars have exactly the same amount of energy stored in the petrol tank, and have been invoolved i catastrophic fires since they were first introduced.

    It's curious how Teslas have the propensity to burst into flame then lock all the doors.

    Ask any source of misleading information and they will repeat this story. It doesn't make it true.

    I suppose that *could* somehow happen with an ICE car, but I've never heard of such an incident involving one.

    The ICE car industry doesn't pay people to spread that partiuclar bit of misleading misinformation.

    And the charging infrastructure just isn't there.

    Yet.

    EV sales as a proportion of overall car sales are falling now in the UK and Europe because of all sorts of mounting concerns.

    https://www.reuters.com/business/autos-transportation/european-car-sales-rise-15-july-evs-up-nearly-61-2023-08-30/

    Since they aren't, my only concern is where you got your misinformation. Perhaps you invented it.

    I personally would give EVs another 10 years, so all the issues surrounding them can be ironed out.

    So now we known what a gullible idiot would do.

    I for one certainly won't be wasting my money on one any time soon and by the time I am I'll probably be to old to safely get behind a wheel anyway.

    You are driving a twenty-year-old car. Clearly you haven't got any money to waste. If your driving is as confused as your thinking, you shouldn't be allowed to control a shopping trolley, let alone a car.
    It's been very well looked after. I have a lot of servicing and
    maintentance invested in it and I hate to waste anything (shadow of
    WW2 rationing) so I plan to run it for as long as it can safely keep
    going. I've been very pleased with it and nothing out there today
    appeals in the least.

    Where will you get gasoline? It's not like gas stations will be staying open for people like you. By 2040 EVs will be over 95% of the cars on the road, which means only 1 in 20 gas stations will be open. Soon after that, it will be none.

    I'll be long dead by then so quite frankly ICGAS.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cursitor Doom@21:1/5 to gnuarm.deletethisbit@gmail.com on Sun Oct 8 18:10:00 2023
    On Sat, 7 Oct 2023 17:17:37 -0700 (PDT), Ricky
    <gnuarm.deletethisbit@gmail.com> wrote:

    On Saturday, October 7, 2023 at 10:49:45?AM UTC-4, Fred Bloggs wrote:
    On Friday, October 6, 2023 at 1:00:27?PM UTC-4, Cursitor Doom wrote:
    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <j...@997arbor.com>
    wrote:
    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <c...@notformail.com> >> > >wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my
    apartment in San Francisco, across the Golden Gate Bridge, with no
    clutch.
    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained
    regularly. Perhaps it's harder to get the proper spares for them in
    the US.

    English automotive design is excellent, it's the manufacturing that's problematic. And that seems to be the case with a lot of UK industry.

    British automotive design was terrible pretty much anytime after WWII. They lost the financial base to invest in research. So a 1970 British car was pretty much the same as a 1950 British car. Same for the US, except they had the money, just not the
    motivation until the Japanese started eating their lunch because of the reliability problems. The US improved greatly, the British sold their car companies to the real automakers.

    The British are fantastic conceptualists. They come up with the most
    amazing ideas and designs for various things, but are largely hopeless
    at successfully bringing them to market. Many old classic British
    cars that were inspired by fabulous concepts never made the grade
    until they were retro-re-engineered decades later to finally become
    the cars they were *meant* to be back in the day.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Cursitor Doom on Sun Oct 8 17:33:41 2023
    XPost: free.spam

    The arsehole Cursitor Doom <cd@notformail.com> persisting in being an Off-topic troll...

    --
    Cursitor Doom <cd@notformail.com> wrote:

    Path: not-for-mail
    From: Cursitor Doom <cd@notformail.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Sun, 08 Oct 2023 18:03:06 +0100
    Organization: A noiseless patient Spider
    Lines: 53
    Message-ID: <c5o5ii99cqvhidji5f3pmr4l0p31amkdlu@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com> <8jf0ii9jl85b0vudo98mvme728novrvhmi@4ax.com> <5b33a4f3-cf41-44dc-9fc3-d77e540356c4n@googlegroups.com> <lae2iihjb4oo6ldsfuh7fglcmm1kjmiu9s@
    4ax.com> <ea84c32e-5b45-427a-9879-b1768a3053c0n@googlegroups.com>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Injection-Info: dont-email.me; posting-host="7c6e0630c4c2b1863232d79951c964bb";
    logging-data="3382236"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+VQkEIwquo5J1SdK2H8cOb+h181FJw3AA="
    User-Agent: ForteAgent/8.00.32.1272
    Cancel-Lock: sha1:rpS0k6ENooHJ5Y8TQhReda1L+YE=
    X-Received-Bytes: 4324

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Fred Bloggs on Sun Oct 8 17:36:41 2023
    XPost: free.spam

    The arsehole Fred Bloggs <bloggs.fredbloggs.fred@gmail.com> persisting in being an Off-topic troll...

    --
    Fred Bloggs <bloggs.fredbloggs.fred@gmail.com> wrote:

    X-Received: by 2002:a05:622a:1a84:b0:417:971e:ab19 with SMTP id s4-20020a05622a1a8400b00417971eab19mr165539qtc.12.1696690181419;
    Sat, 07 Oct 2023 07:49:41 -0700 (PDT)
    X-Received: by 2002:a05:6870:bf0b:b0:1e5:78de:89b4 with SMTP id
    qh11-20020a056870bf0b00b001e578de89b4mr2398996oab.0.1696690180936; Sat, 07
    Oct 2023 07:49:40 -0700 (PDT)
    Path: not-for-mail
    Newsgroups: sci.electronics.design
    Date: Sat, 7 Oct 2023 07:49:40 -0700 (PDT)
    In-Reply-To: <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com>
    Injection-Info: google-groups.googlegroups.com; posting-host=2601:5cc:4701:5250:dc1c:a48d:c866:dc6c;
    posting-account=iGtwSwoAAABNNwPORfvAs6OM4AR9GRHt
    NNTP-Posting-Host: 2601:5cc:4701:5250:dc1c:a48d:c866:dc6c
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <5m80iit7i02me0ebcd9atci7laijvr64pt@4ax.com>
    <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <1169b273-74af-468a-b929-86910e486d55n@googlegroups.com>
    Subject: Re: Another EV goes haywire!
    From: Fred Bloggs <bloggs.fredbloggs.fred@gmail.com>
    Injection-Date: Sat, 07 Oct 2023 14:49:41 +0000
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable
    X-Received-Bytes: 2408

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Ricky on Sun Oct 8 17:36:47 2023
    XPost: free.spam

    The arsehole Ricky <gnuarm.deletethisbit@gmail.com> persisting in being an Off-topic troll...

    --
    Ricky <gnuarm.deletethisbit@gmail.com> wrote:

    X-Received: by 2002:a05:620a:31a7:b0:76e:fdb4:c124 with SMTP id bi39-20020a05620a31a700b0076efdb4c124mr189558qkb.3.1696724395198;
    Sat, 07 Oct 2023 17:19:55 -0700 (PDT)
    X-Received: by 2002:a05:6808:3098:b0:3ad:fe4c:17fc with SMTP id
    bl24-20020a056808309800b003adfe4c17fcmr4291433oib.0.1696724394975; Sat, 07
    Oct 2023 17:19:54 -0700 (PDT)
    Path: not-for-mail
    Newsgroups: sci.electronics.design
    Date: Sat, 7 Oct 2023 17:19:54 -0700 (PDT)
    In-Reply-To: <cgm3iid0dfvrvoipr2jv786s69phn4846m@4ax.com>
    Injection-Info: google-groups.googlegroups.com; posting-host=65.207.89.54; posting-account=I-_H_woAAAA9zzro6crtEpUAyIvzd19b
    NNTP-Posting-Host: 65.207.89.54
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <5m80iit7i02me0ebcd9atci7laijvr64pt@4ax.com>
    <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com> <1169b273-74af-468a-b929-86910e486d55n@googlegroups.com>
    <cgm3iid0dfvrvoipr2jv786s69phn4846m@4ax.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <acf5801e-cd08-4ffd-9f06-b56c7160c793n@googlegroups.com>
    Subject: Re: Another EV goes haywire!
    From: Ricky <gnuarm.deletethisbit@gmail.com>
    Injection-Date: Sun, 08 Oct 2023 00:19:55 +0000
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable
    X-Received-Bytes: 3164

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Cursitor Doom on Sun Oct 8 17:37:00 2023
    XPost: free.spam

    The idiot Cursitor Doom <cd@notformail.com> persisting in being an Off-topic troll...

    --
    Cursitor Doom <cd@notformail.com> wrote:

    Path: not-for-mail
    From: Cursitor Doom <cd@notformail.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Sat, 07 Oct 2023 23:23:19 +0100
    Organization: A noiseless patient Spider
    Lines: 30
    Message-ID: <cgm3iid0dfvrvoipr2jv786s69phn4846m@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <5m80iit7i02me0ebcd9atci7laijvr64pt@4ax.com> <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com> <1169b273-74af-468a-b929-86910e486d55n@googlegroups.com>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Injection-Info: dont-email.me; posting-host="7c6e0630c4c2b1863232d79951c964bb";
    logging-data="2779913"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19CHXCyIx8OdqwHRTrWiMjYhffZ2ruDxcg="
    User-Agent: ForteAgent/8.00.32.1272
    Cancel-Lock: sha1:MwC00JLUSlnlJOKYDBt+Qz+X4HA=
    X-Received-Bytes: 2364

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ricky@21:1/5 to Cursitor Doom on Sun Oct 8 13:20:36 2023
    On Sunday, October 8, 2023 at 1:15:09 PM UTC-4, Cursitor Doom wrote:
    On Sat, 7 Oct 2023 17:17:37 -0700 (PDT), Ricky
    <gnuarm.del...@gmail.com> wrote:

    On Saturday, October 7, 2023 at 10:49:45?AM UTC-4, Fred Bloggs wrote:
    On Friday, October 6, 2023 at 1:00:27?PM UTC-4, Cursitor Doom wrote:
    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <j...@997arbor.com>
    wrote:
    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <c...@notformail.com>
    wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my
    apartment in San Francisco, across the Golden Gate Bridge, with no
    clutch.
    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained
    regularly. Perhaps it's harder to get the proper spares for them in
    the US.

    English automotive design is excellent, it's the manufacturing that's problematic. And that seems to be the case with a lot of UK industry.

    British automotive design was terrible pretty much anytime after WWII. They lost the financial base to invest in research. So a 1970 British car was pretty much the same as a 1950 British car. Same for the US, except they had the money, just not the
    motivation until the Japanese started eating their lunch because of the reliability problems. The US improved greatly, the British sold their car companies to the real automakers.
    The British are fantastic conceptualists. They come up with the most
    amazing ideas and designs for various things, but are largely hopeless
    at successfully bringing them to market. Many old classic British
    cars that were inspired by fabulous concepts never made the grade
    until they were retro-re-engineered decades later to finally become
    the cars they were *meant* to be back in the day.

    Such as?

    --

    Rick C.

    ++ Get 1,000 miles of free Supercharging
    ++ Tesla referral code - https://ts.la/richard11209

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ricky@21:1/5 to Cursitor Doom on Sun Oct 8 13:19:19 2023
    On Sunday, October 8, 2023 at 1:03:14 PM UTC-4, Cursitor Doom wrote:
    On Sat, 7 Oct 2023 17:14:08 -0700 (PDT), Ricky
    <gnuarm.del...@gmail.com> wrote:
    On Saturday, October 7, 2023 at 6:58:23?AM UTC-4, Cursitor Doom wrote:
    On Fri, 6 Oct 2023 20:47:24 -0700 (PDT), Anthony William Sloman
    <bill....@ieee.org> wrote:
    On Saturday, October 7, 2023 at 4:12:33?AM UTC+11, Cursitor Doom wrote: >> >> On Fri, 6 Oct 2023 06:52:54 -0700 (PDT), Anthony William Sloman
    <bill....@ieee.org> wrote:
    On Saturday, October 7, 2023 at 12:12:31?AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.
    Perhaps not, but when they do go wrong, the results can be catastrophic because of the huge amount of energy in the battery.

    Internal combustion-engined cars have exactly the same amount of energy stored in the petrol tank, and have been invoolved i catastrophic fires since they were first introduced.

    It's curious how Teslas have the propensity to burst into flame then lock all the doors.

    Ask any source of misleading information and they will repeat this story. It doesn't make it true.

    I suppose that *could* somehow happen with an ICE car, but I've never heard of such an incident involving one.

    The ICE car industry doesn't pay people to spread that partiuclar bit of misleading misinformation.

    And the charging infrastructure just isn't there.

    Yet.

    EV sales as a proportion of overall car sales are falling now in the UK and Europe because of all sorts of mounting concerns.

    https://www.reuters.com/business/autos-transportation/european-car-sales-rise-15-july-evs-up-nearly-61-2023-08-30/

    Since they aren't, my only concern is where you got your misinformation. Perhaps you invented it.

    I personally would give EVs another 10 years, so all the issues surrounding them can be ironed out.

    So now we known what a gullible idiot would do.

    I for one certainly won't be wasting my money on one any time soon and by the time I am I'll probably be to old to safely get behind a wheel anyway.

    You are driving a twenty-year-old car. Clearly you haven't got any money to waste. If your driving is as confused as your thinking, you shouldn't be allowed to control a shopping trolley, let alone a car.
    It's been very well looked after. I have a lot of servicing and
    maintentance invested in it and I hate to waste anything (shadow of
    WW2 rationing) so I plan to run it for as long as it can safely keep
    going. I've been very pleased with it and nothing out there today
    appeals in the least.

    Where will you get gasoline? It's not like gas stations will be staying open for people like you. By 2040 EVs will be over 95% of the cars on the road, which means only 1 in 20 gas stations will be open. Soon after that, it will be none.
    I'll be long dead by then so quite frankly ICGAS.

    Not sure what your abbreviation means, but you have pointed out the solution to nearly ever issue with EVs. The people complaining about them will be long dead before it's a problem for them. Glad to hear you are in that group.

    --

    Rick C.

    +- Get 1,000 miles of free Supercharging
    +- Tesla referral code - https://ts.la/richard11209

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cursitor Doom@21:1/5 to gnuarm.deletethisbit@gmail.com on Sun Oct 8 22:59:49 2023
    On Sun, 8 Oct 2023 13:20:36 -0700 (PDT), Ricky
    <gnuarm.deletethisbit@gmail.com> wrote:

    On Sunday, October 8, 2023 at 1:15:09?PM UTC-4, Cursitor Doom wrote:
    On Sat, 7 Oct 2023 17:17:37 -0700 (PDT), Ricky
    <gnuarm.del...@gmail.com> wrote:

    On Saturday, October 7, 2023 at 10:49:45?AM UTC-4, Fred Bloggs wrote:
    On Friday, October 6, 2023 at 1:00:27?PM UTC-4, Cursitor Doom wrote:
    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <j...@997arbor.com>
    wrote:
    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <c...@notformail.com>
    wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my
    apartment in San Francisco, across the Golden Gate Bridge, with no
    clutch.
    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained
    regularly. Perhaps it's harder to get the proper spares for them in
    the US.

    English automotive design is excellent, it's the manufacturing that's problematic. And that seems to be the case with a lot of UK industry.

    British automotive design was terrible pretty much anytime after WWII. They lost the financial base to invest in research. So a 1970 British car was pretty much the same as a 1950 British car. Same for the US, except they had the money, just not the
    motivation until the Japanese started eating their lunch because of the reliability problems. The US improved greatly, the British sold their car companies to the real automakers.
    The British are fantastic conceptualists. They come up with the most
    amazing ideas and designs for various things, but are largely hopeless
    at successfully bringing them to market. Many old classic British
    cars that were inspired by fabulous concepts never made the grade
    until they were retro-re-engineered decades later to finally become
    the cars they were *meant* to be back in the day.

    Such as?

    Since they're all ICEs and you hate ICEs, I'll save myself the bother
    of compiling a list you'd only delight in shooting down in flames.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to Cursitor Doom on Sun Oct 8 22:02:10 2023
    On Monday, October 9, 2023 at 9:00:00 AM UTC+11, Cursitor Doom wrote:
    On Sun, 8 Oct 2023 13:20:36 -0700 (PDT), Ricky
    <gnuarm.del...@gmail.com> wrote:
    On Sunday, October 8, 2023 at 1:15:09?PM UTC-4, Cursitor Doom wrote:
    On Sat, 7 Oct 2023 17:17:37 -0700 (PDT), Ricky
    <gnuarm.del...@gmail.com> wrote:

    On Saturday, October 7, 2023 at 10:49:45?AM UTC-4, Fred Bloggs wrote:
    On Friday, October 6, 2023 at 1:00:27?PM UTC-4, Cursitor Doom wrote: >> >> > On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <j...@997arbor.com> >> >> > wrote:
    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <c...@notformail.com>
    wrote:

    Such as?

    Since they're all ICEs and you hate ICEs, I'll save myself the bother of compiling a list you'd only delight in shooting down in flames.

    Cursitor Doom is probably thinking of that quintessentially British car designer

    https://en.wikipedia.org/wiki/Alec_Issigonis

    who was born in Symra and had German connections through his mother.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Ricky on Mon Oct 9 13:28:56 2023
    XPost: free.spam

    The idiot Ricky <gnuarm.deletethisbit@gmail.com> persisting in being an Off-topic troll...

    --
    Ricky <gnuarm.deletethisbit@gmail.com> wrote:

    X-Received: by 2002:ac8:7c53:0:b0:418:fab:2d2d with SMTP id o19-20020ac87c53000000b004180fab2d2dmr187623qtv.11.1696796360111;
    Sun, 08 Oct 2023 13:19:20 -0700 (PDT)
    X-Received: by 2002:a05:6808:1588:b0:3ae:2710:cfa4 with SMTP id
    t8-20020a056808158800b003ae2710cfa4mr7494256oiw.2.1696796359708; Sun, 08 Oct
    2023 13:19:19 -0700 (PDT)
    Path: not-for-mail
    Newsgroups: sci.electronics.design
    Date: Sun, 8 Oct 2023 13:19:19 -0700 (PDT)
    In-Reply-To: <c5o5ii99cqvhidji5f3pmr4l0p31amkdlu@4ax.com>
    Injection-Info: google-groups.googlegroups.com; posting-host=65.207.89.54; posting-account=I-_H_woAAAA9zzro6crtEpUAyIvzd19b
    NNTP-Posting-Host: 65.207.89.54
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    <8jf0ii9jl85b0vudo98mvme728novrvhmi@4ax.com> <5b33a4f3-cf41-44dc-9fc3-d77e540356c4n@googlegroups.com>
    <lae2iihjb4oo6ldsfuh7fglcmm1kjmiu9s@4ax.com> <ea84c32e-5b45-427a-9879-b1768a3053c0n@googlegroups.com>
    <c5o5ii99cqvhidji5f3pmr4l0p31amkdlu@4ax.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <8c9b2398-28e6-438b-9bcc-3a82265d0bffn@googlegroups.com>
    Subject: Re: Another EV goes haywire!
    From: Ricky <gnuarm.deletethisbit@gmail.com>
    Injection-Date: Sun, 08 Oct 2023 20:19:20 +0000
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable
    X-Received-Bytes: 5468

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ricky@21:1/5 to Cursitor Doom on Mon Oct 9 12:11:39 2023
    On Sunday, October 8, 2023 at 6:00:00 PM UTC-4, Cursitor Doom wrote:
    On Sun, 8 Oct 2023 13:20:36 -0700 (PDT), Ricky
    <gnuarm.del...@gmail.com> wrote:
    On Sunday, October 8, 2023 at 1:15:09?PM UTC-4, Cursitor Doom wrote:
    On Sat, 7 Oct 2023 17:17:37 -0700 (PDT), Ricky
    <gnuarm.del...@gmail.com> wrote:

    On Saturday, October 7, 2023 at 10:49:45?AM UTC-4, Fred Bloggs wrote:
    On Friday, October 6, 2023 at 1:00:27?PM UTC-4, Cursitor Doom wrote: >> >> > On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <j...@997arbor.com> >> >> > wrote:
    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <c...@notformail.com>
    wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my
    apartment in San Francisco, across the Golden Gate Bridge, with no >> >> > >clutch.
    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained
    regularly. Perhaps it's harder to get the proper spares for them in >> >> > the US.

    English automotive design is excellent, it's the manufacturing that's problematic. And that seems to be the case with a lot of UK industry.

    British automotive design was terrible pretty much anytime after WWII. They lost the financial base to invest in research. So a 1970 British car was pretty much the same as a 1950 British car. Same for the US, except they had the money, just not
    the motivation until the Japanese started eating their lunch because of the reliability problems. The US improved greatly, the British sold their car companies to the real automakers.
    The British are fantastic conceptualists. They come up with the most
    amazing ideas and designs for various things, but are largely hopeless
    at successfully bringing them to market. Many old classic British
    cars that were inspired by fabulous concepts never made the grade
    until they were retro-re-engineered decades later to finally become
    the cars they were *meant* to be back in the day.

    Such as?
    Since they're all ICEs and you hate ICEs, I'll save myself the bother
    of compiling a list you'd only delight in shooting down in flames.

    That's what I thought. You got nothin'.

    --

    Rick C.

    --- Get 1,000 miles of free Supercharging
    --- Tesla referral code - https://ts.la/richard11209

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Ricky on Mon Oct 9 20:26:57 2023
    XPost: free.spam

    The idiot Ricky <gnuarm.deletethisbit@gmail.com> persisting in being an Off-topic troll...

    --
    Ricky <gnuarm.deletethisbit@gmail.com> wrote:

    X-Received: by 2002:a05:620a:2454:b0:774:c03:557c with SMTP id h20-20020a05620a245400b007740c03557cmr176095qkn.6.1696796437524;
    Sun, 08 Oct 2023 13:20:37 -0700 (PDT)
    X-Received: by 2002:a05:6808:198d:b0:3a3:e17e:d2f7 with SMTP id
    bj13-20020a056808198d00b003a3e17ed2f7mr7018962oib.4.1696796437188; Sun, 08
    Oct 2023 13:20:37 -0700 (PDT)
    Path: not-for-mail
    Newsgroups: sci.electronics.design
    Date: Sun, 8 Oct 2023 13:20:36 -0700 (PDT)
    In-Reply-To: <19o5ii1g6t5lug3lj1ui1i5sv83ak906em@4ax.com>
    Injection-Info: google-groups.googlegroups.com; posting-host=65.207.89.54; posting-account=I-_H_woAAAA9zzro6crtEpUAyIvzd19b
    NNTP-Posting-Host: 65.207.89.54
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <5m80iit7i02me0ebcd9atci7laijvr64pt@4ax.com>
    <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com> <1169b273-74af-468a-b929-86910e486d55n@googlegroups.com>
    <cb64fd42-611d-4f97-b096-62208760a503n@googlegroups.com> <19o5ii1g6t5lug3lj1ui1i5sv83ak906em@4ax.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <58d8ffef-2e8f-4c8e-b3d0-a6293d9e7ca3n@googlegroups.com>
    Subject: Re: Another EV goes haywire!
    From: Ricky <gnuarm.deletethisbit@gmail.com>
    Injection-Date: Sun, 08 Oct 2023 20:20:37 +0000
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable
    X-Received-Bytes: 3915

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Ricky on Mon Oct 9 20:27:03 2023
    XPost: free.spam

    The idiot Ricky <gnuarm.deletethisbit@gmail.com> persisting in being an Off-topic troll...

    --
    Ricky <gnuarm.deletethisbit@gmail.com> wrote:

    X-Received: by 2002:a05:620a:640c:b0:774:143e:f96a with SMTP id pz12-20020a05620a640c00b00774143ef96amr198836qkn.12.1696878700360;
    Mon, 09 Oct 2023 12:11:40 -0700 (PDT)
    X-Received: by 2002:a05:6820:612:b0:56d:72ca:c4dc with SMTP id
    e18-20020a056820061200b0056d72cac4dcmr6366891oow.0.1696878699917; Mon, 09 Oct
    2023 12:11:39 -0700 (PDT)
    Path: not-for-mail
    Newsgroups: sci.electronics.design
    Date: Mon, 9 Oct 2023 12:11:39 -0700 (PDT)
    In-Reply-To: <ge96iip3e0jsi7h2o74ieguj7aipnt30u0@4ax.com>
    Injection-Info: google-groups.googlegroups.com; posting-host=65.207.89.54; posting-account=I-_H_woAAAA9zzro6crtEpUAyIvzd19b
    NNTP-Posting-Host: 65.207.89.54
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <5m80iit7i02me0ebcd9atci7laijvr64pt@4ax.com>
    <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com> <1169b273-74af-468a-b929-86910e486d55n@googlegroups.com>
    <cb64fd42-611d-4f97-b096-62208760a503n@googlegroups.com> <19o5ii1g6t5lug3lj1ui1i5sv83ak906em@4ax.com>
    <58d8ffef-2e8f-4c8e-b3d0-a6293d9e7ca3n@googlegroups.com> <ge96iip3e0jsi7h2o74ieguj7aipnt30u0@4ax.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <2f17cd43-d9af-4ecd-9711-f778a826dcccn@googlegroups.com>
    Subject: Re: Another EV goes haywire!
    From: Ricky <gnuarm.deletethisbit@gmail.com>
    Injection-Date: Mon, 09 Oct 2023 19:11:40 +0000
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable
    X-Received-Bytes: 4522

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Cursitor Doom on Mon Oct 9 20:27:28 2023
    XPost: free.spam

    The idiot Cursitor Doom <cd@notformail.com> persisting in being an Off-topic troll...

    --
    Cursitor Doom <cd@notformail.com> wrote:

    Path: not-for-mail
    From: Cursitor Doom <cd@notformail.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Sun, 08 Oct 2023 22:59:49 +0100
    Organization: A noiseless patient Spider
    Lines: 45
    Message-ID: <ge96iip3e0jsi7h2o74ieguj7aipnt30u0@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <5m80iit7i02me0ebcd9atci7laijvr64pt@4ax.com> <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com> <1169b273-74af-468a-b929-86910e486d55n@googlegroups.com> <cb64fd42-611d-4f97-b096-62208760a503n@
    googlegroups.com> <19o5ii1g6t5lug3lj1ui1i5sv83ak906em@4ax.com> <58d8ffef-2e8f-4c8e-b3d0-a6293d9e7ca3n@googlegroups.com>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Injection-Info: dont-email.me; posting-host="7c6e0630c4c2b1863232d79951c964bb";
    logging-data="3524016"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/IT44VbyTDjw4VlAdO9J9jZr3eim+GlZ0="
    User-Agent: ForteAgent/8.00.32.1272
    Cancel-Lock: sha1:QPciTNk3crO16QqSgeQWSG/H8Hk=
    X-Received-Bytes: 3757

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cursitor Doom@21:1/5 to gnuarm.deletethisbit@gmail.com on Mon Oct 9 22:48:26 2023
    On Mon, 9 Oct 2023 12:11:39 -0700 (PDT), Ricky
    <gnuarm.deletethisbit@gmail.com> wrote:

    On Sunday, October 8, 2023 at 6:00:00?PM UTC-4, Cursitor Doom wrote:
    On Sun, 8 Oct 2023 13:20:36 -0700 (PDT), Ricky
    <gnuarm.del...@gmail.com> wrote:
    On Sunday, October 8, 2023 at 1:15:09?PM UTC-4, Cursitor Doom wrote:
    On Sat, 7 Oct 2023 17:17:37 -0700 (PDT), Ricky
    <gnuarm.del...@gmail.com> wrote:

    On Saturday, October 7, 2023 at 10:49:45?AM UTC-4, Fred Bloggs wrote:
    On Friday, October 6, 2023 at 1:00:27?PM UTC-4, Cursitor Doom wrote: >> >> >> > On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <j...@997arbor.com> >> >> >> > wrote:
    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <c...@notformail.com>
    wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my
    apartment in San Francisco, across the Golden Gate Bridge, with no >> >> >> > >clutch.
    Are you talking about MGs - or "MGs" (the ones made nowadays in
    China).
    Classic MGs rarely give any trouble provided they're maintained
    regularly. Perhaps it's harder to get the proper spares for them in >> >> >> > the US.

    English automotive design is excellent, it's the manufacturing that's problematic. And that seems to be the case with a lot of UK industry.

    British automotive design was terrible pretty much anytime after WWII. They lost the financial base to invest in research. So a 1970 British car was pretty much the same as a 1950 British car. Same for the US, except they had the money, just not
    the motivation until the Japanese started eating their lunch because of the reliability problems. The US improved greatly, the British sold their car companies to the real automakers.
    The British are fantastic conceptualists. They come up with the most
    amazing ideas and designs for various things, but are largely hopeless
    at successfully bringing them to market. Many old classic British
    cars that were inspired by fabulous concepts never made the grade
    until they were retro-re-engineered decades later to finally become
    the cars they were *meant* to be back in the day.

    Such as?
    Since they're all ICEs and you hate ICEs, I'll save myself the bother
    of compiling a list you'd only delight in shooting down in flames.

    That's what I thought. You got nothin'.

    I've got nothing for YOU.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ricky@21:1/5 to Cursitor Doom on Mon Oct 9 16:37:49 2023
    On Monday, October 9, 2023 at 5:48:34 PM UTC-4, Cursitor Doom wrote:
    On Mon, 9 Oct 2023 12:11:39 -0700 (PDT), Ricky
    <gnuarm.del...@gmail.com> wrote:
    On Sunday, October 8, 2023 at 6:00:00?PM UTC-4, Cursitor Doom wrote:
    On Sun, 8 Oct 2023 13:20:36 -0700 (PDT), Ricky
    <gnuarm.del...@gmail.com> wrote:
    On Sunday, October 8, 2023 at 1:15:09?PM UTC-4, Cursitor Doom wrote:
    On Sat, 7 Oct 2023 17:17:37 -0700 (PDT), Ricky
    <gnuarm.del...@gmail.com> wrote:

    On Saturday, October 7, 2023 at 10:49:45?AM UTC-4, Fred Bloggs wrote: >> >> >> On Friday, October 6, 2023 at 1:00:27?PM UTC-4, Cursitor Doom wrote:
    On Fri, 06 Oct 2023 08:12:32 -0700, John Larkin <j...@997arbor.com>
    wrote:
    On Fri, 06 Oct 2023 14:12:20 +0100, Cursitor Doom <c...@notformail.com>
    wrote:

    Ban them!

    https://tinyurl.com/2cjun8v7

    "MG malfunctioned" is perfectly normal. That's not news.

    I wish my MGs would have kept going at 15 MPH.

    I did once make it from the top of Mt Tamalpias back home to my >> >> >> > >apartment in San Francisco, across the Golden Gate Bridge, with no
    clutch.
    Are you talking about MGs - or "MGs" (the ones made nowadays in >> >> >> > China).
    Classic MGs rarely give any trouble provided they're maintained >> >> >> > regularly. Perhaps it's harder to get the proper spares for them in
    the US.

    English automotive design is excellent, it's the manufacturing that's problematic. And that seems to be the case with a lot of UK industry.

    British automotive design was terrible pretty much anytime after WWII. They lost the financial base to invest in research. So a 1970 British car was pretty much the same as a 1950 British car. Same for the US, except they had the money, just not
    the motivation until the Japanese started eating their lunch because of the reliability problems. The US improved greatly, the British sold their car companies to the real automakers.
    The British are fantastic conceptualists. They come up with the most >> >> amazing ideas and designs for various things, but are largely hopeless >> >> at successfully bringing them to market. Many old classic British
    cars that were inspired by fabulous concepts never made the grade
    until they were retro-re-engineered decades later to finally become
    the cars they were *meant* to be back in the day.

    Such as?
    Since they're all ICEs and you hate ICEs, I'll save myself the bother
    of compiling a list you'd only delight in shooting down in flames.

    That's what I thought. You got nothin'.
    I've got nothing for YOU.

    Exactly. You say things, then can't back them up.

    --

    Rick C.

    --+ Get 1,000 miles of free Supercharging
    --+ Tesla referral code - https://ts.la/richard11209

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Flyguy@21:1/5 to Anthony William Sloman on Mon Oct 9 19:46:59 2023
    On Friday, October 6, 2023 at 6:52:59 AM UTC-7, Anthony William Sloman wrote:
    On Saturday, October 7, 2023 at 12:12:31 AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.

    I would MUCH RATHER BAN YOU, who insults and attacks other posters on SED without merit.
    <snip more Bozo bullshit>

    Bozo Bill Slowman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Flyguy on Tue Oct 10 02:53:52 2023
    XPost: free.spam

    The idiot Flyguy <soar2morrow@yahoo.com> persisting in being an Off-topic troll...

    --
    Flyguy <soar2morrow@yahoo.com> wrote:

    X-Received: by 2002:a05:622a:1051:b0:419:6cf4:247d with SMTP id f17-20020a05622a105100b004196cf4247dmr265279qte.10.1696906020335;
    Mon, 09 Oct 2023 19:47:00 -0700 (PDT)
    X-Received: by 2002:a05:6808:1809:b0:3ac:a02d:708f with SMTP id
    bh9-20020a056808180900b003aca02d708fmr9030963oib.1.1696906020073; Mon, 09 Oct
    2023 19:47:00 -0700 (PDT)
    Path: not-for-mail
    Newsgroups: sci.electronics.design
    Date: Mon, 9 Oct 2023 19:46:59 -0700 (PDT)
    In-Reply-To: <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com> Injection-Info: google-groups.googlegroups.com; posting-host=2600:6c54:5300:6aee:ad1c:70a4:66e8:127e;
    posting-account=igyo_woAAAAxdxQHjAB2cSS7_KQghTOv
    NNTP-Posting-Host: 2600:6c54:5300:6aee:ad1c:70a4:66e8:127e
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <8a55554a-63c0-4bad-b34e-7c9359c6aad7n@googlegroups.com>
    Subject: Re: Another EV goes haywire!
    From: Flyguy <soar2morrow@yahoo.com>
    Injection-Date: Tue, 10 Oct 2023 02:47:00 +0000
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable
    X-Received-Bytes: 1948

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Ricky on Tue Oct 10 02:53:58 2023
    XPost: free.spam

    The arsehole Ricky <gnuarm.deletethisbit@gmail.com> persisting in being an Off-topic troll...

    --
    Ricky <gnuarm.deletethisbit@gmail.com> wrote:

    X-Received: by 2002:a05:620a:3f04:b0:770:7460:c3f6 with SMTP id tx4-20020a05620a3f0400b007707460c3f6mr193505qkn.6.1696894670223;
    Mon, 09 Oct 2023 16:37:50 -0700 (PDT)
    X-Received: by 2002:a05:6808:2382:b0:3a7:2434:615a with SMTP id
    bp2-20020a056808238200b003a72434615amr8623618oib.4.1696894669937; Mon, 09 Oct
    2023 16:37:49 -0700 (PDT)
    Path: not-for-mail
    Newsgroups: sci.electronics.design
    Date: Mon, 9 Oct 2023 16:37:49 -0700 (PDT)
    In-Reply-To: <n8t8iilq4n8gjp0t73r25n3skg509p06ev@4ax.com>
    Injection-Info: google-groups.googlegroups.com; posting-host=65.207.89.54; posting-account=I-_H_woAAAA9zzro6crtEpUAyIvzd19b
    NNTP-Posting-Host: 65.207.89.54
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <5m80iit7i02me0ebcd9atci7laijvr64pt@4ax.com>
    <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com> <1169b273-74af-468a-b929-86910e486d55n@googlegroups.com>
    <cb64fd42-611d-4f97-b096-62208760a503n@googlegroups.com> <19o5ii1g6t5lug3lj1ui1i5sv83ak906em@4ax.com>
    <58d8ffef-2e8f-4c8e-b3d0-a6293d9e7ca3n@googlegroups.com> <ge96iip3e0jsi7h2o74ieguj7aipnt30u0@4ax.com>
    <2f17cd43-d9af-4ecd-9711-f778a826dcccn@googlegroups.com> <n8t8iilq4n8gjp0t73r25n3skg509p06ev@4ax.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <497c89c6-ff63-4c4a-8350-4b60691f34b8n@googlegroups.com>
    Subject: Re: Another EV goes haywire!
    From: Ricky <gnuarm.deletethisbit@gmail.com>
    Injection-Date: Mon, 09 Oct 2023 23:37:50 +0000
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable
    X-Received-Bytes: 5038

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Cursitor Doom on Tue Oct 10 02:54:23 2023
    XPost: free.spam

    The idiot Cursitor Doom <cd@notformail.com> persisting in being an Off-topic troll...

    --
    Cursitor Doom <cd@notformail.com> wrote:

    Path: not-for-mail
    From: Cursitor Doom <cd@notformail.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Mon, 09 Oct 2023 22:48:26 +0100
    Organization: A noiseless patient Spider
    Lines: 51
    Message-ID: <n8t8iilq4n8gjp0t73r25n3skg509p06ev@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <5m80iit7i02me0ebcd9atci7laijvr64pt@4ax.com> <26f0ii96gmna9s0tenpm65vrk6h8v249hk@4ax.com> <1169b273-74af-468a-b929-86910e486d55n@googlegroups.com> <cb64fd42-611d-4f97-b096-62208760a503n@
    googlegroups.com> <19o5ii1g6t5lug3lj1ui1i5sv83ak906em@4ax.com> <58d8ffef-2e8f-4c8e-b3d0-a6293d9e7ca3n@googlegroups.com> <ge96iip3e0jsi7h2o74ieguj7aipnt30u0@4ax.com> <2f17cd43-d9af-4ecd-9711-f778a826dcccn@googlegroups.com>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Injection-Info: dont-email.me; posting-host="0dd09fceac5526355ce7c06e16d93dd1";
    logging-data="164475"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19YphZeqR/4z3Eu5VEFeZSq4Uql9YJQhVU="
    User-Agent: ForteAgent/8.00.32.1272
    Cancel-Lock: sha1:9rp11+vGZsrZgfIrClf4ljQtNh0=
    X-Received-Bytes: 4197

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to Flyguy on Mon Oct 9 21:52:46 2023
    On Tuesday, October 10, 2023 at 1:47:04 PM UTC+11, Flyguy wrote:
    On Friday, October 6, 2023 at 6:52:59 AM UTC-7, Anthony William Sloman wrote:
    On Saturday, October 7, 2023 at 12:12:31 AM UTC+11, Cursitor Doom wrote:
    Ban them!

    https://tinyurl.com/2cjun8v7

    Why not ban Cursitor Doom? There's nothing specific to electric cars that makes them any more prone to have their control systems go haywire than internal combustion-engined cars.

    I would MUCH RATHER BAN YOU, who insults and attacks other posters on SED without merit.

    If the other posters lack merit, they shouldn't be posting here.

    Your capacity for assessing merit does seem to be flawed - you think that Donald trump handled the Covid-19 pandemic in the US well, when the country ended up with 3,463 deaths per million population - 15th in the rank order, but remarkably high for a
    rich country. The UK did almost as badly, but they had Boris Johnson in charge who is an equally toxic clown.

    _
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Don Y on Tue Oct 10 13:20:52 2023
    On 06/10/2023 21:39, Don Y wrote:
    On 10/6/2023 1:33 PM, Don Y wrote:
    [I've been given specs with obvious incompatibilities -- that the
    author hadn't seen just because he was too close to the problem
    and had too many baked in assumptions:  "Here, imagine THIS
    happening..."]

    Sadly, no one teaches folks how to write (and challenge) good
    specifications (hardware, software, system).  And, few folks have
    an interest in developing that skillset.

    I had a reputation for breaking software and being able to guess
    situations where there might be weak points. It was something I often
    did on Friday afternoons.
    A colleague was designing a video scaler.  And the design was almost
    ready to head off to the foundry!  I pointed out that RS170 video
    scaled to a *smaller* image in the "enlarged" setting than in the
    "normal" setting.  (WTF?)

    How did the design get that far along without anyone challenging
    it with real-life situations??

    It is amazing what escapes into the real world. Certain famous brand TVs
    of a particular era ~10 years ago now had MPEG decoders with one set of coefficients for the dynamic updates reversed. Amazingly it hardly ever
    showed up as a problem IRL except on the edges of news desks when the
    camera panned slowly across and the angle was close to a compass point.

    The previously sharp edge would break up into a sawtooth as the camera
    panned across the scene. The error was made in every 8x8 block. You had
    to be close enough to see that level of detail before it was obvious. It
    was never clear to me if it was an upscaling fault in the SD to HD part
    or in the final output stage. The effect was much less offensive on HD.

    I-frames were correctly decoded and it was only the dynamic movement
    updates that had a part of the coefficient table scrambled. It slightly
    showed up on water sports too since small globs of water spray instead
    of being approximately round would look like stellated icosahedra!

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Larkin@21:1/5 to '''newspam'''@nonad.co.uk on Tue Oct 10 06:53:43 2023
    On Tue, 10 Oct 2023 13:20:52 +0100, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 06/10/2023 21:39, Don Y wrote:
    On 10/6/2023 1:33 PM, Don Y wrote:
    [I've been given specs with obvious incompatibilities -- that the
    author hadn't seen just because he was too close to the problem
    and had too many baked in assumptions:  "Here, imagine THIS
    happening..."]

    Sadly, no one teaches folks how to write (and challenge) good
    specifications (hardware, software, system).  And, few folks have
    an interest in developing that skillset.

    I had a reputation for breaking software and being able to guess
    situations where there might be weak points. It was something I often
    did on Friday afternoons.

    One of my jobs is to do that for hardware, to review a design and find
    where it will break.

    Hardware is a lot more expensive to fix than software.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to John Larkin on Tue Oct 10 07:04:02 2023
    On Wednesday, October 11, 2023 at 12:54:02 AM UTC+11, John Larkin wrote:
    On Tue, 10 Oct 2023 13:20:52 +0100, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 06/10/2023 21:39, Don Y wrote:
    On 10/6/2023 1:33 PM, Don Y wrote:
    [I've been given specs with obvious incompatibilities -- that the
    author hadn't seen just because he was too close to the problem
    and had too many baked in assumptions: "Here, imagine THIS
    happening..."]

    Sadly, no one teaches folks how to write (and challenge) good
    specifications (hardware, software, system). And, few folks have
    an interest in developing that skillset.

    I had a reputation for breaking software and being able to guess >situations where there might be weak points. It was something I often
    did on Friday afternoons.
    One of my jobs is to do that for hardware, to review a design and find
    where it will break.

    Hardware is a lot more expensive to fix than software.

    Not exactly. Once you have worked out what has gone wrong and devised a fix you can remotely download revised software, and that part of the fix is cheap.

    Finding a defect in software that occasionally behaves badly is difficult, expensive and time consuming, in much the same way as finding intermittent faults in hardware.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Martin Brown on Tue Oct 10 10:05:44 2023
    On 10/10/2023 5:20 AM, Martin Brown wrote:
    On 06/10/2023 21:39, Don Y wrote:
    On 10/6/2023 1:33 PM, Don Y wrote:
    [I've been given specs with obvious incompatibilities -- that the
    author hadn't seen just because he was too close to the problem
    and had too many baked in assumptions:  "Here, imagine THIS happening..."] >>>
    Sadly, no one teaches folks how to write (and challenge) good
    specifications (hardware, software, system).  And, few folks have
    an interest in developing that skillset.

    I had a reputation for breaking software and being able to guess situations where there might be weak points. It was something I often did on Friday afternoons.

    I am distressed at how many "obvious" flaws creep into software.
    E.g., if you expect something from the user, try hitting
    "ENTER" (or equivalent) all by itself. Or, "CLEAR" then "ENTER".
    Or, <stuff> followed by "CLEAR" then "ENTER". Do the results differ?
    Should they? Do they "make sense"? Amazing how many times an "empty" buffer/accumulator gets passed as the "entered value"! Or, worse,
    an uninitialized buffer (because the developer thought the user was
    going to type <stuff>! All this before even *checking* for values
    out of limits...

    Races are another problem ripe for picking. No, nothing takes
    zero time; are you sure the code doesn't silently rely on this?

    [Our new oven has many races. It wasn't hard to imagine it
    would because the UI controls multiple concurrent processes
    for a "human speed" operator/cook!]

    As I said, none of these really require any deliberate thought
    to "tickle". So, why hadn't they been tested previously?

    Contrast that with more aggressive challenges (like unplugging
    parts of the system while using it to see how it will react).

    Hardware is relatively easy to test -- does it operate IN
    a given set of conditions. Software has more "situations"
    in which it can be stressed -- because it has to deal with
    *sequences*. (Do something out of the expected sequence
    and you can tickle a bug; COMPLY with that sequence and
    you likely won't!)

    "Big Projects" are often decomposed (by some "system architect")
    and doled out in smaller chunks to individuals/teams. They
    are never shown the whole picture -- because there is no need
    for them to be exposed to all of that complexity.

    But, as a result, they can't imagine flaws in how their
    subassembly will be used. So, they can't comment on flaws in
    the specification FOR THEIR SUBASSEMBLY! (E.g., I'm sure
    the dweeb who coded the UI in our oven followed everything
    to the letter... it wasn't HIS task to deal with how those
    concurrent processes would use his UI; shirley, someone
    "higher up" would have thought of all that, right?)

    Imagine being SHOWN just "your corner" of a schematic
    and expected to comment on a flaw in some other portion!

    But, the whole "challenge" aspect of the specification
    is missing (in formal instruction). Nowadays, there
    isn't even a formal specification phase (waterfall)
    but, rather, an incremental "No, that's not what we
    wanted" approach (agile).

    In hardware designs, you worry about not exceeding limits
    of any individual component, SOA, thermal effects, etc.
    And, can *see* everything in the design (I've worked on
    designs with many hundred page schematics but could still
    grok the design in its entirety; that's not true for
    100 pages of code!)

    [Amusingly, this provides lots of opportunities to
    *protect* code from theft/alteration as even determined
    observers often can't see subtle interrelationships
    embedded therein!]

    And, if "someone else" has assumed the responsibility for
    the design, do *you* take it on yourself to double-check
    the dotted i's and crossed t's?

    E.g., in the scaler example, below, I only stumbled on the design
    flaw because I was trying to understand the algorithm that the
    hardware implemented and RS170 is so "off the top of your head"
    that it provided obvious parameters to plug into the design:

    "Gee, this doesn't make sense..."

    Failing to catch it would have cost us another turn of the crank
    (about 6 weeks at the foundry) and "a year's salary" -- assuming
    we did catch it before release. Software bugs? Considerably
    more expensive to find and correct!

    [Robotron 2084 was plagued with a "problem" that would manifest
    in "enforcer waves": killing them in a corner of the play field
    would often cause the game to spontaneously reboot! Not something
    that a player would enjoy experiencing: "Crap, I was having a
    REALLY good game!" There was a fair bit of discussion as to whether
    this was a software bug or a hardware bug (Robotron was the first game
    to use a full-custom BLTer that we had designed... was there a
    problem in THAT design?). How long do you delay releasing the
    game IN A TIME_SENSITIVE MARKET just to resolve this problem?
    Do the hardware and software folks have a SAY in that decision??]

    A colleague was designing a video scaler.  And the design was almost
    ready to head off to the foundry!  I pointed out that RS170 video
    scaled to a *smaller* image in the "enlarged" setting than in the
    "normal" setting.  (WTF?)

    How did the design get that far along without anyone challenging
    it with real-life situations??

    It is amazing what escapes into the real world. Certain famous brand TVs of a particular era ~10 years ago now had MPEG decoders with one set of coefficients
    for the dynamic updates reversed. Amazingly it hardly ever showed up as a problem IRL except on the edges of news desks when the camera panned slowly across and the angle was close to a compass point.

    The previously sharp edge would break up into a sawtooth as the camera panned across the scene. The error was made in every 8x8 block. You had to be close enough to see that level of detail before it was obvious. It was never clear to
    me if it was an upscaling fault in the SD to HD part or in the final output stage. The effect was much less offensive on HD.

    Because the developers didn't have any sample video to run through the
    decoder? (Really?? <rolls eyes>)

    In big companies, testing is often done by someone other than the
    developer. So, you have to hope they know what to look for in
    those tests and don't just run through the motions.

    When I started using FOSS OSs (almost exactly 30 years ago?),
    I would install precompiled "packages" (why spend time building
    from source?). I recall installing a prebuilt gnuplot(1).
    And, running the COMPREHENSIVE test suite just to see what it
    could do. Until I came to a series of CDFs, one of which
    wasn't "monotonically increasing to 1.0"! WTF? Shirley the
    guy who built this package would have run the test suite...
    how could he have NOT seen this error? (Ans: he didn't
    understand WHAT he should have seen so didn't recognize that
    the test had failed!)

    [Thereafter, I took it upon myself to build all packages
    from source so *I* could see the messages emitted and
    decide which were significant -- the above fault threw
    a compiler warning that was apparently ignored!]

    I-frames were correctly decoded and it was only the dynamic movement updates that had a part of the coefficient table scrambled. It slightly showed up on water sports too since small globs of water spray instead of being approximately round would look like stellated icosahedra!

    Presumably, the "output" could be redirected to compare it to
    the *expected* output, instead of relying on human eyes to
    "notice" these artifacts.

    Testing is so often an afterthought. Why wasn't the scaffolding in
    place to make this a more robust process?

    [The same applies, in spades, to security issues!]

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Martin Brown on Tue Oct 10 18:23:11 2023
    XPost: free.spam

    The arsehole Martin Brown <'''newspam'''@nonad.co.uk> persisting in being an Off-topic troll...

    --
    Martin Brown <'''newspam'''@nonad.co.uk> wrote:

    Path: not-for-mail
    From: Martin Brown <'''newspam'''@nonad.co.uk>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Tue, 10 Oct 2023 13:20:52 +0100
    Organization: A noiseless patient Spider
    Lines: 42
    Message-ID: <ug3fj5$14jm9$1@dont-email.me>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com>
    <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    <ufpjoj$1rduc$1@dont-email.me> <ufpqv8$1so3a$3@dont-email.me>
    <ufprab$1so3a$4@dont-email.me>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit
    Injection-Date: Tue, 10 Oct 2023 12:20:53 -0000 (UTC)
    Injection-Info: dont-email.me; posting-host="e1b21eb8cd8b8ea7d9e31edc46a9703a";
    logging-data="1199817"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/WkArDgxN96dUFxNX72VwG1n50esrsrCjp84VrA8YqLA=="
    User-Agent: Mozilla Thunderbird
    Cancel-Lock: sha1:8qJ+qmM/CDByhnxnYKfS5IKFdJs=
    In-Reply-To: <ufprab$1so3a$4@dont-email.me>
    Content-Language: en-GB
    X-Received-Bytes: 3315

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to John Larkin on Tue Oct 10 18:23:17 2023
    XPost: free.spam

    The arsehole John Larkin <jl@997PotHill.com> persisting in being an Off-topic troll...

    --
    John Larkin <jl@997PotHill.com> wrote:

    Path: not-for-mail
    NNTP-Posting-Date: Tue, 10 Oct 2023 13:53:45 +0000
    From: John Larkin <jl@997PotHill.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Tue, 10 Oct 2023 06:53:43 -0700
    Organization: Highland Tech
    Reply-To: xx@yy.com
    Message-ID: <2nlaii1lahlb7utev0q7o3drd0e2iavo6r@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com> <ufpjoj$1rduc$1@dont-email.me> <ufpqv8$1so3a$3@dont-email.me> <ufprab$1so3a$4@dont-email.me> <ug3fj5$14jm9$1@dont-email.me>
    X-Newsreader: Forte Agent 3.1/32.783
    MIME-Version: 1.0
    Content-Type: text/plain; charset=ISO-8859-1
    Content-Transfer-Encoding: 8bit
    Lines: 23
    X-Trace: sv3-LDA2IuXmYgj405vMhaxfQ3T+sZrXpbcQSFO6DzxHcjwHJGJN+h/1rv6iI5QaadWD4jJB+l3NUTFLQIj!/FVWM7kmRV+Egy+InAnxfTOw31VDopRNTWGiOUBRUqHPTl7e0emJEo8sTKv7Y0Smkj+F4wBCjzub!cr+lvQ==
    X-Complaints-To: www.supernews.com/docs/abuse.html
    X-DMCA-Complaints-To: www.supernews.com/docs/dmca.html
    X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
    X-Postfilter: 1.3.40
    Bytes: 2169
    X-Received-Bytes: 2369

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Don Y on Tue Oct 10 18:24:28 2023
    XPost: free.spam

    The idiot Don Y <blockedofcourse@foo.invalid> persisting in being an Off-topic troll...

    --
    Don Y <blockedofcourse@foo.invalid> wrote:

    Path: not-for-mail
    From: Don Y <blockedofcourse@foo.invalid>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Tue, 10 Oct 2023 10:05:44 -0700
    Organization: A noiseless patient Spider
    Lines: 165
    Message-ID: <ug4099$18jf9$1@dont-email.me>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com>
    <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    <ufpjoj$1rduc$1@dont-email.me> <ufpqv8$1so3a$3@dont-email.me>
    <ufprab$1so3a$4@dont-email.me> <ug3fj5$14jm9$1@dont-email.me>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit
    Injection-Date: Tue, 10 Oct 2023 17:05:46 -0000 (UTC)
    Injection-Info: dont-email.me; posting-host="389e4fe0e851b937058a07b7fdd8b4d1";
    logging-data="1330665"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18fOEbsUHX9jB2DLP8AMWWf"
    User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101
    Thunderbird/102.2.2
    Cancel-Lock: sha1:YviHetCX0rGWYzqQw7nP0YHNKfQ=
    In-Reply-To: <ug3fj5$14jm9$1@dont-email.me>
    Content-Language: en-US
    X-Received-Bytes: 9125

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From john larkin@21:1/5 to blockedofcourse@foo.invalid on Tue Oct 10 12:05:53 2023
    On Tue, 10 Oct 2023 10:05:44 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    On 10/10/2023 5:20 AM, Martin Brown wrote:
    On 06/10/2023 21:39, Don Y wrote:
    On 10/6/2023 1:33 PM, Don Y wrote:
    [I've been given specs with obvious incompatibilities -- that the
    author hadn't seen just because he was too close to the problem
    and had too many baked in assumptions:  "Here, imagine THIS happening..."] >>>>
    Sadly, no one teaches folks how to write (and challenge) good
    specifications (hardware, software, system).  And, few folks have
    an interest in developing that skillset.

    I had a reputation for breaking software and being able to guess situations >> where there might be weak points. It was something I often did on Friday
    afternoons.

    I am distressed at how many "obvious" flaws creep into software.
    E.g., if you expect something from the user, try hitting
    "ENTER" (or equivalent) all by itself. Or, "CLEAR" then "ENTER".
    Or, <stuff> followed by "CLEAR" then "ENTER". Do the results differ?
    Should they? Do they "make sense"? Amazing how many times an "empty" >buffer/accumulator gets passed as the "entered value"! Or, worse,
    an uninitialized buffer (because the developer thought the user was
    going to type <stuff>! All this before even *checking* for values
    out of limits...

    Races are another problem ripe for picking. No, nothing takes
    zero time; are you sure the code doesn't silently rely on this?

    [Our new oven has many races. It wasn't hard to imagine it
    would because the UI controls multiple concurrent processes
    for a "human speed" operator/cook!]

    As I said, none of these really require any deliberate thought
    to "tickle". So, why hadn't they been tested previously?

    Contrast that with more aggressive challenges (like unplugging
    parts of the system while using it to see how it will react).

    Hardware is relatively easy to test -- does it operate IN
    a given set of conditions. Software has more "situations"
    in which it can be stressed -- because it has to deal with
    *sequences*. (Do something out of the expected sequence
    and you can tickle a bug; COMPLY with that sequence and
    you likely won't!)

    "Big Projects" are often decomposed (by some "system architect")
    and doled out in smaller chunks to individuals/teams. They
    are never shown the whole picture -- because there is no need
    for them to be exposed to all of that complexity.

    But, as a result, they can't imagine flaws in how their
    subassembly will be used. So, they can't comment on flaws in
    the specification FOR THEIR SUBASSEMBLY! (E.g., I'm sure
    the dweeb who coded the UI in our oven followed everything
    to the letter... it wasn't HIS task to deal with how those
    concurrent processes would use his UI; shirley, someone
    "higher up" would have thought of all that, right?)

    Imagine being SHOWN just "your corner" of a schematic
    and expected to comment on a flaw in some other portion!

    But, the whole "challenge" aspect of the specification
    is missing (in formal instruction). Nowadays, there
    isn't even a formal specification phase (waterfall)
    but, rather, an incremental "No, that's not what we
    wanted" approach (agile).

    In hardware designs, you worry about not exceeding limits
    of any individual component, SOA, thermal effects, etc.
    And, can *see* everything in the design (I've worked on
    designs with many hundred page schematics but could still
    grok the design in its entirety; that's not true for
    100 pages of code!)

    [Amusingly, this provides lots of opportunities to
    *protect* code from theft/alteration as even determined
    observers often can't see subtle interrelationships
    embedded therein!]

    And, if "someone else" has assumed the responsibility for
    the design, do *you* take it on yourself to double-check
    the dotted i's and crossed t's?

    E.g., in the scaler example, below, I only stumbled on the design
    flaw because I was trying to understand the algorithm that the
    hardware implemented and RS170 is so "off the top of your head"
    that it provided obvious parameters to plug into the design:

    "Gee, this doesn't make sense..."

    Failing to catch it would have cost us another turn of the crank
    (about 6 weeks at the foundry) and "a year's salary" -- assuming
    we did catch it before release. Software bugs? Considerably
    more expensive to find and correct!

    [Robotron 2084 was plagued with a "problem" that would manifest
    in "enforcer waves": killing them in a corner of the play field
    would often cause the game to spontaneously reboot! Not something
    that a player would enjoy experiencing: "Crap, I was having a
    REALLY good game!" There was a fair bit of discussion as to whether
    this was a software bug or a hardware bug (Robotron was the first game
    to use a full-custom BLTer that we had designed... was there a
    problem in THAT design?). How long do you delay releasing the
    game IN A TIME_SENSITIVE MARKET just to resolve this problem?
    Do the hardware and software folks have a SAY in that decision??]

    A colleague was designing a video scaler.  And the design was almost
    ready to head off to the foundry!  I pointed out that RS170 video
    scaled to a *smaller* image in the "enlarged" setting than in the
    "normal" setting.  (WTF?)

    How did the design get that far along without anyone challenging
    it with real-life situations??

    It is amazing what escapes into the real world. Certain famous brand TVs of a
    particular era ~10 years ago now had MPEG decoders with one set of coefficients
    for the dynamic updates reversed. Amazingly it hardly ever showed up as a
    problem IRL except on the edges of news desks when the camera panned slowly >> across and the angle was close to a compass point.

    The previously sharp edge would break up into a sawtooth as the camera panned
    across the scene. The error was made in every 8x8 block. You had to be close >> enough to see that level of detail before it was obvious. It was never clear to
    me if it was an upscaling fault in the SD to HD part or in the final output >> stage. The effect was much less offensive on HD.

    Because the developers didn't have any sample video to run through the >decoder? (Really?? <rolls eyes>)

    In big companies, testing is often done by someone other than the
    developer. So, you have to hope they know what to look for in
    those tests and don't just run through the motions.

    When I started using FOSS OSs (almost exactly 30 years ago?),
    I would install precompiled "packages" (why spend time building
    from source?). I recall installing a prebuilt gnuplot(1).
    And, running the COMPREHENSIVE test suite just to see what it
    could do. Until I came to a series of CDFs, one of which
    wasn't "monotonically increasing to 1.0"! WTF? Shirley the
    guy who built this package would have run the test suite...
    how could he have NOT seen this error? (Ans: he didn't
    understand WHAT he should have seen so didn't recognize that
    the test had failed!)

    [Thereafter, I took it upon myself to build all packages
    from source so *I* could see the messages emitted and
    decide which were significant -- the above fault threw
    a compiler warning that was apparently ignored!]

    I-frames were correctly decoded and it was only the dynamic movement updates >> that had a part of the coefficient table scrambled. It slightly showed up on >> water sports too since small globs of water spray instead of being
    approximately round would look like stellated icosahedra!

    Presumably, the "output" could be redirected to compare it to
    the *expected* output, instead of relying on human eyes to
    "notice" these artifacts.

    Testing is so often an afterthought. Why wasn't the scaffolding in
    place to make this a more robust process?

    [The same applies, in spades, to security issues!]



    We live in the Dark Ages of computer programming. It's like when
    people built cathedrals in the year 900... try it and see if it falls
    down.

    Sad to say, but few people can program responsibly. They need a
    LabView sort of box dragger. With that, a competant admin would create
    better programs.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From three_jeeps@21:1/5 to John Larkin on Tue Oct 10 12:27:05 2023
    On Tuesday, October 10, 2023 at 9:54:02 AM UTC-4, John Larkin wrote:
    On Tue, 10 Oct 2023 13:20:52 +0100, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 06/10/2023 21:39, Don Y wrote:
    On 10/6/2023 1:33 PM, Don Y wrote:
    [I've been given specs with obvious incompatibilities -- that the
    author hadn't seen just because he was too close to the problem
    and had too many baked in assumptions: "Here, imagine THIS
    happening..."]

    Sadly, no one teaches folks how to write (and challenge) good
    specifications (hardware, software, system). And, few folks have
    an interest in developing that skillset.

    I had a reputation for breaking software and being able to guess >situations where there might be weak points. It was something I often
    did on Friday afternoons.
    One of my jobs is to do that for hardware, to review a design and find
    where it will break.

    Hardware is a lot more expensive to fix than software.
    It depends on the context. I have read and have written reports that cite statistics that software rework can be more expensive than hardware rework. Studies have shown that removing a software defect during integration or acceptance testing cost
    anywhere from 50% to 400% removal cost if it was removed early in the development lifecycle, e.g. requirements analysis, architecture analysis. This is a big deal in software-intensive systems where software provides 70%-90% of the functionality.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From john larkin@21:1/5 to jjhudak@gmail.com on Tue Oct 10 13:20:05 2023
    On Tue, 10 Oct 2023 12:27:05 -0700 (PDT), three_jeeps
    <jjhudak@gmail.com> wrote:

    On Tuesday, October 10, 2023 at 9:54:02?AM UTC-4, John Larkin wrote:
    On Tue, 10 Oct 2023 13:20:52 +0100, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 06/10/2023 21:39, Don Y wrote:
    On 10/6/2023 1:33 PM, Don Y wrote:
    [I've been given specs with obvious incompatibilities -- that the
    author hadn't seen just because he was too close to the problem
    and had too many baked in assumptions: "Here, imagine THIS
    happening..."]

    Sadly, no one teaches folks how to write (and challenge) good
    specifications (hardware, software, system). And, few folks have
    an interest in developing that skillset.

    I had a reputation for breaking software and being able to guess
    situations where there might be weak points. It was something I often
    did on Friday afternoons.
    One of my jobs is to do that for hardware, to review a design and find
    where it will break.

    Hardware is a lot more expensive to fix than software.
    It depends on the context. I have read and have written reports that cite statistics that software rework can be more expensive than hardware rework. Studies have shown that removing a software defect during integration or acceptance testing cost
    anywhere from 50% to 400% removal cost if it was removed early in the development lifecycle, e.g. requirements analysis, architecture analysis. This is a big deal in software-intensive systems where software provides 70%-90% of the functionality.

    I meant that hardware is more expensive to fix in the field. It
    requires boxes to be removed and shipped back to the fractory and
    reworked and tested and such.

    Software, you can just put less-buggy rev 14.31.02b online, or email
    it to a customer.

    In some products, we can also send them a plugin flash chip or an SD
    card.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to All on Tue Oct 10 15:22:14 2023
    On 10/10/2023 12:27 PM, three_jeeps wrote:
    It depends on the context. I have read and have written reports that cite statistics that software rework can be more expensive than hardware rework. Studies have shown that removing a software defect during integration or acceptance testing cost anywhere from 50% to 400% removal cost if it was removed early in the development lifecycle, e.g. requirements analysis, architecture analysis. This is a big deal in software-intensive systems where software provides 70%-90% of the functionality.

    It's not just engineering costs. Actually "fitting" the fix to the
    (deployed) devices has costs, as well. Even if you can distribute
    the "upgrade" for free, there is a cost to installing it and
    dealing with any "problems" in that process.

    Manufacturers conveniently ignore this cost because the CUSTOMER
    bears it. But, the customer most assuredly *does* pay that cost.
    One would think a customer would be eager to have the latest and
    greatest, yet...

    How EAGER are you to install software updates for your various
    PC applications? And, that's with a device that likely has
    internet access ALREADY IN PLACE and an automated process to check
    for them, download them, etc.

    Do you even KNOW how to update the software in your TV? Stove?
    Refrigerator? Furnace? 'scope?

    [And, what happens if the update munges the device? Who pays
    THAT price to get it operational, again? Or, if there is some
    other "calibration" procedure involved? Or, if something
    more critical (to THAT customer) now has a problem?]

    I try to advocate for swap outs to upgrade/repair products:
    "The UPS driver will be there, tomorrow, with a new unit.
    Take it out of the box. Put your OLD unit *in* the box and
    give it back to the UPS driver. He will ship it back to us,
    prepaid."

    For folks who are really sensitive about continuous availability,
    buy a cold spare.

    Where this becomes costly is for consumer kit where you have to rely
    on the consumer to bring in the device for an upgrade/exchange.

    [In the 80's, I was working in Chicago suburbs. At the time,
    EPROM was the prefered encapsulation of code. A client told
    me it would cost him $600/unit to upgrade a device at customers
    located "in the city" -- while we were in the SUBURBS! Sheesh,
    it's just a half hour drive, including parking! "Can't you just
    mail the EPROMs to each customer?" "And what do we do when the
    customer folds a leg under while inserting the chips into sockets?
    *Assuming* the device detects this condition (i.e., not an
    intermittent connection to the top of the socket), he is now
    annoyed that HE had to fix OUR problem... and, now he has a
    broken machine! And, we have a service call that has to be
    handled NOW -- instead of an upgrade visit that could be scheduled
    at a more convenient time!"]

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to jjhudak@gmail.com on Tue Oct 10 22:31:02 2023
    XPost: free.spam

    The idiot three_jeeps <jjhudak@gmail.com> persisting in being an Off-topic troll...

    --
    three_jeeps <jjhudak@gmail.com> wrote:

    X-Received: by 2002:ad4:5887:0:b0:66c:fb8b:9ea0 with SMTP id dz7-20020ad45887000000b0066cfb8b9ea0mr46976qvb.8.1696966027105;
    Tue, 10 Oct 2023 12:27:07 -0700 (PDT)
    X-Received: by 2002:a05:6808:1a09:b0:3ae:7044:fde0 with SMTP id
    bk9-20020a0568081a0900b003ae7044fde0mr10045058oib.7.1696966026881; Tue, 10
    Oct 2023 12:27:06 -0700 (PDT)
    Path: not-for-mail
    Newsgroups: sci.electronics.design
    Date: Tue, 10 Oct 2023 12:27:05 -0700 (PDT)
    In-Reply-To: <2nlaii1lahlb7utev0q7o3drd0e2iavo6r@4ax.com>
    Injection-Info: google-groups.googlegroups.com; posting-host=136.226.18.172; posting-account=FRjqegoAAADz_Z3fAICQ1u4DKaXzRcvn
    NNTP-Posting-Host: 136.226.18.172
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    <ufpjoj$1rduc$1@dont-email.me> <ufpqv8$1so3a$3@dont-email.me>
    <ufprab$1so3a$4@dont-email.me> <ug3fj5$14jm9$1@dont-email.me> <2nlaii1lahlb7utev0q7o3drd0e2iavo6r@4ax.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <c9a7b216-aff1-4fc9-a123-5c0a761541e7n@googlegroups.com>
    Subject: Re: Another EV goes haywire!
    From: three_jeeps <jjhudak@gmail.com>
    Injection-Date: Tue, 10 Oct 2023 19:27:07 +0000
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable
    X-Received-Bytes: 3054

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Don Y on Tue Oct 10 22:31:39 2023
    XPost: free.spam

    The arsehole Don Y <blockedofcourse@foo.invalid> persisting in being an Off-topic troll...

    --
    Don Y <blockedofcourse@foo.invalid> wrote:

    Path: not-for-mail
    From: Don Y <blockedofcourse@foo.invalid>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Tue, 10 Oct 2023 15:22:14 -0700
    Organization: A noiseless patient Spider
    Lines: 58
    Message-ID: <ug4iqn$1d1p9$2@dont-email.me>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com>
    <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    <ufpjoj$1rduc$1@dont-email.me> <ufpqv8$1so3a$3@dont-email.me>
    <ufprab$1so3a$4@dont-email.me> <ug3fj5$14jm9$1@dont-email.me>
    <2nlaii1lahlb7utev0q7o3drd0e2iavo6r@4ax.com>
    <c9a7b216-aff1-4fc9-a123-5c0a761541e7n@googlegroups.com>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit
    Injection-Date: Tue, 10 Oct 2023 22:22:17 -0000 (UTC)
    Injection-Info: dont-email.me; posting-host="3fd8938ad2cd16f63dcfd6887e0f2ac9";
    logging-data="1476393"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/TiU+ff4U17EutKNnTe3/p"
    User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101
    Thunderbird/102.2.2
    Cancel-Lock: sha1:7m8zZhGYTXaiNHnPM2ircTixHb0=
    Content-Language: en-US
    In-Reply-To: <c9a7b216-aff1-4fc9-a123-5c0a761541e7n@googlegroups.com> X-Received-Bytes: 4234

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to john larkin on Tue Oct 10 22:31:45 2023
    XPost: free.spam

    The idiot john larkin <jl@650pot.com> persisting in being an Off-topic troll...

    --
    john larkin <jl@650pot.com> wrote:

    Path: not-for-mail
    NNTP-Posting-Date: Tue, 10 Oct 2023 19:05:53 +0000
    From: john larkin <jl@650pot.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Tue, 10 Oct 2023 12:05:53 -0700
    Message-ID: <vs7biih4cl52j9tav915nfp2qo3irueccv@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com> <ufpjoj$1rduc$1@dont-email.me> <ufpqv8$1so3a$3@dont-email.me> <ufprab$1so3a$4@dont-email.me> <ug3fj5$14jm9$1@dont-email.me> <ug4099$18jf9$
    1@dont-email.me>
    User-Agent: ForteAgent/8.00.32.1272 trialware
    MIME-Version: 1.0
    Content-Type: text/plain; charset=ISO-8859-1
    Content-Transfer-Encoding: 8bit
    Lines: 176
    X-Trace: sv3-hFxsNWmyLPQNH3CCNogyHQiR7Sat994XhmjisCoZazvVm8Kwan0m0fTCgtvDyiQ4mm6gLJC42F0570z!ehQnihT9YaEOav+nAUK/if+EtJVaP+s0oDCFx+vd6QBvioifl6LHDx/JNqSriK751RVXbLzRdXSH!6ZOEfw==
    X-Complaints-To: www.supernews.com/docs/abuse.html
    X-DMCA-Complaints-To: www.supernews.com/docs/dmca.html
    X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
    X-Postfilter: 1.3.40
    Bytes: 9616
    X-Received-Bytes: 9754

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony William Sloman@21:1/5 to Don Y on Tue Oct 10 18:13:07 2023
    On Wednesday, October 11, 2023 at 4:05:54 AM UTC+11, Don Y wrote:
    On 10/10/2023 5:20 AM, Martin Brown wrote:
    On 06/10/2023 21:39, Don Y wrote:
    On 10/6/2023 1:33 PM, Don Y wrote:
    [I've been given specs with obvious incompatibilities -- that the
    author hadn't seen just because he was too close to the problem
    and had too many baked in assumptions: "Here, imagine THIS happening..."]

    Sadly, no one teaches folks how to write (and challenge) good
    specifications (hardware, software, system). And, few folks have
    an interest in developing that skillset.

    I had a reputation for breaking software and being able to guess situations
    where there might be weak points. It was something I often did on Friday afternoons.

    I am distressed at how many "obvious" flaws creep into software.

    You may be distressed, but you shouldn't be surprised. Human's make mistakes all the time.

    Our internal communications system seems to be noisy. You intend to type one letter but end up typing another - a typo - or intended to say one thing and ended up saying another - a speech error. Psychologists group them all together as errors of action.
    In England, engineers call them drop-offs.

    The answer is design reviews. Somebody else has to go through your work in detail, and make sure that it all makes sense.

    To make this easy you should go in for modular, heirarchical design, so you end up inspecting lots of small lumps. No multipage functions.

    --
    Bill Sloman, Sydney

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ricky@21:1/5 to Anthony William Sloman on Tue Oct 10 18:21:41 2023
    On Tuesday, October 10, 2023 at 9:13:13 PM UTC-4, Anthony William Sloman wrote:
    On Wednesday, October 11, 2023 at 4:05:54 AM UTC+11, Don Y wrote:
    On 10/10/2023 5:20 AM, Martin Brown wrote:
    On 06/10/2023 21:39, Don Y wrote:
    On 10/6/2023 1:33 PM, Don Y wrote:
    [I've been given specs with obvious incompatibilities -- that the
    author hadn't seen just because he was too close to the problem
    and had too many baked in assumptions: "Here, imagine THIS happening..."]

    Sadly, no one teaches folks how to write (and challenge) good
    specifications (hardware, software, system). And, few folks have
    an interest in developing that skillset.

    I had a reputation for breaking software and being able to guess situations
    where there might be weak points. It was something I often did on Friday afternoons.

    I am distressed at how many "obvious" flaws creep into software.
    You may be distressed, but you shouldn't be surprised. Human's make mistakes all the time.

    Our internal communications system seems to be noisy. You intend to type one letter but end up typing another - a typo - or intended to say one thing and ended up saying another - a speech error. Psychologists group them all together as errors of
    action. In England, engineers call them drop-offs.

    The answer is design reviews. Somebody else has to go through your work in detail, and make sure that it all makes sense.

    To make this easy you should go in for modular, heirarchical design, so you end up inspecting lots of small lumps. No multipage functions.

    That is one of the main tenents of forth, keeping word (subroutine) definitions short (typically 1 to 4 lines). This allows ease of debugging by walking through the word in your mind, as well as simplification of visualizing what is happening on the
    data stack. Then the word can be tested interactively at the command line easily. It can lead to more productivity.

    --

    Rick C.

    -+- Get 1,000 miles of free Supercharging
    -+- Tesla referral code - https://ts.la/richard11209

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From whit3rd@21:1/5 to john larkin on Tue Oct 10 20:00:38 2023
    On Tuesday, October 10, 2023 at 1:20:23 PM UTC-7, john larkin wrote:
    On Tue, 10 Oct 2023 12:27:05 -0700 (PDT), three_jeeps
    <jjh...@gmail.com> wrote:
    On Tuesday, October 10, 2023 at 9:54:02?AM UTC-4, John Larkin wrote:
    On Tue, 10 Oct 2023 13:20:52 +0100, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 06/10/2023 21:39, Don Y wrote:
    On 10/6/2023 1:33 PM, Don Y wrote:
    [I've been given specs with obvious incompatibilities -- that the
    author hadn't seen just because he was too close to the problem
    and had too many baked in assumptions: "Here, imagine THIS
    happening..."]

    Sadly, no one teaches folks how to write (and challenge) good
    specifications (hardware, software, system). And, few folks have
    an interest in developing that skillset.

    I had a reputation for breaking software and being able to guess
    situations where there might be weak points. It was something I often
    did on Friday afternoons.
    One of my jobs is to do that for hardware, to review a design and find
    where it will break.

    Hardware is a lot more expensive to fix than software.
    It depends on the context. I have read and have written reports that cite statistics that software rework can be more expensive than hardware rework. Studies have shown that removing a software defect during integration or acceptance testing cost
    anywhere from 50% to 400% removal cost if it was removed early in the development lifecycle, e.g. requirements analysis, architecture analysis. This is a big deal in software-intensive systems where software provides 70%-90% of the functionality.
    I meant that hardware is more expensive to fix in the field. It
    requires boxes to be removed and shipped back to the fractory and
    reworked and tested and such.

    Software, you can just put less-buggy rev 14.31.02b online, or email
    it to a customer.

    In some products, we can also send them a plugin flash chip or an SD
    card.

    It's not always that simple; a firmware update, for example, has not only to
    be supplied to the customer, but has to be applied somehow to all the unassembled
    bits that are in the spare parts inventory for warranty repairs. It also might
    be the case that a faulty software means half a warehouse of install disks and associated
    packaging and documentation need a trip to the shredder.

    And then, there's the issue of notifications going out to the concerned parties...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to All on Tue Oct 10 20:29:29 2023
    On 10/10/2023 8:00 PM, whit3rd wrote:
    It's not always that simple; a firmware update, for example, has not only to be supplied to the customer, but has to be applied somehow to all the unassembled
    bits that are in the spare parts inventory for warranty repairs. It also might
    be the case that a faulty software means half a warehouse of install disks and associated
    packaging and documentation need a trip to the shredder.

    And then, there's the issue of notifications going out to the concerned parties...

    There are, also, industries where release engineering involves regulatory approvals. You're not going to make even TRIVIAL changes to a piece
    of software in a medical instrument, gaming device, aero/astronautics, etc. There are very tangible costs to those "bugs" and to "casual" changes
    to systems in which they could present.

    In such cases, the cost of the change is directly experienced by the manufacturer. There is a big incentive NOT to incur them, needlessly!
    (I wonder what ever became of the Therac-26?)

    So, you don't adopt the notion that "software is easy/inexpensive to change" and, thus, prevent yourself from slipping into situations where you EXPECT
    that to be true.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to whit3rd@gmail.com on Wed Oct 11 03:40:15 2023
    XPost: free.spam

    The idiot whit3rd <whit3rd@gmail.com> persisting in being an Off-topic troll...

    --
    whit3rd <whit3rd@gmail.com> wrote:

    X-Received: by 2002:a05:6214:8d0:b0:66d:3c9:4afa with SMTP id da16-20020a05621408d000b0066d03c94afamr15805qvb.0.1696993239296;
    Tue, 10 Oct 2023 20:00:39 -0700 (PDT)
    X-Received: by 2002:a05:6870:955b:b0:1e9:7928:6f1b with SMTP id
    v27-20020a056870955b00b001e979286f1bmr1019594oal.0.1696993239109; Tue, 10 Oct
    2023 20:00:39 -0700 (PDT)
    Path: not-for-mail
    Newsgroups: sci.electronics.design
    Date: Tue, 10 Oct 2023 20:00:38 -0700 (PDT)
    In-Reply-To: <n3cbiih5tb1185p5ba7rlg6584snimuklk@4ax.com>
    Injection-Info: google-groups.googlegroups.com; posting-host=209.221.140.126; posting-account=vKQm_QoAAADOaDCYsqOFDAW8NJ8sFHoE
    NNTP-Posting-Host: 209.221.140.126
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    <ufpjoj$1rduc$1@dont-email.me> <ufpqv8$1so3a$3@dont-email.me>
    <ufprab$1so3a$4@dont-email.me> <ug3fj5$14jm9$1@dont-email.me>
    <2nlaii1lahlb7utev0q7o3drd0e2iavo6r@4ax.com> <c9a7b216-aff1-4fc9-a123-5c0a761541e7n@googlegroups.com>
    <n3cbiih5tb1185p5ba7rlg6584snimuklk@4ax.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <e3d8b63f-ee17-41dc-82cd-96b5d204699en@googlegroups.com>
    Subject: Re: Another EV goes haywire!
    From: whit3rd <whit3rd@gmail.com>
    Injection-Date: Wed, 11 Oct 2023 03:00:39 +0000
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable
    X-Received-Bytes: 4274

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Don Y on Wed Oct 11 03:40:52 2023
    XPost: free.spam

    The idiot Don Y <blockedofcourse@foo.invalid> persisting in being an Off-topic troll...

    --
    Don Y <blockedofcourse@foo.invalid> wrote:

    Path: not-for-mail
    From: Don Y <blockedofcourse@foo.invalid>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Tue, 10 Oct 2023 20:29:29 -0700
    Organization: A noiseless patient Spider
    Lines: 26
    Message-ID: <ug54qr$1khqv$2@dont-email.me>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com>
    <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    <ufpjoj$1rduc$1@dont-email.me> <ufpqv8$1so3a$3@dont-email.me>
    <ufprab$1so3a$4@dont-email.me> <ug3fj5$14jm9$1@dont-email.me>
    <2nlaii1lahlb7utev0q7o3drd0e2iavo6r@4ax.com>
    <c9a7b216-aff1-4fc9-a123-5c0a761541e7n@googlegroups.com>
    <n3cbiih5tb1185p5ba7rlg6584snimuklk@4ax.com>
    <e3d8b63f-ee17-41dc-82cd-96b5d204699en@googlegroups.com>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit
    Injection-Date: Wed, 11 Oct 2023 03:29:32 -0000 (UTC)
    Injection-Info: dont-email.me; posting-host="3fd8938ad2cd16f63dcfd6887e0f2ac9";
    logging-data="1722207"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/Ed6J9NDk/E9qc4XEQTnbn"
    User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101
    Thunderbird/102.2.2
    Cancel-Lock: sha1:6wdyA6B2F36S/ToLXmAMH84SXGo=
    In-Reply-To: <e3d8b63f-ee17-41dc-82cd-96b5d204699en@googlegroups.com> Content-Language: en-US
    X-Received-Bytes: 2794

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to john larkin on Wed Oct 11 09:45:21 2023
    On 10/10/2023 20:05, john larkin wrote:
    On Tue, 10 Oct 2023 10:05:44 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    On 10/10/2023 5:20 AM, Martin Brown wrote:

    I-frames were correctly decoded and it was only the dynamic movement updates
    that had a part of the coefficient table scrambled. It slightly showed up on
    water sports too since small globs of water spray instead of being
    approximately round would look like stellated icosahedra!

    Presumably, the "output" could be redirected to compare it to
    the *expected* output, instead of relying on human eyes to
    "notice" these artifacts.

    They were quite subtle and only clearly visible on ~50" sets so my guess
    is that they were tested on much smaller screens where the defects would
    be hidden by the limited pixel resolution.

    Testing is so often an afterthought. Why wasn't the scaffolding in
    place to make this a more robust process?

    [The same applies, in spades, to security issues!]

    Testing is also pretty much skipped when development overruns (as it
    almost always does) and the suits tell the engineers to ship it and be
    damned so that they get their sales bonuses.

    We live in the Dark Ages of computer programming. It's like when
    people built cathedrals in the year 900... try it and see if it falls
    down.

    +1

    Sadly I have to partially agree with you. Despite vast improvements in
    the capabilities of modern software tools to detect common human errors
    much of the software development process remains stuck in a suck it and
    see mode. I find the random laying on of casts painful to watch.

    It is a bit like medieval cathedral building where if it was still
    standing after 5 years then it was a good 'un. Ely cathedral and the
    leaning tower of Pisa being notable edge cases. Medieval cathedral
    builders were a bit smarter though they left some engineering safety
    margin in their designs to compensate for limited knowledge.

    There are bright spots here and there where some things are done
    properly - there is a lot of good software out there but there is also
    some truly terrible stuff.

    Even classic structural engineering can make massive balls ups. The
    shaking footbridge in London is yet again under repair and the walkie
    talkie building that cooks cars in the street below at certain times of
    year shows the sorts of thing that can still go wrong even today.

    Sad to say, but few people can program responsibly. They need a
    LabView sort of box dragger. With that, a competant admin would create
    better programs.

    Labview is OK in its domain but it isn't general enough. Generative AI
    might be one way forward if you don't mind having a new sort of bugs.

    Nassi-Sneiderman diagrams tried to do just that. Essentially circuit
    diagrams for software. I actually liked the idea at least for laying out algorithms but the people who disliked it called them Nasty Spiderman
    diagrams (and history shows that they won that argument).

    https://en.wikipedia.org/wiki/Nassi%E2%80%93Shneiderman_diagram

    Still used today in Germany according to Wiki (I didn't know that).


    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Martin Brown on Wed Oct 11 05:24:19 2023
    On 10/11/2023 1:45 AM, Martin Brown wrote:
    On 10/10/2023 20:05, john larkin wrote:
    On Tue, 10 Oct 2023 10:05:44 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    On 10/10/2023 5:20 AM, Martin Brown wrote:

    I-frames were correctly decoded and it was only the dynamic movement updates
    that had a part of the coefficient table scrambled. It slightly showed up on
    water sports too since small globs of water spray instead of being
    approximately round would look like stellated icosahedra!

    Presumably, the "output" could be redirected to compare it to
    the *expected* output, instead of relying on human eyes to
    "notice" these artifacts.

    They were quite subtle and only clearly visible on ~50" sets so my guess is that they were tested on much smaller screens where the defects would be hidden
    by the limited pixel resolution.

    Why would the test procedure have, essentially, been "Look at the
    screen and verify it looks OK"? That's like saying "Place your
    finger on R27 and verify it is not hot".

    Note my comments re: my gnuplot experience. Why wouldn't the
    test scaffolding have done a bitwise compare of the image
    created during the test run vs. the image created at time of
    test creation?

    This all just speaks of a poor *process* with (likely) no
    oversight.

    "Did you test the power supply?"
    "Sure"

    What is NOT being said/asked, there?

    Testing is so often an afterthought.  Why wasn't the scaffolding in
    place to make this a more robust process?

    [The same applies, in spades, to security issues!]

    Testing is also pretty much skipped when development overruns (as it almost always does) and the suits tell the engineers to ship it and be damned so that
    they get their sales bonuses.

    It's usually not even a formal *step* in the process without overruns!
    There is too much /ad hoc/ development happening. Often, because the
    people in charge of the process are ignorant of its needs. So, at
    nest, they make token superficial attempts at pretending they are
    Doing The Right Thing when they're really just adding window dressing.

    Can you move to an arbitrary fork in the development and recreate it
    as of the date of that fork? Have you captured a snapshot of the complete source tree at that point in time? Including the build scripts? AND
    the build tools? (along with any environment they need to execute)
    If not, how can you address a reported anomaly: "We can't reproduce
    it, here..." (can you even reproduce the binary that shipped at that
    time to be able to examine and challenge the sources?)

    Sadly I have to partially agree with you. Despite vast improvements in the capabilities of modern software tools to detect common human errors much of the
    software development process remains stuck in a suck it and see mode. I find the random laying on of casts painful to watch.

    Tools can't compensate for bad process. The availability of simulation
    tools doesn't improve the quality of hardware designs generated by a slap-together-app-notes designer.

    There's a difference with hardware; one can (usually) see that a
    design is being tested/stressed vs. being designed. The activities
    and equipment used are different. Software is often tested at
    the same workstation that was used to design/develop it. And,
    often interspersed with the development process.

    Do I click on an icon on my screen to cause my time to be charged to
    "testing" vs. "development"?

    Only large projects (with lots of staff) put in place formal test
    procedures. Which mirror their formal SPECIFICATION procedures.
    Ask anyone managing a software project (or software PART of a
    project) to show you the specification for the software. Try
    not to laugh too loudly at the document that appears (if any).
    Subbing out such a task would end up with both parties in
    litigation for years as the subcontractor would argue that
    the (formal) document didn't require all of the things that
    the client is now CLAIMING should be present in the software.

    Like asking a builder to "build a 4 bedroom house" and then
    complaining that the bedrooms are too small, oddly shaped,
    have low ceilings, no plumbing or electricity, etc.
    "Well, of COURSE it should have all those things!"
    "Yet, you didn't think them important enough to specify?"

    In an even cruder analysis, ask how much TIME was spent:
    - specification
    - design/development/coding
    - test
    Just look at relative figures and ask the responsible party to
    explain the often absurd imbalance (5/90/5 is probably a
    GOOD figure <rolls eyes>)

    [When quizzing an applicant for a software position, you can SEE
    these events unfold before your eyes. Pay attention to the
    relative mix if you want to have a "good" hire!]

    It is a bit like medieval cathedral building where if it was still standing after 5 years then it was a good 'un. Ely cathedral and the leaning tower of Pisa being notable edge cases. Medieval cathedral builders were a bit smarter though they left some engineering safety margin in their designs to compensate
    for limited knowledge.

    There are bright spots here and there where some things are done properly -

    "/done/ properly" (emphasis mine) implicitly speaks to *process*.

    Too often, software is the bandaid for the design -- the parts that
    weren't thought out or appropriately handled. Like Klaus having
    to "fix" a bad layout IN SOFTWARE instead of just laying out a new
    board. How many other problems will that hack bring into play?

    there is a lot of good software out there but there is also some truly terrible
    stuff.

    Even classic structural engineering can make massive balls ups. The shaking footbridge in London is yet again under repair and the walkie talkie building that cooks cars in the street below at certain times of year shows the sorts of
    thing that can still go wrong even today.

    Problems that come from unforeseen circumstances get a bit of a pass.
    MIT's Building 54's design had to be modified to address (ahem)
    "local atmospheric pressure differentials" <https://en.wikipedia.org/wiki/Green_Building_(MIT)#Problems>
    (Wasn't Pei supposed to be a GOOD architect? Perhaps he didn't
    have a good theoretical understanding of the issues?? :> )

    Labview is OK in its domain but it isn't general enough. Generative AI might be
    one way forward if you don't mind having a new sort of bugs.

    This is yet another version of "let's try to change the tools to
    compensate for bad practices". Let's do away with pointers because
    people make mistakes with them. Let's do away with KNIVES because
    people cut themselves with them.

    Let's use solder with a lower melting point so we can use cooler
    soldering irons that won't BURN folks who are too stupid to know
    which end to hold! Really?

    That trend is the business world trying to figure out how to
    get something for nothing. It's what leads to these endless
    strings of bloated languages and IDEs. How's that working out?
    Gee, lets try MORE of it... maybe the problem is that we
    haven't gone far enough down that path!?

    People just need to learn how to ENGINEER software and stop
    cranking out "programmers" and (ick) coders. The fact that it's
    so EASY to get folks to write "functional" code leads them
    to thinking they can write GOOD code and, worse, design
    good software-based SYSTEMS.

    We don't advocate for tools that let us dumb down EEs so
    they can be replaced by *technicians* (think of the money
    that could be saved when an AI can just draw up a schematic
    for you! Dial in just how much you want the circuit to
    cost, how large you want it to be, what sort of warranty
    repair rate you'll tolerate, etc. Bingo! We can replace all
    of the *engineering* schools with *trade* schools!)

    Nassi-Sneiderman diagrams tried to do just that. Essentially circuit diagrams for software. I actually liked the idea at least for laying out algorithms but
    the people who disliked it called them Nasty Spiderman diagrams (and history shows that they won that argument).

    Even trivial software is too interconnected to make exposing
    interactions a practical thing. Unlike hardware, where each
    component or subassembly has FEW direct connections, much
    software interacts with MANY other bits (especially true
    of poorly designed software)

    And, it's the interactions that are where the issues lie.
    This is why things like encapsulation, information hiding,
    limiting function size (and interface width), etc. are
    touted as best practices for "good smells". The era of
    monolithic blocks and 2G/3G languages is just SO far behind us
    that to see folks using those similar design TECHNIQUES speaks
    volumes to their lack of design sophistication.

    https://en.wikipedia.org/wiki/Nassi%E2%80%93Shneiderman_diagram

    Still used today in Germany according to Wiki (I didn't know that).

    That's yet another *tool*. Using DFAs everywhere doesn't make
    software any better (in a general sense). Or Petri Nets. Or...
    You have to treat it as an engineering DISCIPLINE and not just a
    (increasingly) "necessary step" in a product's design.

    "Learn to code in 24 days"
    "Learn to layout PCBs in 24 days"
    "Learn to design FPGAs in 24 days"

    Get the complete set, now in bookstores, near you! :>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Larkin@21:1/5 to blockedofcourse@foo.invalid on Wed Oct 11 07:43:13 2023
    On Wed, 11 Oct 2023 05:24:19 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    On 10/11/2023 1:45 AM, Martin Brown wrote:
    On 10/10/2023 20:05, john larkin wrote:
    On Tue, 10 Oct 2023 10:05:44 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    On 10/10/2023 5:20 AM, Martin Brown wrote:

    I-frames were correctly decoded and it was only the dynamic movement updates
    that had a part of the coefficient table scrambled. It slightly showed up on
    water sports too since small globs of water spray instead of being
    approximately round would look like stellated icosahedra!

    Presumably, the "output" could be redirected to compare it to
    the *expected* output, instead of relying on human eyes to
    "notice" these artifacts.

    They were quite subtle and only clearly visible on ~50" sets so my guess is >> that they were tested on much smaller screens where the defects would be hidden
    by the limited pixel resolution.

    Why would the test procedure have, essentially, been "Look at the
    screen and verify it looks OK"? That's like saying "Place your
    finger on R27 and verify it is not hot".

    Note my comments re: my gnuplot experience. Why wouldn't the
    test scaffolding have done a bitwise compare of the image
    created during the test run vs. the image created at time of
    test creation?

    This all just speaks of a poor *process* with (likely) no
    oversight.

    "Did you test the power supply?"
    "Sure"

    What is NOT being said/asked, there?

    Testing is so often an afterthought.  Why wasn't the scaffolding in
    place to make this a more robust process?

    [The same applies, in spades, to security issues!]

    Testing is also pretty much skipped when development overruns (as it almost >> always does) and the suits tell the engineers to ship it and be damned so that
    they get their sales bonuses.

    It's usually not even a formal *step* in the process without overruns!
    There is too much /ad hoc/ development happening. Often, because the
    people in charge of the process are ignorant of its needs. So, at
    nest, they make token superficial attempts at pretending they are
    Doing The Right Thing when they're really just adding window dressing.

    Can you move to an arbitrary fork in the development and recreate it
    as of the date of that fork? Have you captured a snapshot of the complete >source tree at that point in time? Including the build scripts? AND
    the build tools? (along with any environment they need to execute)
    If not, how can you address a reported anomaly: "We can't reproduce
    it, here..." (can you even reproduce the binary that shipped at that
    time to be able to examine and challenge the sources?)

    Sadly I have to partially agree with you. Despite vast improvements in the >> capabilities of modern software tools to detect common human errors much of the
    software development process remains stuck in a suck it and see mode. I find >> the random laying on of casts painful to watch.

    Tools can't compensate for bad process. The availability of simulation
    tools doesn't improve the quality of hardware designs generated by a >slap-together-app-notes designer.

    There's a difference with hardware; one can (usually) see that a
    design is being tested/stressed vs. being designed. The activities
    and equipment used are different. Software is often tested at
    the same workstation that was used to design/develop it. And,
    often interspersed with the development process.

    We have several formal design reviews when we design a PC board. I
    expect attendees to have looked at every sheet of a schematic, at
    every part on every sheet, to THINK, and to bring up any concerns for discussion.

    The designer walks the attendees through the schematic to jog their
    memories and evoke gotchas.

    Do software projects get reviewed like that? Are attendees expected to
    have carefully read all the code?

    We know that we can't test quality into hardware. It takes too long
    and too many dollars to lay out and buy and assemble PC boards. A
    metastability or tolerance stackup bug might have an MTBF of months or
    years.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Larkin@21:1/5 to '''newspam'''@nonad.co.uk on Wed Oct 11 07:32:58 2023
    On Wed, 11 Oct 2023 09:45:21 +0100, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 10/10/2023 20:05, john larkin wrote:
    On Tue, 10 Oct 2023 10:05:44 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    On 10/10/2023 5:20 AM, Martin Brown wrote:

    I-frames were correctly decoded and it was only the dynamic movement updates
    that had a part of the coefficient table scrambled. It slightly showed up on
    water sports too since small globs of water spray instead of being
    approximately round would look like stellated icosahedra!

    Presumably, the "output" could be redirected to compare it to
    the *expected* output, instead of relying on human eyes to
    "notice" these artifacts.

    They were quite subtle and only clearly visible on ~50" sets so my guess
    is that they were tested on much smaller screens where the defects would
    be hidden by the limited pixel resolution.

    Testing is so often an afterthought. Why wasn't the scaffolding in
    place to make this a more robust process?

    [The same applies, in spades, to security issues!]

    Testing is also pretty much skipped when development overruns (as it
    almost always does) and the suits tell the engineers to ship it and be
    damned so that they get their sales bonuses.

    We live in the Dark Ages of computer programming. It's like when
    people built cathedrals in the year 900... try it and see if it falls
    down.

    +1

    Sadly I have to partially agree with you. Despite vast improvements in
    the capabilities of modern software tools to detect common human errors
    much of the software development process remains stuck in a suck it and
    see mode. I find the random laying on of casts painful to watch.

    It is a bit like medieval cathedral building where if it was still
    standing after 5 years then it was a good 'un. Ely cathedral and the
    leaning tower of Pisa being notable edge cases. Medieval cathedral
    builders were a bit smarter though they left some engineering safety
    margin in their designs to compensate for limited knowledge.

    There are bright spots here and there where some things are done
    properly - there is a lot of good software out there but there is also
    some truly terrible stuff.

    Even classic structural engineering can make massive balls ups. The
    shaking footbridge in London is yet again under repair and the walkie
    talkie building that cooks cars in the street below at certain times of
    year shows the sorts of thing that can still go wrong even today.

    Sad to say, but few people can program responsibly. They need a
    LabView sort of box dragger. With that, a competant admin would create
    better programs.

    Labview is OK in its domain but it isn't general enough. Generative AI
    might be one way forward if you don't mind having a new sort of bugs.

    The fundamental problem with the popular AI concpt is that it assumes
    that a small number of words can express and generate a very complex
    solution. That doesn't make sense, because the solution space is too
    big and the AI can't decide which results are good and which aren't.

    I use Kasiser health care. My wife uses a bunch of healthcare provider
    web sites. Their software is terrible and buggy. The reason is that
    ginding out applications is boring, but inventing computer languages
    and theorems and building layers of abstraction is more fun than
    getting "contact your doctor" code right. The "best" programmers don't
    want to work for a hospital where they are grunts and the superstars
    are the doctors. They want to work where programmers are the
    superstars.

    Please reply to this message with the information.
    You may not reply to this message.



    Nassi-Sneiderman diagrams tried to do just that. Essentially circuit
    diagrams for software. I actually liked the idea at least for laying out >algorithms but the people who disliked it called them Nasty Spiderman >diagrams (and history shows that they won that argument).

    https://en.wikipedia.org/wiki/Nassi%E2%80%93Shneiderman_diagram

    Still used today in Germany according to Wiki (I didn't know that).

    I like graphical representations, essentially block diagrams, to
    design hardware or software. And I like state machines. So I write
    crude code that's done quickly, runs fast in realtime, and rarely has
    bugs. Lots of GOTO and minimal abstraction. That's a spatial-sense
    thing, drawing instead of typing. Many programmers are word (not
    diagram) (and punctuation!) people and want to type, not draw.

    Sometimes I have to pull my software people into a conference room, in
    front of a whiteboard, and untangle their mess. That's going to happen
    next week again, about handling SCPI commands.

    I hate SCPI. Have you read the SCPI99 spec? Obviously the work of a
    committee of eggheads having their kind of fun.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Ricky on Wed Oct 11 16:27:15 2023
    XPost: free.spam

    The arsehole Ricky <gnuarm.deletethisbit@gmail.com> persisting in being an Off-topic troll...

    --
    Ricky <gnuarm.deletethisbit@gmail.com> wrote:

    X-Received: by 2002:a05:6214:3113:b0:65a:fd9b:e057 with SMTP id ks19-20020a056214311300b0065afd9be057mr283089qvb.0.1696987302541;
    Tue, 10 Oct 2023 18:21:42 -0700 (PDT)
    X-Received: by 2002:a05:6870:d24e:b0:1e9:841d:4e96 with SMTP id
    h14-20020a056870d24e00b001e9841d4e96mr743995oac.5.1696987302232; Tue, 10 Oct
    2023 18:21:42 -0700 (PDT)
    Path: not-for-mail
    Newsgroups: sci.electronics.design
    Date: Tue, 10 Oct 2023 18:21:41 -0700 (PDT)
    In-Reply-To: <4daa4f83-a1b5-4c86-9173-df1919696d40n@googlegroups.com> Injection-Info: google-groups.googlegroups.com; posting-host=65.207.89.54; posting-account=I-_H_woAAAA9zzro6crtEpUAyIvzd19b
    NNTP-Posting-Host: 65.207.89.54
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    <ufpjoj$1rduc$1@dont-email.me> <ufpqv8$1so3a$3@dont-email.me>
    <ufprab$1so3a$4@dont-email.me> <ug3fj5$14jm9$1@dont-email.me>
    <ug4099$18jf9$1@dont-email.me> <4daa4f83-a1b5-4c86-9173-df1919696d40n@googlegroups.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <f852ea30-3577-4a99-91ae-b7b94ecd1f33n@googlegroups.com>
    Subject: Re: Another EV goes haywire!
    From: Ricky <gnuarm.deletethisbit@gmail.com>
    Injection-Date: Wed, 11 Oct 2023 01:21:42 +0000
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable
    X-Received-Bytes: 3813

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Martin Brown on Wed Oct 11 16:28:05 2023
    XPost: free.spam

    The arsehole Martin Brown <'''newspam'''@nonad.co.uk> persisting in being an Off-topic troll...

    --
    Martin Brown <'''newspam'''@nonad.co.uk> wrote:

    Path: not-for-mail
    From: Martin Brown <'''newspam'''@nonad.co.uk>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Wed, 11 Oct 2023 09:45:21 +0100
    Organization: A noiseless patient Spider
    Lines: 74
    Message-ID: <ug5nb4$1o4iv$1@dont-email.me>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com>
    <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com>
    <ufpjoj$1rduc$1@dont-email.me> <ufpqv8$1so3a$3@dont-email.me>
    <ufprab$1so3a$4@dont-email.me> <ug3fj5$14jm9$1@dont-email.me>
    <ug4099$18jf9$1@dont-email.me> <vs7biih4cl52j9tav915nfp2qo3irueccv@4ax.com> MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit
    Injection-Date: Wed, 11 Oct 2023 08:45:24 -0000 (UTC)
    Injection-Info: dont-email.me; posting-host="7a9d4d2a866770ed363d5200ce8f7854";
    logging-data="1839711"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/xThWWmylG3k8cFbyflxdNHtGR5Rue8IksQaIoqtQY7A=="
    User-Agent: Mozilla Thunderbird
    Cancel-Lock: sha1:7Sj1VIpWwDrCs18JBPV66nH+Tyg=
    In-Reply-To: <vs7biih4cl52j9tav915nfp2qo3irueccv@4ax.com>
    Content-Language: en-GB
    X-Received-Bytes: 4471

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Don Y on Wed Oct 11 16:28:11 2023
    XPost: free.spam

    The idiot Don Y <blockedofcourse@foo.invalid> persisting in being an Off-topic troll...

    --
    Don Y <blockedofcourse@foo.invalid> wrote:

    Path: not-for-mail
    From: Don Y <blockedofcourse@foo.invalid>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Wed, 11 Oct 2023 05:24:19 -0700
    Organization: A noiseless patient Spider
    Lines: 203
    Message-ID: <ug645l$1qpn8$2@dont-email.me>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com> <ufpjoj$1rduc$1@dont-email.me> <ufpqv8$1so3a$3@dont-email.me> <ufprab$1so3a$4@dont-email.me> <ug3fj5$14jm9$1@dont-email.me> <ug4099$18jf9$
    1@dont-email.me> <vs7biih4cl52j9tav915nfp2qo3irueccv@4ax.com> <ug5nb4$1o4iv$1@dont-email.me>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit
    Injection-Date: Wed, 11 Oct 2023 12:24:22 -0000 (UTC)
    Injection-Info: dont-email.me; posting-host="3fd8938ad2cd16f63dcfd6887e0f2ac9"; logging-data="1926888"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/ClyyAqyP9IQuM0BI81I3O"
    User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2
    Cancel-Lock: sha1:os/N/MMzyC5YW+yVMQlMZH5Yq/I=
    In-Reply-To: <ug5nb4$1o4iv$1@dont-email.me>
    Content-Language: en-US
    X-Received-Bytes: 10820

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to John Larkin on Wed Oct 11 16:28:23 2023
    XPost: free.spam

    The arsehole John Larkin <jl@997PotHill.com> persisting in being an Off-topic troll...

    --
    John Larkin <jl@997PotHill.com> wrote:

    Path: not-for-mail
    NNTP-Posting-Date: Wed, 11 Oct 2023 14:33:01 +0000
    From: John Larkin <jl@997PotHill.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Wed, 11 Oct 2023 07:32:58 -0700
    Organization: Highland Tech
    Reply-To: xx@yy.com
    Message-ID: <07bdii9v85muth242pl5r0n9ned911b0sf@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com> <ufpjoj$1rduc$1@dont-email.me> <ufpqv8$1so3a$3@dont-email.me> <ufprab$1so3a$4@dont-email.me> <ug3fj5$14jm9$1@dont-email.me> <ug4099$18jf9$
    1@dont-email.me> <vs7biih4cl52j9tav915nfp2qo3irueccv@4ax.com> <ug5nb4$1o4iv$1@dont-email.me>
    X-Newsreader: Forte Agent 3.1/32.783
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Lines: 106
    X-Trace: sv3-S3eUxyrl9pUfZSZD9M8Bw6Pwp9s3f4o+VtpNiV2F4o5fKg9Jt67uKfL+XAUXS7JmSiASu9NyjJ9KjZ3!tubn1FqiXOtlHMXnnpQzP6axlvoacx4XGt0Rs/jPOvaH6nYDu/IcBa00DvVN7wlvW2OpyGnv1f/s!O+zNzg==
    X-Complaints-To: www.supernews.com/docs/abuse.html
    X-DMCA-Complaints-To: www.supernews.com/docs/dmca.html
    X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
    X-Postfilter: 1.3.40
    Bytes: 6300
    X-Received-Bytes: 6438

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From john larkin@21:1/5 to blockedofcourse@foo.invalid on Wed Oct 11 10:57:46 2023
    On Tue, 10 Oct 2023 20:29:29 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    On 10/10/2023 8:00 PM, whit3rd wrote:
    It's not always that simple; a firmware update, for example, has not only to >> be supplied to the customer, but has to be applied somehow to all the unassembled
    bits that are in the spare parts inventory for warranty repairs. It also might
    be the case that a faulty software means half a warehouse of install disks and associated
    packaging and documentation need a trip to the shredder.

    And then, there's the issue of notifications going out to the concerned parties...

    There are, also, industries where release engineering involves regulatory >approvals. You're not going to make even TRIVIAL changes to a piece
    of software in a medical instrument, gaming device, aero/astronautics, etc. >There are very tangible costs to those "bugs" and to "casual" changes
    to systems in which they could present.


    Yes, we avoid making such products. The engineering cost is multiplied
    by a big factor.

    But gaming device? How are those regulated?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to john larkin on Wed Oct 11 21:04:23 2023
    XPost: free.spam

    The arsehole john larkin <jl@650pot.com> persisting in being an Off-topic troll...

    --
    john larkin <jl@650pot.com> wrote:

    Path: not-for-mail
    NNTP-Posting-Date: Wed, 11 Oct 2023 17:57:45 +0000
    From: john larkin <jl@650pot.com>
    Newsgroups: sci.electronics.design
    Subject: Re: Another EV goes haywire!
    Date: Wed, 11 Oct 2023 10:57:46 -0700
    Message-ID: <tcodii136920kddcdhok262p5tjccssk75@4ax.com>
    References: <js10ii5ekb7c7ohr21i7l4o191q1mguf7o@4ax.com> <0350c1dc-889f-46fe-9d3e-e814d2f2b514n@googlegroups.com> <ufpjoj$1rduc$1@dont-email.me> <ufpqv8$1so3a$3@dont-email.me> <ufprab$1so3a$4@dont-email.me> <ug3fj5$14jm9$1@dont-email.me> <
    2nlaii1lahlb7utev0q7o3drd0e2iavo6r@4ax.com> <c9a7b216-aff1-4fc9-a123-5c0a761541e7n@googlegroups.com> <n3cbiih5tb1185p5ba7rlg6584snimuklk@4ax.com> <e3d8b63f-ee17-41dc-82cd-96b5d204699en@googlegroups.com> <ug54qr$1khqv$2@dont-email.me>
    User-Agent: ForteAgent/8.00.32.1272 trialware
    MIME-Version: 1.0
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Lines: 24
    X-Trace: sv3-lAXoHUeeImomxSLIyDNN4aQxOp2WcCE8G0TWri65gBV7vQmJxsRSJV6tfYrf1VwvHeVjuSdIXM/ocvF!uH13iGwtDtY8TuF/dly1zU8V3BIAEFD0KpW/AQkfBAuXqMcM4haqv+hA1m2ICvhVOHLLfNihGWaU!URK/BQ==
    X-Complaints-To: www.supernews.com/docs/abuse.html
    X-DMCA-Complaints-To: www.supernews.com/docs/dmca.html
    X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
    X-Postfilter: 1.3.40
    Bytes: 2560
    X-Received-Bytes: 2698

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)