No. Just no.
To every React developer out there: don't do this.
Don't mix content and presentation like this. We have a better tool, it's called CSS. Use it, embrace it.
This is not responsive, it's not semantic, it's hard to maintain, it's less flexible (ironic, isn't it?), it's another dependency and another layer that has to be learnt on top of all the rest. It tries to "save" you from using flexbox in CSS but it doesn't save you from actually *knowing* flexbox OR writing CSS anyway. So just use flexbox, I say!
There is no flexbox "done the React way", unless you're referring to styling your components with flexbox. This is another example of something done while asking yourself if you *could* do it but not asking if you *should* do it.
Nope, sorry, no way I'll ever use it and if I catch one of my colleagues using it I'll bite their pinky fingers.
Sorry if this appears too harsh but I really feel this is a step in the wrong direction, and I invite you to reconsider how you design your components (in React but not only).
I didn't mean an estimation for replacing a Java backend, but rather how much time will pass until Node will be considered a common and valid alternative to Java for building the business logic of an application.
I think "guy" is quite neutral, and also "dude", and *also* "man" in neutral contexts (i.e., not opposed to "woman"), but still this isn't about JavaScript.
How long until Node can actually and effectively replace a Java backend, though? And all of its business logic?
Talking about a complete JavaScript full stack, even in the business area.
[spam]
But I'd like to note:
> Compatible with the most important browsers available in the market: IE 5.5+, Firefox 1.0+, Mozilla 1.3+, Netscape 7+, Chrome.
Netscape is really the selling point for me. Yeah.