As a seasoned developer with a build-stack that I like to adapt and re-use on different projects, I'm curious why enyo went with a custom script loader rather than using or integrating with something like require.js?
I like a lot of what I see with enyo, but need the flexibility to use things like require.js plugins for live development (i.e., coffeescript), and the r.js optimizer for building a production package.
This kind of flexibility seems like it would be a huge hassle in enyo right now, and enyo's loader/build process, while simple to use, feels a bit like a straight-jacket.
Or did I miss something in my initial review of the docs/source?
0 · ·