I was lucky enough to join this session (TensorFlowJS) at Google IO a few days ago. You will see a big jump here soon with their adaptations: https://www.youtube.com/watch?v=OmofOvMApTUhttps://www.youtube.com/watch?v=OmofOvMApTU
@webdevinci
Nothing here yet.
Nothing here yet.
No blogs yet.
I was lucky enough to join this session (TensorFlowJS) at Google IO a few days ago. You will see a big jump here soon with their adaptations: https://www.youtube.com/watch?v=OmofOvMApTUhttps://www.youtube.com/watch?v=OmofOvMApTU
Had a chance to do some big javascript refactoring at work, and something I noticed was the amount of timers on a single script of ours (over 10 setInterval() calls). I responded by created a single timer object to pipe all of those individual timers through. We found a significant performance gain, ~10% faster load time for that particular script: https://gist.github.com/webdevinci/aeb7e568c3e3cbe0d89eb28664ddeb9c
Point taken I am biased against jquery of late, because it isn't needed, nor do I think it's needed to learn since it will be gone one day (like most things). But some ridiculous number of sites still use jquery, https://trends.builtwith.com/javascript/jQuery (many sectioned off at over 70%!). I guess that's one reason to learn, if you are to work in any company with legacy code; which I would still advise to convert :) I literally saved 2-3 seconds by converting a jQuery app to native JS (pre ES6)... just using 'this' instead of '$(this)' 100's of times will help you app perf. Hell, most people diving into jQuery don't even understand that $() is the start of a long function call
100! No need for jQuery any more (except maybe x-browser stuff, but even that you can shim out yourself and not have as much overhead). Francesco Boffa , agreed! Not just because of ES6, but because of the idea of being a proficient JS fundamentalist. Most people that learn jQuery don't know whats happening behind the scenes, how sizzle engine works, etc.