はてなブックマーク

Table of Contents My Issues with AMP As a Publisher My Issues with AMP as a User Scrolling sucks Sharing links is hard AMP content is usually butchered AMP is not optional for users Why I Enabled AMP on my site in the first place It is spreading Users don’t need AMP Please speak up I have a long history with Google’s Accelerated Mobile Pages (AMP) project, but yesterday I drew the final straw. I w

Table of Contents IntroductionMinimal TheoryStep 1. Reproduce and confirm the problemStep 2. Take at least 3 Heap dumpsStep 3. Find the problemStep 4. Confirm that the issue is resolvedLinks to some other resourcesSummary Something you might want to bookmark: Simple Guide to Finding a JavaScript Memory Leak in Node.js by @akras14 https://t.co/oRyQboa8Uw — Node.js (@nodejs) January 6, 2016 Please c

Table of Contents: Parameters for better logging git log --oneline --graphLog actual changes in a file git log -p filenameOnly Log changes for some specific lines in file git log -L 1,1:some-file.txtLog changes not yet merged to the parent branch git log --no-merges master..Extract a file from another branch git show some-branch:some-file.jsSome notes on rebasing git pull --rebaseRemember the bran

I am new to Angular (even though I am not new to the web development), so please take everything that I am about to say with a grain of salt. That being said, I watched a lot of talks and read a lot of articles relevant to Angular performance, and this post is the summary of my findings. Table of Contents 1. Minimize/Avoid Watchers 2. Avoid ng-repeat. If you have to use ng-repeat use infinite scro

Why do we care? Most of out time is spent maintaining code. If you open an editor and: It’s blank – you are writing new code.Something already there – you are maintaining code. Most of us learned JavaScript on our own and developed our own “best” practices Maintainability = Developing as a Team What is Maintainable code Works for 5 years without having to rewrite Maintainable code is: Intuitive –