I'm only making a 'big' deal about this because I have given this serious thought.
This is the third part in a series of articles where I was trying to understand why my intuition was telling me that there was something not quite right about angular.
I finally managed to track it down to this specific little thing, and how the unintended consequences of a feature like this could have far ranging consequences to it as a viable platform.
My reasoning was not about how crazy this is now (which it is), but how this could end up 5-10 years from now if it doesn't get removed now.
Most platforms, at least major ones, ARE relevant for many years. Of course we have yet to see if Angular will be one of them, but it's looking like it will.
Comments
I'm only making a 'big' deal about this because I have given this serious thought.
This is the third part in a series of articles where I was trying to understand why my intuition was telling me that there was something not quite right about angular.
I finally managed to track it down to this specific little thing, and how the unintended consequences of a feature like this could have far ranging consequences to it as a viable platform.
My reasoning was not about how crazy this is now (which it is), but how this could end up 5-10 years from now if it doesn't get removed now.
Why would you expect Angular or any current platform to be relevant in 5 years?
Most platforms, at least major ones, ARE relevant for many years. Of course we have yet to see if Angular will be one of them, but it's looking like it will.