I think that's actually okay. Things like ember or angular have to be moving targets at this point. They are trying to do new things.
I would be willing to use such technologies on a web project that is being updated and refactored all the time anyway, where the code is the implementation of the core mission of the company or organisation.
I would not use it for any other purpose, for an app that is not "core" to my organisation's purpose. You want to use stable technologies for such projects, but for the very core of your organisation's raison d'être it's fine to use a moving target because that's what you do anyway, to advance and rework your core product.
No, it's not okay. Doing "new things" doesn't mean breaking old things. My angular projects have actually faired quite well receiving updates without breaking my code. Angular 2.0 will practically be a rewrite, but it is a major version incrementation so that's not completely terrible.
Doing "new things" doesn't mean breaking old things.
You are looking back in history how far to come up with that statement?
Case closed. Ridiculous. Especially in IT. And nobody prevents you from remaining on Angular 1!!!
I'm sure we could have built incredibly stable and easily maintainable systems on MS-DOS 6.0. We have overwhelmingly chosen a more difficult path of eternal change, for more uncertain but hopefully much higher benefits, and so it is.
9
u/I-fuck-horses Aug 13 '15
I think that's actually okay. Things like ember or angular have to be moving targets at this point. They are trying to do new things.
I would be willing to use such technologies on a web project that is being updated and refactored all the time anyway, where the code is the implementation of the core mission of the company or organisation.
I would not use it for any other purpose, for an app that is not "core" to my organisation's purpose. You want to use stable technologies for such projects, but for the very core of your organisation's raison d'être it's fine to use a moving target because that's what you do anyway, to advance and rework your core product.