3 ms·
If it were a google product, I wouldn’t trust it for a second. It seems that very few consumer facing products from Google are safe from being cut these days.
by village-idiot 8y ago
If it were a google product, I wouldn’t trust it for a second. It seems that very few consumer facing products from Google are safe from being cut these days.
If google is using it internally, the risks change. After the Angular 2.0 debacle I’d fear Google Just up and changing everything and not providing a smooth migration pathway because they can. They probably won’t cut it, but that doesn’t mean that they won’t inadvertently hurt you really badly
- riku_iki 8y agoAngular 2 is just very different product, smooth migration (reliable auto translating sources from js to ts?) would require a lot of effort..
- village-idiot 8y agoFrom a marketing perspective, that was an awful choice. Releasing an effectively unrelated product and calling it 2.0 is just asking for trouble. Second, they immediately announced no migration path and no more bug fixes at the same time. I’m not sure if they stuck with that, I was in the backbone camp at that time, but that is a painful pill to swallow. That they made that call without considering the downstream pain is a sign to me that I should be wary about depending on them
- riku_iki 8y ago> and no more bug fixes Angular 2 was released in Sep 2016. AngularJS continued releases up until Jul 2018, with 3 years of security fixes after that. 5 years is plenty of time to rewrite your app.
- village-idiot 8y agoEither they backed down, or my memory is faulty. I recall at the time the announcement was that they were doing a hard cutover support wise. But since I wasn’t developing in Angular it was more of an interesting thing and not an immediate concern. You’re right, 5 years is plenty of time.
- deleted 8y ago[deleted]