Which JavaScript library has been the most impactful on your career or personal development?
@davidwalshblog Native c/c++ and java was dry, JQ, Angular, Vue almost made me want to quit. I skipped React at first because it seemed different, eventually tried and it matches my thought process so well, i didn't feel the struggle when trying to translate ideas into something concrete.
@davidwalshblog @angular ❤️ and here is why... dev.to/angular/why-do…
@davidwalshblog Thought of it first before looking at your profile — I’d been so enamored with Mootools early in my career (14 years ago), it had this elegant simplicity to it I haven’t seen before. Read the source code with joy and learned so much
@davidwalshblog D3.js. there weren't as many visualization services when I started and I've been asked to teach it early in my career. Being a speaker brought a lot of amazing people in my life.
@davidwalshblog Angular 1.X, started out well from 2013 and almost ruined my career. Defending it forced me to have to learn everything about JavaScript to only to realize how wrong I was. The excruciating embarrassment was one of my biggest lessons (2015).
@davidwalshblog jQuery. I’ll leave you to figure out how old I am… 😂
@davidwalshblog React for sure I don't play around with jQuery spaghetti code 🤣
@davidwalshblog Jquery because I'm old, apparently... Seriously though, I hated Javascript (and front end) in the dark days of ie 800x600 netscape optimised websites. Jquery changed that, and I'll be forever grateful.
@davidwalshblog @emberjs by far! I owe a whole lot of my present expertise to Ember and the amazing community. I often say that I was a bad JS developer before Ember 😂
@davidwalshblog I learned 80% of what I know about programming from AS3 and Flex, occasionally I feel that tech is revisiting those two with different names. JQ was impactful but I felt the pain. Swift for pushing me to mobile-dev, and Flutter for giving me hope of true cross platform-dev...
@davidwalshblog JQuery has been invaluable. I've also grown a liking to Slick slider and Flexslider. Honorable mentions includes bxSlider and jCarouselite. Polyfills for media queries and matchMedia from Paul Irish have also been invaluable. Modernizr helped tremendously.
@davidwalshblog Ramda changed how I approach algorithms and deal with failure cases, and given me much more confidence in my test suites. I can count on one hand the number of for/while loops I've written since 2015.
@davidwalshblog Does Node.js count as a "library"? :P (I guess it's more of a JavaScript runtime + standard library + ecosystem) But yes, Node.js probably was the most impactful. I've been able to script away so many problems, from very simple to highly complex, both at work and in private. 🚀
@davidwalshblog Knockout.js. It was my first JS framework with data binding (same as Angular), and felt like the first JS framework that could be used to build full SPAs, instead of just adding some dynamic functionality to server side rendered pages.
@davidwalshblog It's @d3js_org and @mbostock 's examples. Made me love maps and visualising the real world, and appreciate the vast amount of datasets out there
@davidwalshblog Vue.js was an eye opener after years of jQuery hell.
@davidwalshblog I'm actually going to veer away from some of the obvious one and say lodash. Not only was the functionality extraordinarily helpful but the sheer size of the library (and thus importing only individual parts) helped me appreciate how bloated these things can get
@davidwalshblog @emberjs for sure. And today it's even better!
@davidwalshblog jQuery was like first course, Ractive.js was the eye opener as well module pattern in JavaScript to "bundle" your globals and access them easy. Fun fact Ractive.js was created by @Rich_Harris and Svelte is the next generation of it.
@davidwalshblog @JavaScriptDaily backbone.js was most impactful. Loved the literate self documenting style of the code, and clear concise design principles. Almost every modern SPA library/framework stands on its shoulders.
@davidwalshblog jQuery. I eventually felt like I could pretty much do anything I needed to do with jQuery. That was great for many years. Then React came along and overnight everyone stopped using jQuery and I want back to feeling like I knew nothing. Now I’m digging React. It’s an endless cycle
@davidwalshblog MooTools. It introduced me to OOP in JavaScript and made me realize the browser capabilities
@davidwalshblog jQuery 💯 Definitely jQuery marked the path of my JavaScript career 👩🏫
@davidwalshblog Often feels like I learned everything I know working with and on @LeafletJS. React some distant second place, I guess.
@davidwalshblog @JavaScriptDaily Caolan/async. It changed async programming and callbacks from something I was scared of into a superpower I could control. github.com/caolan/async
@davidwalshblog Dojo. Especially dijits and build tooling.
