
Alex Gaynor
Occupation: Software Developer
Location: San Francisco
His ProfilesRankThis is the rank of 'Alex Gaynor' out of all Google+ Profiles.: 29,920 (GenderRankFor the gender 'Men'.: 18,271)
His ProfilesRankThis is the rank of 'Alex Gaynor' out of all Google+ Profiles. in United States: 6,878 (GenderRankFor the gender 'Men'.: 4,522)
His CircleRankThis is the rank of 'Alex Gaynor' out of all indexed profiles and pages at CircleCount.com.: 36,889
Followers: 2,852
Following: 160
Added to CircleCount.com: 07/13/2011That's the date, where Alex Gaynor has been indexed by CircleCount.com.
This hasn't to be the date where the daily check has been started. (Update nowYou can update your stats by clicking on this link!
This can take a few seconds.)
Alex Gaynor was in following circles
| Author | Followers | Date | Users in Circle | Comments | Reshares | +1 | Links |
|---|---|---|---|---|---|---|---|
| Tom Brander | 3,334 | 2012-03-05 15:51:34 | 471 | 4 | 0 | 0 | CC G+ |
| Tom Brander | 3,334 | 2012-01-08 18:54:03 | 466 | 20 | 0 | 0 | CC G+ |
| marius ibanez | 85 | 2011-12-13 23:07:17 | 489 | 0 | 0 | 1 | CC G+ |
| Marko Shiva Pavlovic (4N7IS3C) | 6,596 | 2011-10-16 02:43:11 | 501 | 38 | 8 | 21 | CC G+ |
| Andy Dustman | 753 | 2011-10-13 19:33:37 | 389 | 2 | 0 | 4 | CC G+ |
| Michael Bernstein | 8,885 | 2011-10-11 17:42:31 | 295 | 43 | 8 | 13 | CC G+ |
Latest postings
2013-04-14 18:33:44 (0 comments, 2 reshares, 9 +1s)
http://jmoiron.net/blog/whats-going-on/
Both authors blame bad habits and bad APIs for the slowness of scripting languages. Specifically, using hash maps instead of objects, and APIs that force you to allocate objects in order to do simple stuff.
While I agree that you shouldn't use a hash if you could instead use a real object it doesn't actually make any difference in V8. foo["x"] compiles to exactly the same thing as foo.x.
And as for allocation/GC overhead, I think it's overrated, at least if your language has a real generational GC. Bump allocation is very fast and young-space GC is also very fast. The suggested cures of reusing objects and buffers and designing more complex APIs that allow that will complicate your program considerably and expose you to a bunch of potential bugs. His example non-allocating C code looks very simple:
