jQuery as a Dependency
opened this issue · comments
I'm almost through with recoding cms.js to not rely on jQuery. Would that be something that I could attempt to merge, or should I keep that one on my own branch?
The main reason I ask is that some of my code replacements relies on ES6 which is fully supported in current browsers but is relatively new and may not work in older browsers.
I did already merge one piece of code for that which is a new way to do for: 'for (this of that)'.
Anyway, it's significant enough that I also wanted to get some opinions as I know while there would be advantages to not requiring jQuery that there may be reasons people want it to stay.
Thanks @barryanders I'm definitely open to using vanilla JS and was thinking of converting it down the line myself. Although, I would really like to keep support for ES5 though being that CMS.js is in the early stages of development/usage...at least for now until the ES6 gap is tightened.
+1 to remove jQuery as a dependency
In progress: #42
Looking through old issues and I noticed that #42 was closed, which was in part the same issue as this. If someone else wants to carry this on, feel free to start a new issue. I think cms.js is really cool and may make a nice smooth framework for non blog situations too (ex. electron apps). The remaining pieces that rely on jQuery are pretty heavily coded in from what I remember. It would require a lot to completely remove jQuery. In the spirit of closing old issues that are no longer being considered, I'm going to close this to clean up my list of open issues.