At this point, my main concern is performance and UX, pretty much above anything else. Whether HTML in JS or JS in HTML is the best way to go, it's secondary. It doesn't matter if the final product is sluggish, something we usually only discover too late in the process. I'm not crazy about React's development style, but I do like the responsiveness of anything developed with it. It's arguably the fastest among the mainstream JS frameworks. IMO it doesn't matter if Angular is using Typescript or COBOL in their HTML; if the final product is heavy and slow, it's not worth using it. I hope in v2 they have seriously addressed this issue.
That's not what I've said. I'm interested in performance, and while I'm all for micro-libraries, I'm careful before choosing any framework that will completely change the way I write html because this has larger implications. Will I find answers to my framework specific questions? Will I find UI plugins ready to use with this framework? Is it battle tested enough in large projects that I have confidence I won't run into major bugs in production? All these things matter too, and even if Mithril is faster than React, it won't have the same level of community support that the mainstream frameworks do.
I don't even use React in my job, we use server side mvc with pjax/jquery. These are just the kinds of things I'd consider if I have a case to use a client side mvc, such as a highly dynamic UI (e.g. Trello).
12
u/felipeccastro Jan 05 '16
At this point, my main concern is performance and UX, pretty much above anything else. Whether HTML in JS or JS in HTML is the best way to go, it's secondary. It doesn't matter if the final product is sluggish, something we usually only discover too late in the process. I'm not crazy about React's development style, but I do like the responsiveness of anything developed with it. It's arguably the fastest among the mainstream JS frameworks. IMO it doesn't matter if Angular is using Typescript or COBOL in their HTML; if the final product is heavy and slow, it's not worth using it. I hope in v2 they have seriously addressed this issue.