Re: Python (was Re: Recent history of vi)

On 12/20/25 05:12, Richard Kettlewell wrote:
> candycanearter07 <[email protected]>
> writes:
>> Lawrence D’Oliveiro <[email protected]> wrote at 02:05 this Sunday (GMT):
>>> On 13 Dec 2025 11:55:35 GMT, Stéphane CARPENTIER wrote:
>>>> Everything else is just a lot of lies. They pretend it's not
>>>> strongly typed, but in the real world you will only encounter a lot
>>>> of issue if you believe that.
>>>
>>> Think about why both JavaScript and PHP need a “===” operator, while
>>> Python does not.
>>>
>>> It’s because Python is strongly typed.
>>
>> I thought it was because JS was too liberal with type-casting to make
>> things true, and the JS devs didn't want to break compatibility.
> 
> “No implicit type conversion” is one of the definitions of strong
> typing, at least back to the 1970s[1]. And JavaScript is certainly
> weakly typed in that sense:
> 
>      > 'a' + 1
>      'a1'
>      > 1/false
>      Infinity
> 
> What dividing by a boolean could possibly mean is a mystery, but
> JavaScript will do it anyway.
> 
> Python fits this definition of strong typing up to a point:
   Well, I kind of liked PICK system ... everything was
   equal, always represented as a string. Numbers, chars,
   whatever - instantly/easily converted between each other.
   NO 'types'.