jsPerf

@jsperf

JavaScript performance playground

The interwebs
jsperf.com
Joined August 2010
4 Photos and videos Photos and videos

Tweets

You blocked @jsperf

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @jsperf

  1. 29 Dec 2016

    📢 jsPerf is looking for sponsors! Background:

    3 replies 5 retweets 6 likes
    Undo
  2. 29 Dec 2016

    jsPerf is now back online, thanks to the lovely people at !

    1 reply 1 retweet 9 likes
    Undo
  3. 27 Dec 2016

    Yes, jsPerf is down. Please bear with us as we’re working with to bring it back!

    Undo
  4. 8 Dec 2016

    Mr. is brainstorming an incremental jsPerf redesign. Here’s his first proposal: Feedback welcome!

    Image
    3 replies 4 retweets 12 likes
    Undo
  5. 19 Nov 2016

    Open source haters gonna hate

    Replying to @jsperf
    no. Just won't bother using your broken site.
    1 reply 4 retweets 7 likes
    Undo
  6. 18 Oct 2016

    jsPerf is back online! This is v2-beta, powered by Node.js. Please help make it better:

    5 replies 161 retweets 194 likes
    Undo
  7. 16 Oct 2016

    Watch this space.

    Image
    5 retweets 15 likes
    Undo
  8. Retweeted
    24 Jun 2015
    Replying to

    Huge props to and offering to help. That's some serious muscle against the spammers!

    1 reply 2 retweets 14 likes
    Undo
  9. Retweeted
    24 Jun 2015

    If you can, help get back online:

    1 reply 8 retweets 3 likes
    Undo
  10. 3 Mar 2015

    . is working on a new version of the jsPerf back-end, running on io.js: Contributions welcome!

    12 retweets 12 likes
    Undo
  11. 1 Jul 2014

    In response to the massive spam flood that jsPerf has been experiencing the past few days, we’ve now enabled . Fingers crossed.

    14 replies 3 retweets 1 like
    Undo
  12. Retweeted
    17 Jun 2014

    "jsPerf becomes tremendously powerful—when you need to compare true bottleneck situations across many environments" –

    2 retweets 4 likes
    Undo
  13. 22 Feb 2014

    Nice UI proposal to make this easier to spot which revision of a test case is the most authoritative:

    2 likes
    Undo
  14. Retweeted
    14 Feb 2014

    Just received a DMCA takedown notice for a coding challenge (a few paragraphs of text) that a user posted to . ©

    3 replies 5 retweets 5 likes
    Undo
  15. Retweeted
    4 Jan 2014
    Replying to

    And in particular, see the Firefox 29 numbers at (needs tomorrow's nightly to reproduce, probably).

    2 replies 5 retweets
    Undo
  16. Retweeted
    4 Jan 2014

    Taught IonMonkey about non-effectful DOM methods, so we can do CSE, LICM, DCE on them. More caveats for the microbenchmarker!

    2 replies 19 retweets 11 likes
    Undo
  17. 5 Jan 2014

    Please stop the jsPerf abuse: by

    2 replies 35 retweets 26 likes
    Undo
  18. 4 Oct 2013

    Great talk by , explaining why microbenchmarks are evil and should be avoided: Please use jsPerf correctly!

    52 retweets 74 likes
    Undo
  19. Retweeted
    25 Aug 2013

    jsPerf has moved charts to an iframe to avoid JIT issues w/ Google Charts & DOM de-optimizations in Firefox. TIL Google Charts hurts FF JIT.

    1 reply 3 retweets 3 likes
    Undo
  20. Retweeted
    6 Aug 2013

    Updated . Uses lodash internally for _.isPlainObject, _.partialRight, _.forOwn, _.cloneDeep, _.support, & ES6 template delimiters.

    3 replies 2 retweets
    Undo

@jsperf hasn't Tweeted yet.

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·