View Single Post
Old 03-21-2013, 07:17 AM   #50
GlenBarrington
Cheese Whiz
GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.GlenBarrington ought to be getting tired of karma fortunes by now.
 
GlenBarrington's Avatar
 
Posts: 1,986
Karma: 11677147
Join Date: Jan 2010
Location: Springfield, Illinois
Device: Kindle PW, Samsung Tab A 10.1(2019), Pixel 6a.
Quote:
Originally Posted by VydorScope View Post
The problem with Google products, and keep in mind I have an Android Tablet and use many of them, is that you never know when they are going to randomly cancle them. See Google Reader this week for example.
I don't think it's random, if you look at that which is getting cancelled (and those that seem in some sort of decline, like Picasa) all of them are those that lie outside the business model Google is pursuing.

Regardless of their popularity, all of them are discrete projects that receive no benefit from the common code and infrastructure Google is building. All take a separate effort to maintain.

My years in IT tells me that ongoing maintenance is THE major expense in a software product that can prevent it from ever being profitable. You have to keep people on who understand the code, the reason's why this 'thing' was done 'this' way and not some 'other' way. And no one is ever good enough to get all that stuff down in documentation, and few are good enough to completely absorb the documentation provided.

When you have a coherent and cohesive planned set of software sharing a common core of code, ongoing maintenance is much less costly and more effective since maintenance on one software title automatically provides that maintenance to all SW titles. And you avoid those numerous little pockets of highly paid technical expertise that are never fully utilized.
GlenBarrington is offline   Reply With Quote