It is important to note here to the casual observer, that of course
not _all_ configuration will be moved to package.json - only the stuff
that fits there better.
Darryl explained that above, this is mainly about moving the
"dependency" definitions right now - the rest will stay unchanged.
-J
Am D
I would not personally favor using ES6 classes, here are my main reasons:
* ES6 class is really sugar around prototypal inheritance, unlike many
other languages
* In many cases it is better to use functional programming and factory
functions than classes
Some reading:
*
https://artem.today/what-i
I was wondering what our sentiment should be about using ES6 classes?
My own opinion in coming in a response email.
-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.ap
Nightly build #926 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g
cordova@nightly'
For details check build console at
https://builds.apache.org/job/cordova-nightly/926/consoleFull
-
Jenkins for Apache Cordova
-
I both agree and disagree with your points :P
To your first point, yes ES6 classes are just syntactic sugar around
prototypes, but that sugar exists for a reason and it's extremely
popular now. Personally, I've been using class syntax at work for
going on three years now, and looking at some parts
+1 for using modern JS wherever applicable.
Am Fr., 30. Nov. 2018, 06:55 hat Darryl Pogue
geschrieben:
> I both agree and disagree with your points :P
>
> To your first point, yes ES6 classes are just syntactic sugar around
> prototypes, but that sugar exists for a reason and it's extremely
> po
