trevnorris

5 ms·

1. 1.▲
   by trevnorris 12y ago

   "Non-conforming" only means they didn't completely adhere to the ES specification. There should be no possibility of buffer overflow.
2. 2.▲
   by trevnorris 13y ago

   Here's a follow up to this completely misunderstood post: http://blog.trevnorris.com/2013/08/callbacks-what-i-said-was...
3. 3.▲
   by trevnorris 13y ago

   Thank you. Yes, that was more along the point. I just get punchy about how I say it after 3am.
4. 4.▲
   by trevnorris 13y ago

   > my closures are executed oh, about 100 times a second (e.g. completely negligible perf hit). This is a seriously flawed benchmark. Take Node's case where you're accepting HTTP requests. Each request is going to require a new
5. 5.▲
   by trevnorris 13y ago

   Ah yeah. I forgot that Buffer#fill() only returns "this" in master. I updated the example to fix this.
6. 6.▲
   by trevnorris 16y ago

   Those are some interesting ideas. You can look at what we've done at https://github.com/jstat/jstat The core.js file will run server-side. It has no dependencies and has been included using "this", which attaches to Node.js' modules. So t
7. 7.▲
   by trevnorris 16y ago

   We're getting one up and running on github. Sorry it's taken so long. Right now the code is being completely revamped for community involvement and extendibility. The address is https://github.com/jstat/jstat