Yes I agree. Using native javascript for specific tasks such as this is probably a good idea in terms of minimising the size of your assets and maximising performance. It can be especially satisfying for the programmer as well.
I do understand the need/popularity of libraries like jQuery however; In development teams there aren't always dedicated people for 'just' the back-end or 'just' the front-end. Most people do both in varying levels of competency, a library like jQuery makes it a lot easier for people less at home in the front-end to create things. 'Easiers' because of the cross-browser compatibility, consistency and the fast amount of online resources. So I do get it, while it is still not that hard to pick up some new things.
If you are in the front-end a lot/only then sticking to gigantic frameworks without using more modern javascript is just a shame, because it can bring you great benefit.
I do understand the need/popularity of libraries like jQuery however; In development teams there aren't always dedicated people for 'just' the back-end or 'just' the front-end. Most people do both in varying levels of competency, a library like jQuery makes it a lot easier for people less at home in the front-end to create things. 'Easiers' because of the cross-browser compatibility, consistency and the fast amount of online resources. So I do get it, while it is still not that hard to pick up some new things.
If you are in the front-end a lot/only then sticking to gigantic frameworks without using more modern javascript is just a shame, because it can bring you great benefit.