3 ms·

I think what alot of people don't think about is that "proper / correct engineering principles" don't necessarily translate to creating successful projects / co

I think what alot of people don't think about is that "proper / correct engineering principles" don't necessarily translate to creating successful projects / companies. If your goal is to nitpick about the reasons why a specific framework is not right for the job, then "mission accomplished". If your goal is to create amazing products / services. And are willing to do anything to accomplish that, then sadly I think you're on the wrong side of the argument.

fixermark 12y ago
Essentially this. Angular may be monolithic and less flexible, but if a young company gets to prototype faster with it and as a result survives to second- and third- funding rounds, they can afford the engineering hours to re-implement their UI from scratch. Success (and its associated revenue) solves all engineering problems in the long run.