> If you want to future-proof your web application, you have to make a bet on what engineers will want to use in three years. If everyone thinks like that we'l

> If you want to future-proof your web application, you have to make a bet on what engineers will want to use in three years. If everyone thinks like that we'll only see more faddish frameworks come and go. Why not make a bet on what framework will continue to provide the most productivity in three years? Or stability, maintainability, etc.? If it's a mere popularity contest then it's winner takes all and we'll all be writing javascript in the near future.