Top all-time · #3222
getiblog
Personal blog · blog.getify.comprogrammingweb
getiblog is a personal blog at blog.getify.com about programming and web. Since 2009, 24 different Hacker News readers have linked it 42 times, most often ““Why I'm Not Waiting on 'await'”; 2-pt blog post on pros/cons of 'async..await'”. No feed was found, so read it on the site itself.
Too few sampled comments (5) to say how often HN recommends it.?
Why HN links it
HN readers link getiblog for its LABjs posts on loading JavaScript in parallel versus concatenating files, and for a critical write-up of async and await. Other comments cite it without judging it.
Summarised by Claude from a sample of 5 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- “Why I'm Not Waiting on 'await'”; 2-pt blog post on pros/cons of 'async..await'3 people · 3 mentions · first linked 2016-05-24
- Technical Interviews Suck2 people · 2 mentions · first linked 2013-04-15
- Dev Consoles Considered Harmful2 people · 2 mentions · first linked 2015-03-12
- Teaching: Convergence and Divergence2 people · 2 mentions · first linked 2016-05-03
- Promises: The Inversion Problem (part 2)2 people · 2 mentions · first linked 2014-05-19
- /2009/11/labjs-why-not-just-concat/2 people · 2 mentions · first linked 2011-01-31
What Hacker News says?
I won't do tech interviews either, but not because I think I will fail at them. I think they are completely bogus and give totally the wrong signal. It's a waste of my time AND the company's time. I wrote up my thoughts on this exact thing a few months back: http://blog.getify.com/technical-interviews-suck/ TL;DR: Everything you need to know about if I'm a good fit is available online in my OSS (et al) track-records…
Comment linking /technical-interviews-suck/
on “I will not do a tech interview”Submitted Constantly Confusing ‘const’ as a story · 33 points
HN discussionHere's a nice writeup that's critical of async and await: https://blog.getify.com/not-awaiting-1/
Comment linking /not-awaiting-1/
on “Async and Await”Submitted On Script Loaders as a story · 26 points
HN discussionPromises are actually about trust, not syntax. With a callback you have to trust that the function that will invoke your callback (which might not be something you wrote) will only ever call it once, that it will pass through errors, that it won't call both your success and failure callbacks, etc. With a promise (or rather, following the promise specification) you instead get back an object that you choose how to ha…
Comment linking /promises-part-2/
on “Node.js stream handbook”Submitted Teaching: Convergence and Divergence as a story · 20 points
HN discussionThis has been shown to not necessarily always be the best option for performance. See http://blog.getify.com/2009/11/labjs-why-not-just-concat/ , and http://yepnopejs.com/ The best and brightest in the JS performance area now mostly advocate using some form of loader to load the JavaScripts, bearing in mind that the overall page speed and perceived performance can be affected by more factors than simply the number o…
Comment linking /2009/11/labjs-why-not-just-concat/
on “Show HN: MicroEvent.js - js micro event emitter in less than 20lines”Submitted Silly Rabbit... Frameworks are for Prototypes as a story · 18 points
HN discussionIf you want more information, here's some blog posts I did to explain LABjs: http://blog.getify.com/2009/11/labjs-new-hotness-for-script-... There's also posts on the site about LABjs in relation to: * speeding up DOM-ready * coupling inline script execution * concat'ing versus parallel downloads
Comment linking /2009/11/labjs-new-hotness-for-script-loading/
on “LABjs : Loading And Blocking JavaScript”Submitted Unimorphic Isoversal JavaScript What? as a story · 13 points
HN discussionActually it makes a ton of sense to asynchronously require javascript files on your production page. If you load them asynchronously and in parallel, you can often get much better performance than one single request (serially). http://blog.getify.com/2009/11/labjs-why-not-just-concat/
Comment linking /2009/11/labjs-why-not-just-concat/
on “Browser-require.js brings "require" to the browser (just like node)”Submitted On the nature of timers as a story · 12 points
HN discussionSubmitted Thoughts on Thunks; How JavaScript thunks explain promises as a story · 5 points
HN discussionSubmitted “Concurrently JavaScript”; exploring concepts of concurrency, parallelism, async as a story · 5 points
HN discussionSubmitted “Promises: All the Wrong Ways” exploring promise anti-patterns as a story · 4 points
HN discussionSubmitted “Why I'm Not Waiting on 'await'”; 2-pt blog post on pros/cons of 'async..await' as a story · 4 points
HN discussionSubmitted Coordination of concurrency and true parallelism via Remote CSP Channels as a story · 4 points
HN discussionSubmitted Promises: The Extension Problem (part 4) as a story · 4 points
HN discussionSubmitted “Arrow This”: clearing up how ES6 = arrows handle 'this' and others as a story · 3 points
HN discussionSubmitted Promises: The Trust Problem (part 3) as a story · 3 points
HN discussionSubmitted Promises: The Sync Problem (part 1) as a story · 3 points
HN discussionSubmitted Adaptive Hybrid JavaScript as a story · 3 points
HN discussionSubmitted IE11: please bring "real script preloading" back as a story · 3 points
HN discussionSubmitted Why I’m Not Waiting on ‘await’ (part 1) as a story · 2 points
HN discussionSubmitted Teaching: Convergence and Divergence as a story · 2 points
HN discussionSubmitted Concurrently JavaScript (2) as a story · 2 points
HN discussionSubmitted JavaScript Promises: Sync, Inversion, Trust, and Extension as a story · 2 points
HN discussionSubmitted Promises: The Inversion Problem (part 2) as a story · 2 points
HN discussionSubmitted Obsessions: HTTP Request Reduction as a story · 2 points
HN discussionSubmitted Technical Interviews Suck as a story · 2 points
HN discussion
