Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
It's funny.  Laugh. Cloud Google Social Networks Software The Internet Technology

Google Keep End-of-Life Date Forecasted 164

An anonymous reader writes "A smart aleck journalist for UK's Guardian newspaper has turned the tables on Google by compiling data on 39 of the company's terminated projects, summarized in a table and bar graph. The mean lifespan of the doomed products turns out to be almost exactly 4 years, which led Mr. Arthur to conclude that your data would be safe with Google Keep — until March 2017, give or take a few months. Of course, this assumes that Keep is destined to be one of those products and services that wouldn't be Kept, or rather 'didn't gain traction with users' in the familiar lingo of Google marketing."
This discussion has been archived. No new comments can be posted.

Google Keep End-of-Life Date Forecasted

Comments Filter:
  • by i_ate_god ( 899684 ) on Friday March 22, 2013 @04:02PM (#43250721)

    Yeah, I miss things like Code Search.

    Well that's the only thing I used really.

    But like, no one had to pay for these services. There was no contractual obligation in play. What responsibility does Google have to spend time and money on infrastructure on products that are used by the minority of people?

    • They don't have to. People are just pointing out that Google has a pattern of introducing services as trial balloons, and then discontinuing them a few years later if it doesn't fit into their overalls strategy. If you understand that and are okay with it, no problem. If you'd rather not have to scramble to find a replacement in a few years in the (not that unlikely) circumstance where the service is shut down, however, you might want to look elsewhere.

      • by jockm ( 233372 ) on Friday March 22, 2013 @04:15PM (#43250923) Homepage

        People are just pointing out that Google has a pattern of introducing services as trial balloons, and then discontinuing them a few years later if it doesn't fit into their overalls strategy.

        There is another term for that: Let a thousand flowers bloom. This is what Google has always done, try things. The things that work, that have an audience that can justify continued operation then they live. The ones that don't fail.

        This is no different than how most companies work. The backlash against Readers closure is silly. Products fail, companies pivot, they aren't required to keep things going in perpetuity.

        And Google lets you get your data out, which so many other failed products don't.

        • So, your argument is that software is a popularity contest?

          Very perceptive. Market share is just popularity. And the unpopular eventually lose, every time.

          So the object lesson is: if you depend of a software product, make sure you depend on a popular software product. Otherwise, expect to be inconvenienced (or worse) sooner rather than later.

          Potential object lesson 2: don't depend on any one else's software product. That's the point of the Free Software movement. But that requires a degree of technical comp

          • by jockm ( 233372 ) on Friday March 22, 2013 @05:04PM (#43251565) Homepage

            No my argument is that nothing is really ever assured. Anything and anyone can fail. Asteroids hit the earth, fires burn down houses, hard drives die, commercial software can fail to find a market, etc etc etc.

            The world of software is littered with the corpses of dead companies and products. It has always been thus. Even free software can end up orphaned and so unmaintained it won't work on modern systems. It is foolish to believe any product will exist forever.

            In the same way you should have a good 3, 2, 1 Backup strategy [dpbestflow.org] for your data, you should have a plan for what to do if products you rely on stop working.

            I really don't get your point...

          • Well, for free, ad-supported service? Yes. More users means more eyes for their ads
            • by spiralx ( 97066 )

              Which is fine up until the point where you want to change some part of your system that service relies on - another service's API, your underlying data storage technology, or just migrating from old server equipment. Now there's a whole load of costs incurred in just keeping the service exactly the same, which I doubt the low number of users and ad impressions sold are going to compensate for.

          • by hairyfish ( 1653411 ) on Friday March 22, 2013 @10:41PM (#43254241)

            So the object lesson is: if you depend of a software product, make sure you depend on a popular software product. Otherwise, expect to be inconvenienced (or worse) sooner rather than later.

            Which is precisely why people stick with MS. Regardless of what you think of their engineering or business practices, there is a certain amount of security in using the products that everyone else is using.

            • Which is precisely why people stick with MS. Regardless of what you think of their engineering or business practices, there is a certain amount of security in using the products that everyone else is using.

              With a few exceptions [wikipedia.org].

              • Well, at least those applications aren't cloud services, so even with no support from Microsoft you can still install and use those applications. Sadly, it appears that won't be the case with some of Microsoft's current products.

        • The backlash against Readers closure is silly.

          That may be true (I was never a user), but that does not negate the bad PR they are getting from geeks telling normal people about not trusting Google anymore.

          • by jockm ( 233372 )

            Yeah I am not sure how true that is. If you can show some quantifiable effect, please do. Otherwise I suspect the so called Normal People will just continue to act as they otherwise would. I think we overestimate our influence on them.

            • by Grizzley9 ( 1407005 ) on Friday March 22, 2013 @06:09PM (#43252237)

              Yeah I am not sure how true that is. If you can show some quantifiable effect, please do. Otherwise I suspect the so called Normal People will just continue to act as they otherwise would. I think we overestimate our influence on them.

              Does it affect common users? Yes as I and others that usually vouch for Google are now cautious. They really should have held off longer between the two announcements and added more features to Keep. I won't be using it and will likely be wary of new services and will look to have alternatives lined out to switch current ones. Basically, I'm not as loyal to Google anymore, and that hurts them in the long run as I'm not alone.

              • by jockm ( 233372 )

                That is a logical argument, not an example of quantified evidence. Show me some evidence that regular users — who either never used Reader or stopped using it some time ago — are more concerned if Google will kill products or services or not; then we can talk.

                But I am not interested in arguing about theoretical measurements of angel's tap shoes...

      • by Belial6 ( 794905 )
        Most people won't have to worry about it. If they did, the services wouldn't have been shut down and they wouldn't have to worry about it.
        • by Trepidity ( 597 )

          That particular claim depends on how Google-service users are distributed. It's true that any one service shutdown affects a minority of overall Google users, since they tend to shut down the less popular ones. But what proportion of Google users do 20 service shutdowns affect? It depends on the distribution of users. It could be a small minority, basically the same early adopters who keep signing up for every doomed service. But it could affect a considerably larger number of users in aggregate, if the cor

      • If you'd rather not have to scramble to find a replacement

        Scramble? Really?
        Please enlighten us which free Google service essential to your life disappeared overnight and how you had to put everything aside for a week to find said replacement and prevent terrible hardships.

        • by Myopic ( 18616 ) *

          Is that what scramble means to you? That isn't what it means to me. I just looked it up in my dictionary and the dictionary has pretty much the definition that I have. To scramble is to hurriedly and haphazardly overcome an obstacle. The obstacle doesn't have to be a 'terrible hardship', in fact to me the word implies a not-so-terrible hardship. Without looking it up in a dictionary, how would you define "scramble"?

          • Is that what scramble means to you? That isn't what it means to me. I just looked it up in my dictionary and the dictionary has pretty much the definition that I have. To scramble is to hurriedly and haphazardly overcome an obstacle. The obstacle doesn't have to be a 'terrible hardship', in fact to me the word implies a not-so-terrible hardship. Without looking it up in a dictionary, how would you define "scramble"?

            Scrambling (in the only definition that reasonably applies to the GP post) implies is that it is absolutely necessary to hurry. Technically, you are correct and one could scramble for no apparent reason, but well, that is just stupid. Even more so when talking about finding a replacement for a free online service.

            Logically, there should be some reason to hurry in finding the replacement. I will admit that 'terrible hardships' was a bit over the top.
            Not as much as 'scramble', though.

            • by Myopic ( 18616 ) *

              Yes, scrambling to me implies some kind of hurry. For instance, hurry up because you only have a few months to find a replacement. That's hurrying but I don't agree with the rest of what you said:

              * essential to your life
              * disappeared overnight
              * put everything aside
              * terrible hardships.

              It's okay I just think you overreacted a little bit. I think 'scramble' was an appropriate word to use.

              • You're kidding me, right?
                In what world is 'a few months' an exceptionally short period to find a replacement for, say, an online email service?

                No, I did not overreact. The person who used the word 'scramble' overreacted. And in a way that is frankly insulting to people who've ever actually had to scramble to do something. As I said: scrambling not only implies hurrying, but doing so in a haphazard/frantic way because there is extreme urgency. It is not a synonym of hurrying.

                "Oh noes, Google Reader went away

      • People are just pointing out that Google has a pattern of introducing services as trial balloons, and then discontinuing them a few years later if it doesn't fit into their overalls strategy.

        Google has a strategy?

    • by rokstar ( 865523 ) on Friday March 22, 2013 @04:09PM (#43250819)
      Conversely there is no obligation to use their services either, which I think is the larger point. Their "responsibility" is to not pissing off a sufficiently large portion of their user base such that they have no interest in trying their new products.
      • by AmiMoJo ( 196126 ) *

        You are not obligated but they certainly want you use their service, so it is fair to moan about it.

    • by cultiv8 ( 1660093 ) on Friday March 22, 2013 @04:10PM (#43250837) Homepage

      What responsibility does Google have to spend time and money on infrastructure on products that are used by the minority of people?

      It would be nice if they open-sourced these projects and then let the "minority of people" who actually use it maintain it themselves.

      • by Reapman ( 740286 )
      • by Ksevio ( 865461 )
        But a lot of them aren't particularly innovative code wise - they're just convenient because Google hosts them. Google Wave had some interesting stuff in it, so they released that, but there are plenty of RSS aggregators out there and it's easy to code a new one.
      • by jopsen ( 885607 )

        What responsibility does Google have to spend time and money on infrastructure on products that are used by the minority of people?

        It would be nice if they open-sourced these projects and then let the "minority of people" who actually use it maintain it themselves.

        True, on the other hand some of these projects can't... Because they are based on complicated infrastructure... Google Code search for example...
        Anyways, we have seen Google open source etherpad, when they closed that service...

        I also hate it when a service I use is closed (Google Reader for example), but at the end of the I respect Google for innovating and trying out different things, and that includes admitting that something was only a partial success, or not a success at all..

      • Or maybe charge people for these services?
      • by c ( 8461 )

        It would be nice if they open-sourced these projects and then let the "minority of people" who actually use it maintain it themselves.

        Easier said than done. A lot of the value isn't in the software as much as the service.

        Google Reader being a good example. A web-based RSS reader as well as mobile versions... The web-based interface is decent, but quite frankly the Android version is weak, not to mention buggy. The main advantage to both as RSS interfaces is that they don't really get in your way.

        The real va

    • by mungtor ( 306258 )

      What responsibility does Google have to spend time and money on infrastructure on products that are used by the minority of people?

      Google's time and money is what it probably comes down to. Somewhere deep in the accounting department they figure out that the quality of data they are mining is not enough to offset the actual cost of running the service. It's true that a larger user base would create a larger data set and therefore be more likely to be profitable for them, but if it's just a different representation of the same data there really isn't any point. They can figure out what we're interested in from Search, what we actua

    • by SirGarlon ( 845873 ) on Friday March 22, 2013 @04:21PM (#43251007)

      But like, no one had to pay for these services.

      It's not about licensing cost, it's about migration cost.

    • by sribe ( 304414 )

      What responsibility does Google have to spend time and money on infrastructure on products that are used by the minority of people?

      None whatsoever. Entering into such a deal, where the other party obviously has no obligation to you, is a bad idea--and that's largely the point here, even if obscured by the clever attempts at humor ;-)

    • by grahamtriggs ( 572707 ) on Friday March 22, 2013 @04:25PM (#43251063)

      Oh, I get the point that we are not entitled to use these products, because we aren't paying for them.

      But there are two points, really:

      1) Anger is a way of expressing that people do actually care about the services. If they shut them down with nobody saying anything, then they are right. Conversely, if lots of people kick up a fuss, maybe they see that they are wrong (in thinking that people don't use it).

      2) And this one is particularly pertinent to things like Google Sync/Exchange ActiveSync. Just because users aren't paying for the services, doesn't mean that they wouldn't. If I had the option to simply upgrade my Google Mail to a paid apps account / simply pay to retain the features that they are cutting from the free account, then maybe I would. I would *certainly* pay for a "Google Apps for Home", which kept Google Reader, EAS (upgraded to work with Outlook 2013), etc.

      But they don't offer that option. That I don't pay for these services, isn't my fault in not seeing the value. It is their fault in providing the option.

      • Regarding 1), Google has full access to the Reader accounts. This isn't desktop software, they know full well who and how much people use it. The "fuss" is nothing but a storm in our little bubble of technologists. There's a whole world that uses Google products and doesn't even know Reader exists.

      • Oh, I get the point that we are not entitled to use these products, because we aren't paying for them.

        Yes, we were. We paid for them with the data Google uses to sell us advertisements. Moreover their shut-down incurs definite migration costs.

        We have every right to complain.

        Of course, Google has every right to ignore us and shut down whatever they want, but the claim that we weren't paying for them so we should shut up about it is moronic.

    • by afgam28 ( 48611 ) on Friday March 22, 2013 @04:25PM (#43251065)

      There was no contractual obligation in play. What responsibility does Google have to spend time and money on infrastructure on products that are used by the minority of people?

      There's no contractual obligation for users to put on a happy face either. The fact is that it's kinda annoying when a service that you've come to rely on gets shut down.

      Google doesn't have a responsibility to provide free services to everyone but it is in their interest to build trust amongst their user base. Otherwise no one is going to invest any time into things like Google Keep.

    • by drcln ( 98574 ) on Friday March 22, 2013 @04:33PM (#43251149)

      There was no contractual obligation in play. What responsibility does Google have to spend time and money on infrastructure on products that are used by the minority of people?

      It's not hate, its disgust at the stupidity of it all. Google created these ancillary products to draw people into the Googlesphere, and it worked. As someone from Google has said "The lifetime value of a Chrome user is enormous." Google's ancillary projects drew in people and Google prospered.

      In the short term, Google can kill the products that are marginally effective in drawing in new eyeballs, but that sound you hear as they cancel projects that drew people in is the sound of people heading for the exits. That smoke is from the burning of bridges.

      Google's near sighted cancelation of today's well liked projects is erecting barriers to acceptance of its future offereings. Google's real product is people, and Google is polluting its product stream with disapointed people who are tiring of learning to use a tool only to have it taken away. Not a good long term strategy.

      I won't be using Google+, or Google Docs, or or Google Drive, or Keep, or Google's NIK software, or Chrome, and definitely not a Chromebook, since any of these can disapear or be rendered unusable on a whim.

    • by mwvdlee ( 775178 ) on Friday March 22, 2013 @04:39PM (#43251211) Homepage

      What responsibility does Google have to spend time and money on infrastructure on products that are used by the minority of people?

      None.
      What reason do people have to give personal information to a company that takes no responsibility over it's products?
      Remember; your time and information is only free if it's worthless. You ARE paying Google with something valuable, just not currency.

    • by skids ( 119237 ) on Friday March 22, 2013 @04:55PM (#43251431) Homepage

      This deserves a car analogy.

      Suppose a private individual decides to allow drivers to use some of his privately owned land to take a shortcut to avoid a swamp.

      Now suppose there are competing grits delivery companies. Delivery Companes A and B start using the shortcut, and they sell off their SUVs because they no longer have to muck through the swamp. Company C uses the shortcut, but since he cannot trust it to stay there, he holds on to the SUVs. Company C goes out of business because Companies A and B don't need to buy as much gasoline since they do not have SUVs, and they underbid company C for new contracts.

      Then the private individual decides he wants to close the shortcut to build a large statue of Natalie Portman.

      The business of grits delivery being one with tight margins, Company A and B cannot afford to buy SUVs on such short notice. Company A goes bankrupt trying to finance SUVs, and Company B just stops grits delivery to people that live on the other side of the swamp.

      Now nobody on the other side of the swamp has any grits at all. Sure they all saved a few pennies on 4AM deliveries of hot grits in the meantime, but it wasn't worth going cold turkey.

      The moral of the story is that building something useful but ephemeral, especially if the stability of that thing is unpredictable, destabilizes markets by playing on their inherent vulnerability to human greed and shortsightedness. There may be zero legal obligation to ensure the stability of the service, and your standard disclaimers in the EULA that you can end it at any time may protect you from any sort of legal action, but for a company with a "do no evil" motto, marketing, advertising, and then killing such a product tends to produce consequences far from their stated ideal.

      • LOL - nice analogy and nice callbacks to Slashdot of yore! :)

      • Then the private individual decides he wants to close the shortcut to build a large statue of Natalie Portman [followed by tale of destruction of grits delivery infrastructure, due to this decision].

        Although the motives of the private individual are impeccable in this case, this is why we have the legal concept of an easement [wikipedia.org] - to prevent terrible tragedies like this.

      • Great analogy as an example of "market failure" due in part to "unquantified risk" (and to a lesser extent de-facto monpoly by market position).

        http://en.wikipedia.org/wiki/Market_failure [wikipedia.org]
        "Market failures are often associated with information asymmetries, non-competitive markets, principal-agent problems, externalities, or public goods. The existence of a market failure is often used as a justification for government intervention in a particular market."

        From another domain, but a related example of greed and

    • Since you don't understand the anger, let me, or rather Charles Schulz, draw you a picture [wikia.com].
    • by gl4ss ( 559668 )

      people didn't even have a chance to pay for them.
      that's the gist, it seems so random from user point of view.

      people gave flack to gm for cancelling ev1 too. some people liked it, but gm didn't want to bother with it.

    • by Junta ( 36770 )

      What people *should* take away from this is that the fad of software as a service carries an extreme risk. Sure, for things highly contingent upon networking effects (e.g. mail), SaS doesn't really change the dynamic. However, for things like RSS reading, document editing, photo editing, and so on and so fourth, with all other things being equal, it's better to pick the offline capable model where you still have capability no matter what the vendor decides to do or if the vendor fails completely.

    • There was no contractual obligation in play. What responsibility does Google have to spend time and money on infrastructure on products that are used by the minority of people?

      Perhaps, but there is a key dependency problem. If you introduce a free service which people come to depend on, and if you pulling the service results in costs/damages/lives lost, there is at least a moral obligation, if not a legal obligation, to keep the service running, or at least add a fee instead of discontinuing it directly. Now, of course, Reader and Keep aren't that critical of a service, but if say Google Wallet becomes one of the de-facto methods of payment and Google decides to pull the plug

      • In your analogy there's a moral obligation because people would fucking die otherwise. To compare this with using another RSS reader (even if somehow worse) is asinine.

        If I were to run a service, I would probably feel a moral obligation to keep it running, much like I did in the past feel an obligation to keep my open source extensions up to date and available.

        But if some entitled fuck had come and whined that I had that moral obligation, I'd cut him off immediately. There's stuff that may be morally impera

        • In your analogy there's a moral obligation because people would fucking die otherwise. To compare this with using another RSS reader (even if somehow worse) is asinine.

          Can you read, Mr. Asinine? "Now, of course, Reader and Keep aren't that critical of a service" "A somewhat contrived analogy would be"

          If I were to run a service, I would probably feel a moral obligation to keep it running, much like I did in the past feel an obligation to keep my open source extensions up to date and available.

          So you agree with me

          But if some entitled fuck had come and whined that I had that moral obligation, I'd cut him off immediately.

          So you're a kid who gets angry if someone tells you you should do something. Let me tell you, in society, society expects all sorts of things from you, some reasonable, some unreasonable, and if you're going to get angry every time someone tells you you should do something, you're going to have a lot of problems.

          • "Now, of course, Reader and Keep aren't that critical of a service" "A somewhat contrived analogy would be"

            I think it's asinine when applied to Google Wallet as well, and calling it a contrived analogy is an understatement. You're free to disagree.

            If I were to run a service, I would probably feel a moral obligation to keep it running, much like I did in the past feel an obligation to keep my open source extensions up to date and available.

            So you agree with me

            No, because you're judging others, while I don't feel I have the right to do that in this case. I would feel a moral obligation to do so, but that doesn't mean I think Google (or anyone else) does.

            So you're a kid who gets angry if someone tells you you should do something.

            No, it depends on what, who said it and for what reasons. And I wouldn't really feel angry, but I would feel some schadenfreude after cutting them off.

            Let me tell you, in society, society expects all sorts of things from you, some reasonable, some unreasonable, and if you're going to get angry every time someone tells you you should do something, you're going to have a lot of problems.

            Considering I've been c

          • by Myopic ( 18616 ) *

            "if you're going to get angry every time someone tells you you should do something, you're going to have a lot of problems."

            In America we have an entire major political party dedicated to exactly that. But you're right, they do cause a lot of problems.

    • by 0ld_d0g ( 923931 )

      How is that different from the way any other company should be treated? Should people not point out that their previous such products were canned after X-months ? After all, if Google wants our data, we should be pressuring them to keep their products around for a long period of time. When no such user pressure exists, Google will just keep on launching new products that capture user data for monetizing and when they are unable to do so, they simply shut down their projects without any repercussions. (The r

    • by LihTox ( 754597 )

      First, Google isn't making any money from Reader but it must have been getting something out of it or else they never would have put it online in the first place. Part of what they're getting is goodwill, so that people will further equate "Google" with "useful product". Now that they're closing Reader, they lose that goodwill. And if we the users make a big enough stink about it, if we make it very expensive for them to shut down Reader, than next time they will have to factor that into their calculatio

  • by Burz ( 138833 ) on Friday March 22, 2013 @04:12PM (#43250883) Homepage Journal

    ....a set of mainframe services. Re-brand it as 'cloud' all you want-- Over the long term, its not the best fit.

    Its better to have locally-running apps that give you a choice of data storage points (especially local and private VPN).

  • The mean lifespan of the doomed products turns out to be almost exactly 4 years

    And that's just it: The MEAN.

    If you look at the graph, there is a slight flat spot there, but really, over all, it's a pretty constent slope all the way up.

    Seriously, nothing to see here.

  • downside of SaaS (Score:5, Interesting)

    by crgrace ( 220738 ) on Friday March 22, 2013 @04:17PM (#43250951)

    This really is a big negative of Software as a Service. When you own something, you can run it forever, even if the developer decides to stop using it.

    I have some simulation software for electrical design that was last updated in 1998. Still works fine and gets the job done. If it were on the cloud I'd be out of luck and forced to continually move my data between paid services. Too bad.

    • Exactly, look how many companies still run some DOS program in a CMD box on Windows. They're doing so because it's more worth it to them than to develop some new solution. The solution they already had still works. If it were cloud-based then they'd be stuck paying bills that they really don't need to. The cloud is always going to fuck over the people who depend on it.
    • When you own something, you can run it forever, even if the developer decides to stop using it.

      In theory, yes you can keep using unsupported software. The reality is that most companies would ultimately be better off if they were forced to drop it sooner rather than later. It hurts to rip off that bandaid, but it's usually worth it.

      • Corporations tend to be very conservative about making changes to critical infrastructure, on the theory of "don't fix it if it ain't broke." They don't like unscheduled forced expenditures and down time. I can personally think of at least a dozen DOS and Windows 98 machines that are in service today. This may come as a shock, but there are actually computers out there which aren't on the internet, so security vulnerabilities and upgrades aren't an issue. And the last thing a company that has something
  • Why?

    In all seriousness, despite the weakness of the statistics (33 points does not make a universe, particularly with such widely scattered data), this is simply a codification of the reluctance many feel about trusting vital data to Google. It's interesting to note how many projects Google has shuttered, and the lengths of time they were live. I do appreciate the fact that the author has provided his raw data so that we can draw our own conclusions.

  • Keep uses Google Drive, so your data isn't going anywhere.
    • by gl4ss ( 559668 )

      well technically drive would be shut down a while before it, on average.

      I predict a re-branding of it within 5 years anyways.

  • use it. The more people who do, the better its chances.
  • The started having a banner that iGoogle was going to be turned on in November of 2013 in mid 2011. There is no reason to think they would shut down something like Google Keep without at least that much warning.
  • by interval1066 ( 668936 ) on Friday March 22, 2013 @05:06PM (#43251599) Journal
    I wonder why google trends [google.com] isn't predicting the end of these various Google services?
  • Struck a Nerve (Score:5, Insightful)

    by Grizzley9 ( 1407005 ) on Friday March 22, 2013 @05:21PM (#43251753)
    Google seems to have reached the tipping point when they cancelled Reader. Now, their main base of loyal geeks are starting to question them, in print no less. This is not a good sign for Google. They are taking a much larger PR hit than just losing some respect from a few Reader users. Granted many of those services likely did need to be cut, or not even started, but it seems they've now pushed enough to where geeks are starting to push back and relaying that mistrust to their non-geek friends.
    • by snadrus ( 930168 )

      Breaking-down the obvious:
      - Laymen could get Reader's benefit
      - Geeks saw a product that only told Google that some RSS source interested them.
      - Those geeks like Google's open-source policy & assumed to unprofitable would become open-sourced.
      - Reader wasn't open-source, tarnishing this image.
      - A simple open-source promise could save them a lot of hassle.

      Unless perhaps Google wants to give free cloud services a black-eye?
      It certainly made me consider installing my own jsPerf instance.

  • by Mr. White ( 22990 ) on Friday March 22, 2013 @05:24PM (#43251777) Homepage Journal

    Google+ launched on June 28, 2011.

    They will stop trying to shove it down our throats on estimated June 28, 2015.

    We are half way there.

  • The graph clearly shows that there is no correlation to 4 years. it shows a wide, fairly even, range. Where a few months is as likely as 10 years.

    4 years is the average, nothing more.

  • by xs650 ( 741277 ) on Friday March 22, 2013 @08:10PM (#43253393)

    Google is doing us a service by reminding us that online services, data storage, etc come and go. Don't rely on any one company if a service or your data is important to you.

    Reality bites and it's good to have an occasional nip like this latest one from Google to remind us of that.

  • He's not being a "smart aleck" ... ... he's doing analytics.

I have hardly ever known a mathematician who was capable of reasoning. -- Plato

Working...