Maybe people are finally learning that investing into Google offerings is a risky long term proposition. The company has a long history of abandoning projects, and they simply treat the broader developer community as free beta testers.
That's a false dichotomy. Many companies do a much better job either maintaining projects or having a proper transition to the community when they're not interested in them. Google is has one of the worst track records in this regard.
I don't really see it this way for libraries. Guice and GWT come to mind, which have been around forever and still actively maintained (GWT arguably less so than Guice).
Besides, it's open source. If it gets abandoned while still being useful, it will be picked up by someone else. We saw that with Dagger bouncing from Google to Square and then back to Google.
What popular libraries do you have in mind that Google abruptly stopped supporting and which caused problems to developers?
I think people are confusing libraries with products. Google loves to abandon products. Development libraries, on the other hand, are actually mantained pretty well.
But anyway, I think the best way to "predict" if a company is going to drop a development library is to check if they're using them in a widely used product. Protocol buffers, Google Test, Guava, Guice, Angle, etc. are good examples. Now Angular I don't know what product from them use it.
By the way:
Besides, it's open source. If it gets abandoned while still being useful, it will be picked up by someone else. We saw that with Dagger bouncing from Google to Square and then back to Google.
But it still big blow to the project, and depending on the circumstances it could mean its dead. I mean, just look at Wave...
No, open source will not just be picked up. Look at so many Apache projects. They are useful, but nobody has the resources to gain enough knowledge about all that code to be able to maintain it. Then nobody has time or resources to really maintain it.
They do have a better track record for libraries, but again generally for the ones they're using themselves. It could be that product lifecycle tends to be shorter and so it's more obvious.
It's not trivial to hand over a non-trivial open source product. This was precisely my point regarding a proper transition. The current maintainer has to engage the community and help volunteers become comfortable with the product.
I would argue Angular 1 is a perfect example of Google using the broader community as beta testers. The only reason it got popular was because Google was behind it. People immediately assume that Google has lots of smart people working there so they know what they're doing. If it's complex or does questionable things like two-way data binding, there must be a good reason.
The reality is Google is just fumbling with it and by getting lots of people to try their idea they realized that there was a lot wrong with it. So, then they deprecated it and moved on to make a new thing. All the people who bought into it are left with a slow and deprecated mess Google abandoned.
The only reason it got popular was because Google was behind it.
That's a simplistic view. The main reason why it succeeded was that it was useful and solved a real problem. The fact that Google was behind it was icing on the cake, plenty of libraries get popular that are written by a single developer on their free time.
Who's behind a library is a lot less important than how useful it is.
3
u/Eirenarch Dec 15 '15
So why isn't Angular 2 creating new hype for Angular?