Re:The State of Meteor Part 2: What Happens Next
by rimantas on Thursday January 21, 2016 @01:16AM
(#10943678)
That need was filled by Prototype.js before jQuery. I remember the times when Rails defaulted to Prototype (author was a member of Rails core team, iirc). I also remember when we still had to choose between the two for the new project and I was unhappy if the choice was Prototype. So they both solved the problem, but jQuery's solution was more focused and way more elegant.
[ Parent
| on HN ]
Re:The State of Meteor Part 2: What Happens Next
by apalmer on Thursday January 21, 2016 @01:54AM
(#10943766)
thing about prototype is it fundamentally changed how you dealt with javascript.
jquery was just easy dom selection and manipulation, easy ajax, and easy events... you could drop it into any project and it didnt really proscribe anything else...