3 ms·
This isn't letting you work with the DOM directly...it is yet another library which encompasses the DOM API...just like jQuery. It only feels a bit more natura
by reflectiv 13y ago
This isn't letting you work with the DOM directly...it is yet another library which encompasses the DOM API...just like jQuery.
It only feels a bit more natural since the style it uses feels more direct...this is just another javascript wrapper for the DOM...a problem we (basically) solved with jQuery.
I also find myself rarely using jQuery for much these days when I use various MV* javascript libraries. This library looks neat, but I don't need to replace a library I use less and less...and has no real benefits other than size and API differences (that can basically be mapped to each other 1:1).
- nadabu 13y agoEh, not a wrapper, sorry. It's a helper that directly extends the DOM to provide syntax sugar. Yes, it is not pure DOM interface, but if it were, then the library would be a whopping 0KB. :)
- reflectiv 13y agoThat teaches me for not looking at the source prior to commenting...my apologies (I am at work on limited time)... I still feel this library (with the exception of the cleaner feeling API) is not much more than a wrapper/extension around the native functionality. But good job on making it pleasing to work with (as it appears to be), and the website around introducing it is also quite nice...if I was using these DOM-wrapper-sugarizing libs to any serious degree these days I would likely consider it. Overall this looks nice, but I feel like the javascript world is mostly moving away from the whole 'modify the layout that is pre-generated' and more towards a data driven/render what I specify world...
- nadabu 13y agoYeah, i agree, which is one reason heavy-weight DOM manipulators are losing ground to small components. There will always be some need for working with the DOM though.
- SimHacker 13y agoMore like "Syntactic Olestra".