So the team working on the brand spanking new Inferno website is looking for example components to include in the website which you can see here in beta: https://beta.infernojs.org/.
We'd like to populate the page with 3-5 new examples. We would like examples that focus on varying use cases that expone the power and ease of the library. Here are some general ideas in case anyone is interested in contributing:
Of course the examples should not be limited to these general concepts. Matter of fact if you don't have time to contribute source, post an idea for an example and perhaps another community member might take it on.
Can't wait to see what everyone comes up with.
Eventually we'll ask everyone to post their examples at https://github.com/infernojs/inferno-examples but for now we'll collect general concepts.
As incentive I'm giving away $10 Starbuck cards for contributions. We will likely pick 3-5 examples to choose your examples wisely :-)
A React compatibility
How about using something like react-toolbox with inferno compat?
Pigeon-maps was ported to Inferno. I believe it will be on the main branch tomorrow. We should definitively do a Maps-Inferno thing, performance is a beast on pigeon-maps-inferno!
I guess we could do one of SSR+styled components/aphrodite/cxs/whatever too
@degroote22 wow, looks great. As an example it might be a bit heavy, but we may want to consider a case study section to house Inferno uses in userland. Would you be willing to contribute a short write-up on how Inferno helped with the project?
For anyone else not interested in creating an actual example, a write-up + demo we can host on our site to pair along with the copy would be pretty neat.
@ddibiase I can do whatever is better for the project, but I didn't get what you wanted me to do, I guess.
I can do a write-up on the performance of the maps under Inferno, if that's the case...
Hey, author of pigeon-maps here :).
@ddibiase I think pigeon-maps would be an interesting performance case study. Comparing the react version and inferno version that @degroote22 helped build, you can clearly see how much faster Inferno is.
The react version (with a 5x slowdown) in Chrome Timeline:

The inferno version (with the same 5x slowdown):

Both frameworks manage to reach 60FPS on my MBP, but looking at the timeline, Inferno does it with much less effort. That's a big thing for slower computers, mobile devices, etc.
And just for reference, here's the issue where we worked on Inferno support. Perhaps the approach detailed there can be of use to other library authors interested in supporting Inferno with minimal changes to the library.
Most helpful comment
A React compatibility
How about using something like react-toolbox with inferno compat?