News for hackers. Stuff that matters.
Re:How did Google Talk change from a dream to a nightmare? by harryf on Sunday February 11, 2018 @06:02AM (#16352171)
It may be a byproduct of how Google incentivizes their engineers.

As I've heard from chatting with engineers and PMs at Google, the biggest rewards go to those that take a product to its first major release and the initial marketing fanfare.

After hitting 1.0 you typically see teams break up, the star engineers moving on to the next big thing. Once that happens the pace of the products development slows significantly, leading to ignored user feedback and a struggle make improvements.

The product mothballs for some years until - in the case of something like Google Talk - momentum is generated around replacing it with the next 1.0 product.

And so on...

Re:How did Google Talk change from a dream to a nightmare? by username223 on Sunday February 11, 2018 @09:27AM (#16352800)
Writing really good software takes years of user feedback, and a team of knowledgeable engineers digesting that feedback to write new versions. A company can afford to do that when its users are its customers. When they are its product instead, you get a steady stream of half-baked and quickly-abandoned software, often installed via forced update.
Re:How did Google Talk change from a dream to a nightmare? by hedora on Sunday February 11, 2018 @05:00PM (#16355075)
Most of the industry has settled on the CADT model instead. The GP of this post suggests Google has done a particularly good job formalizing it these days.

https://www.jwz.org/doc/cadt.html

Re:How did Google Talk change from a dream to a nightmare? by harryf on Tuesday February 13, 2018 @09:55AM (#16367524)
Did you try that link when HN is the referrer? ;)
Re:How did Google Talk change from a dream to a nightmare? by erik_seaberg on Sunday February 11, 2018 @06:19PM (#16355397)
In theory the goal is "launch and iterate", but yeah, the incentives add up to "launch and leave".