Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #124439
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Newsgroups | comp.lang.javascript |
| Subject | Re: 30 Years Of JavaScript |
| Date | 2026-07-13 22:31 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <1133ov4$3ul2m$2@dont-email.me> (permalink) |
| References | <vuc5g5$dmqd$1@dont-email.me> <1132o8b$3jv8i$1@dont-email.me> |
On Mon, 13 Jul 2026 16:12:42 +0300, Mikko wrote: > I would like to have the semicolons mandatory. So would I. But given that they’re not, we have to work with the language as it is specified. > At least '===' and '!==' are there so there is no need to use '==' > or '!=' when one doesn't want. Think about why a language like Python doesn’t need “===” and “!==”. It’s because it eschews the more error-prone automatic type conversions, so it doesn’t need a way to turn them off. > Fortunatly conditions are usually in contexts that marks them as > conditions. And if an expression returns certain values, the result of (mis)interpreting them as booleans can be ... interesting. > One problem with many program languages is that the program does not > identify the revision of the standard. This would be important with > Javascript as the same program is intended for a large variety of > implementations that are not updated to the latest revision or are > aleady updated to a revision that is published after the publication > of the program. HTML used to have “<script language=javascript>” versus “<script language=javascript1.2>” etc. For some reason that was considered more trouble than it was worth. > The subject line means that Javascript already existed 30 years ago. > In some sense that is false: the Javascript that we know today is > not the same as the Javascript 30 years ago. So when did today’s JavaScript come into being? How old would you say it really was, if not 30 years?
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
30 Years Of JavaScript Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-04-24 01:52 +0000
Re: 30 Years Of JavaScript Mikko <mikko.levanto@iki.fi> - 2026-07-13 16:12 +0300
Re: 30 Years Of JavaScript Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-13 22:31 +0000
Re: 30 Years Of JavaScript Mikko <mikko.levanto@iki.fi> - 2026-07-14 09:59 +0300
Re: 30 Years Of JavaScript Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-14 07:27 +0000
Re: 30 Years Of JavaScript Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2026-07-18 04:51 +0200
Re: 30 Years Of JavaScript John Harris <niam@jghnorth.org.uk.invalid> - 2026-07-14 10:50 +0100
Re: 30 Years Of JavaScript Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-14 22:12 +0000
Re: 30 Years Of JavaScript John Harris <niam@jghnorth.org.uk.invalid> - 2026-07-15 11:01 +0100
Re: 30 Years Of JavaScript Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2026-07-18 04:46 +0200
Re: 30 Years Of JavaScript Mikko <mikko.levanto@iki.fi> - 2026-07-19 11:40 +0300
Re: 30 Years Of JavaScript Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-19 23:29 +0000
Re: 30 Years Of JavaScript Mikko <mikko.levanto@iki.fi> - 2026-07-20 09:42 +0300
Re: 30 Years Of JavaScript Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-20 08:08 +0000
Re: 30 Years Of JavaScript Mikko <mikko.levanto@iki.fi> - 2026-07-21 08:57 +0300
Re: 30 Years Of JavaScript Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-21 23:08 +0000
Re: 30 Years Of JavaScript Mikko <mikko.levanto@iki.fi> - 2026-07-22 09:39 +0300
Re: 30 Years Of JavaScript Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2026-07-27 14:20 +0200
Re: 30 Years Of JavaScript Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2026-07-27 14:19 +0200
Re: 30 Years Of JavaScript Jon Ribbens <jon+usenet@unequivocal.eu> - 2026-07-13 14:46 +0000
csiph-web