Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.misc,alt.folklore.computers,comp.lang.python
Subject: Re: Python (was Re: Recent history of vi)
Date: 20 Dec 2025 05:48:58 GMT
Lines: 20
Message-ID: <mqmrmaF2n74U5@mid.individual.net>
References: <CtydnVqzjrtfd5P0nZ2dnZfqn_adnZ2d@giganews.com> <10fc99s$309k$1@dont-email.me> <10fco97$6fc7$5@dont-email.me> <mnumuiF7n72U5@mid.individual.net> <mnuptvF8hn7U1@mid.individual.net> <10fddvm$dsjl$3@dont-email.me> <10fig07$8oe$1@news.misty.com> <akjvulxcnk.ln2@Telcontar.valinor> <slrn10hrfud.a0q.apple.universe@freight.zombinet> <10fvcgr$3d6mu$1@paganini.bofh.team> <slrn10ib12n.hfr.apple.universe@freight.zombinet> <10g526s$3o78s$1@dont-email.me> <10ga7mg$7ph$3@news.misty.com> <wwvecpjp5nw.fsf@LkoBDZeT.terraraq.uk> <slrn10ik3ub.2dppt.als@mordor.angband.thangorodrim.de> <10gekt9$39ian$4@dont-email.me> <10gfihn$3lshj$1@dont-email.me> <10gh6oj$83hq$8@dont-email.me> <wwv1plf6apd.fsf@LkoBDZeT.terraraq.uk> <10ghqrq$g7pg$1@dont-email.me> <wwvy0nma8fp.fsf@LkoBDZeT.terraraq.uk> <693d5437$0$2499$426a34cc@news.free.fr> <10hl622$jeli$11@dont-email.me> <slrn10kakjl.14g1t.candycanearter07@candydeb.host.invalid> <10i4e92$1f2vl$2@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net tnmoMw5COeysrhoCarrD3wTL1RscohOwhLIeSlx7Jnu3UDbDW4
Cancel-Lock: sha1:f5I0DYlttxsWlaMy1whCRFViMQw= sha256:oitfV5kt7gs9CgFO97BfO+bIyKiVJWhARCI6nW9h/Q4=
User-Agent: Pan/0.162 (Pokrosvk)
Xref: csiph.com comp.os.linux.misc:79541 alt.folklore.computers:232720 comp.lang.python:197644

On Fri, 19 Dec 2025 20:58:10 -0000 (UTC), Lawrence D’Oliveiro wrote:

> On Fri, 19 Dec 2025 13:30:03 -0000 (UTC), candycanearter07 wrote:
> 
>> Lawrence D’Oliveiro <ldo@nz.invalid> wrote at 02:05 this Sunday (GMT):
>>>
>>> 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.
> 
> Is there some other interpretation of “strongly typed”?

I haven't worked with them enough to know if type hints are useful or if 
they're like TypeScript's attempt to rein in JavaScript. It's like the 
dunders that are like saying 'Please mugger, don't take my IPad' rather 
than something that is enforced.