Andrew - FinalsClub
andrew at finalsclub.org
Thu Jun 19 14:17:38 UTC 2014
I am a fan of vanilla JS over Coffeescript but wonder if this really adds much value at this point, particularly while in the midst of finalizing the first packaged release of Annotator 2.0.
If we compile all our current code to vanilla JS using something like js2coffee.org, that process will still require someone to spend considerable time cleaning up the resulting JS code.
Would we be better served for the time being by adding a few examples to the documentation showing both vanilla JS and Coffeescript side-by-side with some guidelines about how someone could write either style and submit a plugin, patch, or PR?
Also, @Nick, I still have to bug you about recording a live coding video for annotatorJS.org. Stay tuned.
> On Jun 18, 2014, at 2:40 PM, Randall Leeds <tilgovi at hypothes.is> wrote:
> On Jun 18, 2014 12:20 AM, "Kristof Csillag" <csillag at hypothes.is> wrote:
> > What do you mean by "switching"?
> > 1. Deciding to accept new incoming JS code, alongside new incoming Coffee code?
> > 2. Deciding that all new incoming code must be JS?
> > 3. Removing all the Coffee, and replacing it all with JS? (Either by automatic compilation, or manually?)
> At least (2), unless it's a patch to a file that's still JS. Probably (3) as soon as is reasonable.
> annotator-dev mailing list
> annotator-dev at lists.okfn.org
> Unsubscribe: https://lists.okfn.org/mailman/options/annotator-dev
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the annotator-dev