That’s an interesting proposal but I’m struggling to think how that would solve this same issue 2 or 3 or 5 years down the line? JavaScript and browsers have a symmetry along with HTML, CSS... and given the disparity of devices today alone, let alone tomorrow a new major version would cause more harm than good. Ideally we would need a solution that works as ES5 as standard, then have that semantic in later versions of the language.
Perhaps this is not a problem for this community but something browser providers should be providing / considering to allow developers to specify their runtime in order to allow the language to progress more natrurally? > On 23 Jul 2017, at 23:38, doodad-js Admin <[email protected]> wrote: > > Maybe that's time to start a new major version of JS? > > -----Original Message----- > From: David White [mailto:[email protected]] > Sent: Sunday, July 23, 2017 5:54 PM > To: [email protected] > Subject: Re: Re: Removal of language features > > Lots of good thoughts and discussions here, and while it’s gone slightly off > topic I’d love to discuss the possibilities of how we could get JavaScript to > a point where we could actively remove features with every new specification. > > I’m sure nobody would want to break the web, which would be very likely > removing any parts of JavaScript, and certainly the biggest challenge, it > does seem a shame that we can’t find an ulterior direction as it does seem > allowing various features we consider bad practice today to still exist and > the overhead that exists with them certainly hinders progress more than it > helps. > > Linting is certainly the fastest and easiest method, but to a certain extent > I not really a solution in that we only lint our own code, and not the > additional code that we rely upon. Ideally removal of features should mean > more performance out of JavaScript, if engines have less constructs to deal > with then there should be some beneficial performance related with that? > > Given the lack of control over what browsers many users are using perhaps > versioning could be a new semantic built into the language itself in the same > way we have strict mode? > > We could allow developers the option to specify the version they wish to use, > avoiding unnecessary transpiration back to ES5 for applications confident > enough to give their users the choice to upgrade if needed but also allow > browsers to only run based on versions? > > I'm sure it’s worth considering as removing features of a language / > application is as important, if not more so, than adding features to a > language or application. > > David > _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
