Closed andylima closed 9 years ago
Thanks a lot for your feedback.
In fact, removing jQuery is already on my agenda.
Furthermore I even thought about removing JS entirely to just work with the css :target
selector, but I figured out that having the grey box beneath the menu might be a bit tricky then.
The truth is, getting into... "more serious" web development at the start of the smartphone era, I learned JS throughout jQuery (It made much more sense at that time aswell as IE6, 7 and 8 were awful). Hence I'm not good at vanilla JS. But I am willing to do so.
In other words: there will be a non-jquery variant coming within the next few days.
Wow, that was fast! ;) Thank you, @andreruffert !
Oh. This wasn't even you. I was just remembering Andre haha, well... good job by @andreruffert.
I really like how Paradeiser looks and works. Thank you! :)
My biggest suggestion is to remove the jQuery "baggage" — consider the following (quoted from the You Might Not Need jQuery site):
Main advantages:
Some resources that are helpful for switching from jQuery to native JavaScript:
There's also this one (a bit more advanced):
Mmm... Should I just say it? — "No jQuery" is the direction hipsters are taking. :D
The people in-the-know are now developing libraries without the jQuery requirement...
When feasible, a library should stand on its own feet — this way it is (more) future-proof, less dependent on other libraries, easier to get started with, and more flexible to be integrated in systems which don't use jQuery.
jQuery was created for a time when the DOM was hard. The DOM is pretty easy, now. ;)