Hi could you post some before and after traces (chrome dev tools recordings) of the site. Performance is nuanced, and the original tweet only helps to put down others (the react team) unfairly.

I think the win here is less about react and more about not running as much javascript on the client. I hypothesize that the traces will show this, but it is impossible to know for sure without them :)

Thanks in advance!

> the original tweet only helps to put down others (the react team) unfairly.

There was nothing personal or malicious in that slide at all. Do we need a safe space to talk about performance metrics now?

Let’s say you think it’s not React or you have time to improve React to solve that problem: wouldn’t having some data help test that assertion and make changes?

We have the data: they removed React and performance increased by 50%.

Why should any more work be put into keeping React or improving it if their solution of removing it entirely already works?

Well, for one, cause they did /not/ remove it entirely: They use it on the server.

It doesn't "work", it's a hack.

50% isn't data. It's a claim without evidence. The evidence in this case may help fix React.

Hey Hippich, it currently gives you node count, heapsize, and eventListeners after the action is taken and a "super" GC has been run https://github.com/samccone/drool/commit/4c3ac304448509afc08....

It is up to the consumer of the tool to decide what is really a failure and what actions are "clean"

Here is a nifty set of OS data to track the ebola outbreak https://github.com/cmrivers/ebola

author here:

Pioneer uses cucumber and Pioneer for its tests, you are correct. We also have a suite of unit tests that are powered by mocha.

Since we wanted true integration tests we choice to use Pioneer to test Pioneer. We wanted our feature files to act as documentation thus Cucumber was a clear choice.

As far as precedence goes ... This is not an uncommon pattern

Mocha uses mocha to test https://github.com/visionmedia/mocha/blob/master/test/http.m...

thanks for pointing that out, all resolved!

I'm seeing the same issue with other PSDs that generate Fs

If it is not resolving try these

http://psdlint.com http://www.psdgrade.com

True, but this is for HTML5 and not vimeo integration

RTFM -____-

http://vimeo.com/blog/post:268 http://vimeo.com/blog/post:334

hint.js wont work with the HTML5 player for vimeo and certainly won't work for the vimeo flash player.

Vire, however works for both. All with one line of code! Try it before you knock it!

I never knocked. I only said "alternative".

true, but froogaloop standardizes between vimeo's HTML5 player and flash player.