I woke up very hung over this morning and started thinking about how I was going to the solve the issue of button pressed states not working properly on touch devices in the corporate container app for my current work project. I had googled a lot for it already, but this time I decided to try to google for videos. I came across this video. Honestly, he doesn't talk much about touch device specific things here; it just has Touch Screen in the title because the actual project was meant to run on that giant touch panel on the left there in the video preview. However, I still enjoyed this video and liked getting inside of this guy's head. He reports directly tot he CEO of his company he's in charge of basically all aspects of building the software and getting it out so you know that he has successfully completed at least a few projects (although he admits that he is pretty new to AngularJS). Overall he gives some insight on thinking about custom directives (although he has a weird style where inside of the .directive() he just returns basically the equivalent of the link function, but nothing is labeled in the way you might be used to seeing directives). He also does some other weird things like using Coffeescript, Haml, and he talks about the yeoman seed project as if there's only one. hehe. But weirdness aside, it's a good video, and you should give it a watch.
Key Takeaways
- Local Storage- Early on in the video he mentions that he uses local storage a lot to improve performance. This makes sense, and we know that of cookies, cache, etc. the local storage is the best because it will stay saves even after everything is closed and turned off (that is what you wanted, right?).
- Directives as "Reusable Things" - Jim talks briefly about his experience working with the ui designer and how he says to himself, "Oh, we're using this thing in a lot of places. Let's make it a directive!". I think this makes perfect sense. A directive can just be an html tag that you stick in the HTML wherever it's needed (although in 1.5 you might make it a 'component' instead of a directive).
- Angular on backend?? - He says, "Angular isn't great for everything", but then he starting talking about how Angular isn't good for the backend and how he wants to rewrite the backend in Angular (~6:00 in the video). First of all, I didn't even know 'Backend Angular' was a thing. And second, that's just weird. If I was writing a backend I would just use NodeJS, or even better: Node-Red.
- It's interesting that he mentions a blog post by Joel Hooks (the big egghead.io instructor) that basically says, "Jquery is a Crutch" and that you should just use the jqLite with Angular. I avoid using jquery selectors as much as possible, but honestly when I run to Gulp-Angular generator to scaffold a new project I usually just go with the default choice which is described in the yeoman answer as, "jQuery 2.x (new version, lighter, IE9+)".
- Memory Leaks - It was very interesting to heard his story about how they found huge memory leaks in the application. Basically, they had a clock directive that was calling a $timeout every second, and the memory was piling up. I was surprised that his performance profiling tools was just regular out chrome dev tools! He said the app would go up to several hundred megabytes and then just crash, and even showed the code that fixed the leak (calling the cancel method on the timeout that is triggered every second),
RSS Feed