Tankenstein

Because using tables or table properties when you're not dealing with actual data tables is bad practice. This was phased out a while ago.

Been using eslint for a while now, it truly is great. Using it with the airbnb javascript conf for react development often catches stupid style mistakes and helps my team keep in the same style.

Cool! i've been wanting to see a good simple getting-started with relay for a while now. I feel like this is a bit overkill for most of my projects, but i might use it someday. I like the idea that you just declare what your component's data dependencies are, and let relay sort most of that out.

"I use Redux, where all the state tickles down through the props" Isn't that just flux, or even just good React practice?

No, in actually good shape. Lift 3 times a week, have a 6-pack.

4% body fat is fatal really fast, isn't it?

I had a chuckle.

I'm sorry, but please, please, PLEASE, do not hijack scrolling. There is no reason for it, it's distracting, often fucks up mobiles. I mean no disrespect, just don't do it. Cool product!

I'm not really an Ember dude, but i might have some input on 3. In react, when you start, it looks the same way. A bunch of functions passed down like 5 components. Fortunately, there's a way better way, and it's flux. I'm guessing Ember will let you use something like flux.

Just pure react is great for tiny things, but for large applications you should use React with Flux architecture with alt or flummox or reflux or whatever you like, it simplifies things in the long run.

Of course you would need to do things like ajax or routing, for which there are endless libraries, or you can just go pure XHR. React-Router is terrific for routing.

Yup, i really like how the js community doesn't hate on other frameworks/libraries, but instead they use each other's ideas to better their own.

Every JS framework is moving in the direction of React, because React is (in my experience) the best and most logical we have right now.

Read the spec, it's basically storing the vote in a completely encrypted state. Once counting starts, the personal information is destroyed (literally, i know the guy, he takes the hard drives and bashes them until they are completely powder pretty much), and the votes are unencrypted. Once you start counting, there is no way to know whose vote is who. (It's actually much more difficult, but it's based on mail voting. I'm a bad source on this, read the spec. Everything is open-source.)

This is not a new thing.

This is great! definitely going to use this in the future.

Excellent! Just as a tip, when writing curses it's best to run everything in a curses wrapper, so wrap your main function in curses.wrapper(main) basically. If you don't do so, crashing messes up the terminal.

This is really cool! Nicely done and easy to use, also i'm real happy that it handles ES6. Might just use this in the future.

This is pretty cool! It's going to get even more interesting once ES6 features are implemented :). However, i feel like javascript by itself is such a great language (has some weird parts but eh) that i would never use this. Cool project though!

I am also interested in this. I'm reading a lot about it, and goroutines look fantastic.

Have been using this in production for about 4 months now, still has a lot of quirks to iron out, but nothing you can't solve pretty fast. It's noticeably (and obviously) less mature than bootstrap, but it's definitely worth a shot. I quite recommend it.

This is terrific! Speedy javascript as well.

If anyone has any feature requests, i'd love to hear them.