For understanding the current status, I think that the following documents will
be helpful.
The note and slide for the 66th meeting of Ecma TC39
https://github.com/rwaldron/tc39-notes/blob/master/es9/2018-09/sept-26.md#decorators-stage-2-update
I'm not from TC39, but I can hazard a guess.
Decorators are somewhat useless without data properties to modify.
Currently, class-fields is the proposal du jour, but even while in stage 3,
it has issues, requiring trade-offs that many have voiced an unwillingness
to accept. The awful syntax is
Supposed to land in ES2016, decorators haven't moved from Stage 2 for more
than a year now.
In various other discussions everyone has the easy "use decorators" answer
for any problem, and yet no browser ships decorators, and no stage 3 is
happening neither.
Is there already a better replacement
It's a great read and it makes sense in some case, but it also reminds me
too much how Android Apps, and their incremental permission model, work.
If an App had granted access to read or write files, and the company behind
such App changes, or its developers change, the permission remains but
The npm / event-stream incident is the perfect teaching moment for POLA
(Principle of Least Authority), and for the need to support least authority
for JavaScript libraries.
https://medium.com/agoric/pola-would-have-prevented-the-event-stream-incident-45653ecbda99
by Kate Sills (cc'ed) explains
5 matches
Mail list logo
