It's pretty incomplete for parts of the world, and certain applications require accuracy (or at least completeness). The answer, of course, is to contribute, but when your core business isn't mapping that's hard to propose as a viable fix.
Parts of the world in my case ~= Sydney, which has a decent number of geeks per capita to contribute. OSM is wonderful, but has a way to go before it's a viable solution for everyone.
Second that. Google maps are surprisingly bad in a number of first-world countries like France or Israel; OpenStreetMap are very very detailed. I don't think Bing maps would be better than either of those.
Adding the missing features (email + maps) to owncloud would appear to be the neatest way to go. Then target something like the openstack API and you can move between providers pretty easily. The bit that bugs me is how to deal with rolling your own maps provider, but if you're willing to compromise on having access to all maps all the time it wouldn't be so hard.
"It's because I think that Google is now working against the potential of the open web" That's a pretty bold claim and an epic overreaction, especially given that Google currently derives 97% of its revenue from the Web, and if it goes away, it would be very problematic for Google.
The Web is a small subset of the Internet. There are many other protocols to enable the sharing of data between individuals and platforms, and it looks like Google wishes to deprecate at least some of those in favour of its own end-to-end solution. I think that killing off Reader in favour of G+ is the start of acceleration in that direction. I hope I'm wrong.
First of all, the quote, from you, specifically says "open Web" not "open Internet"
Secondly, Reader was not killed because of G+. If FriendFeed is finally killed off, will you say it was because Facebook needed the resources and engineers on a competing product? Consumers have moved on to desire the kinds of features that are inherent in services like Facebook, and RSS simply isn't suited to solving the problem of federated social networking. There is no open standard for this, remember, Google tried it with PubHubSubHub/WebFinger/OpenID/OAuth/ActivityStreams but it didn't work.
I favor federated feeds as well (see my essay http://timepedia.blogspot.com/2008/05/decentralizing-web.htm...), but honestly, for me personally, RSS was a HUGE step back from what I had on USENET in the 80s with RN/TRN. Someone must create a new, open federated social networking platform, but honestly, you can't put the cart before the horse. Google tried that several times and failed.
First, you've got to built a super successful platform consumers love, then you can standardize it. The history of doing it the other way is littered with failure. Remember OpenSocial?
I don't think Google has lost sight of the Open Web, I think it just realized that you must focus on the end user design issues first if you want to be successful. Ignore this at your peril, look at the way consumers flock to native apps on mobile. They care about experiences, not implementation. If the "open web" specs don't do the job, then you need to create a product first that consumers show they want, and then work backwards to figure out how to fix the specs.
You're also correct that RSS doesn't solve the problem of federated social networking. It was never intended to.
W.r.t. developing protocols for federated social networking: Google isn't interested; it would harm their bottom line if users on their systems could easily share content outside those systems. Hence why Google+ doesn't even offer an RSS feed.
Do you really, hand-on-heart, think that Google would support a federated social media protocol on Google+ should such a thing come into being? Do you think they're planning to build such a protocol?
A central core feature of Google Wave was federation. Wave failed. Reason? Not because of federation, but because of consumer experience and confusion.
If you look at G+, Google has taken a very very careful approach this time (after OpenSocial, Buzz, Wave, et al failed), building on it very incrementally, always concentrating on user experience at each step. Even to the extent that they don't have even have an API to post content to G+ programmatically. Whether or not it will eventually turn into some idea federated open network, I have no idea.
But I would not take G+ as somehow Google dropping support for the open web. Google is a very large company with lots and lots of product, and company culture just doesn't change overnight.
I'd love it if Google had done a disapora-like federated system. But honestly, if they had gone that route, we'd have threads all over the blog-sphere laughing at Google for yet another social networking failure.
Those kinds of projects earn the love and adoration of the hacker community, but they don't get grandma, teens, and celebrities on your site.
Want better counter-evidence? Look at WebRTC and Google Hangouts. Hangouts are a defining competitive advantage G+ has over all over social networks, and Google sponsors a spec that essentially makes them a commodity that anyone can implement now.
Hmmmm ... the fact that there is no API access, no RSS feed etc. doesn't strike me as a coincidence, or perhaps a consequence of a streamlined user experience. I think it's deliberate, & part of a long-term strategy.
Clearly you don't though.
Perhaps we should resume this conversation in five years time? :)
I still think this is all ridiculous. Stopping support for a product that uses a certain standard doesn't mean you're against that standard, unless you're a conspiracy theorist.
You can argue that they're against certain open standards if you want, but the canceling of Reader isn't actually evidence of that. Simultaneously putting effort into G+ is also not evidence of that. It's not even symbolic of that. It is only evidence of shifting product priorities, not outright opposition to open standards.
The singular data point that I can think of as being anti-standard is the pending drop of CalDAV for Calendar, which I personally think sucks. But nobody ever cites that. Everybody's pissed that Google canceled a product that they liked, and that's what's driving this never-ending criticism.
The main problem with Google at the moment is the centralization of many popular services into one corporate entity. Video, search, email etc. are all now in the hands of, mostly, Google. With so few viable competitors, you get a de-factory monopoly as well as insane growth. The centralization itself is the problem.
Success like this does not breed innovation. Aside from some novel extra-Internet projects like Glass and autonomous cars, Google does not innovate much, and many of these services have stagnated, and Google does not seem to care much about Internet standards or about being ethical.
I can get behind your first paragraph, which is basically just saying that as a consumer you like to support variety and a dynamic market by using services from multiple providers. If that's you're goal, that's a reasonable enough justification for me. However, that's not a reaction that would come as a direct result of one product cancellation (because it is a proactive, not reactive perspective), and my comment is in response to the post, which explicitly claims the reason for expunging Google is due to Google's supposed new opposition to open standards.
I really don't understand your angle with the second paragraph though. It's just the kind of stuff that's going to make this all devolve into a battle of words about who the best/worst/most evil/most creative/most underdog/most overvalued/undervalued/deserving/undeserving companies are. Frankly a generalization like that without any specifics or context is a fanboy thing to say. If you're trying to tell me that Google is a stagnating company doing more net harm than good, all I think it's worth to say is that I think you're terribly wrong, and I disagree.
He is not claiming an opposition to open standards, but that open standards are secondary, and will get thrown under bus if it conflicts with the primary goal of making money, and that it seems Google believes social in general and Google+ is the way to make more money, and that this puts open standards at risk.
Reducing your dependency on Google's support for open standards then becomes prudent.
Personally I'm sticking with a number of Google services, but I'm also taking precautions (backing up my data; my primary address is on my own domain so I can move away from Gmail easily if I want to (don't think they'd close it down, but they certainly can - and have - made changes that I find detrimental; I only stick with Gmail now because of a number of tweaks using Minimalist, for example)
It's not so much that Google has become horrible, but that they've taken a number of steps to be "less good" than what a lot of people have come to expect and depend on. They're on their way to being "just another company" instead of anything special.
No he is arguing that because Google closed down Reader, using any other service offered by Google is poor judgement while also stating that they don't innovate in many if not all product areas.
I can't read that from the original comment. In fact, he didn't even mention Google Reader specifically.
If you are referring to the original article, the article makes it fairly obvious that the GReader event was the proverbial last straw, not the main motivator.
Yes, as a consumer I would like variety and a dynamic market. But regarding the second point (proactive/reactive), I would also like an ecosystem of businesses that are engaged in some level of technological cooperation towards common goals. This over-reliance on Reader, for example, is an example of a bad ecosystem. It's not entirely Google's fault; it's also our fault as users for not seeing the single-provider trap until too late, and it's the entire ecosystem's fault for marginalizing feed technology in favour of intrusive ad-infested web sites.
As for the second paragraph: My point is that once you have a certain amount of dominance, and a certain amount of traction in the market (of the kind that it's hard to switch from, such as Gmail or Reader or Docs/Drive), it's no longer important prioritize openness or sharing or standards compliance. Those things don't matter in the short run to your user base, many of whom are loyal by necessity (switching is hard) or inertia (don't really care, it's the default choice), or who just don't know or care. It doesn't really matter to your bottom line if you piss of a minor percentage (eg., Reader, or the recent post about Google not providing any kind of support), and the competition is so small that they don't matter much either.
- Video: Till Oct '12, youtube's market share peaked at ~52%. [1]
- Email: Gmail surpassed Outlook in market share only in Oct '12. [2]
- Search: Google Search 67.5% as of March 15, 2013. [3]
> many of these services have stagnated
And when they attempt to get out of markets so that other new companies can perform better, we get Reader like response.
> Google does not seem to care much about Internet standards
And how are you sure that FastMail and Vimeo (Alternatives suggested in the OP) are any better?
Would love to see some market-share breakdowns. Still, that's pretty huge. I expected them to bigger at video, but I guess there is a pretty long tail of smaller providers such as Vimeo and Liveleak and what not?
> And when they attempt to get out of markets so that other new companies can perform better
I really doubt that they canceled Reader for such altruistic reasons.
> And how are you sure that FastMail and Vimeo (Alternatives suggested in the OP) are any better?
I don't know what their market share is, but I bet it's very small compared to Google's. In other words, they have to care about standards because they are nowhere near in control.
> they canceled Reader for such altruistic reasons
There is no evidence that it was done to bring more users to Reader (like the article suggested) either. They did allow you to takeout your reader content. So yes I do evidence that they hope that users find services that fit their needs.
>Email: Gmail surpassed Outlook in market share only in Oct '12.
Sorry, you can't say "Outlook" when it's actually "Hotmail". Just because Hotmail had 400 million accounts, doesn't mean Outlook will have, too. Outlook only had 10 million accounts last I checked.
Good question. There aren't many. Most of the ones I can think of (Kickstarter, Github, Heroku) launched years ago and have since built on their success without really innovating much beyond the initial idea.
The YC portfolio has a lot of interesting, innovative startups. No products that I use myself at this point, though.
Right now, personally, the new idea I find the most exciting is crowd-funding computer games. Last year I spent a ton of money on Kickstarter to fund small indie developers such as Double Fine.
The innovation is the crowd-funding model used to seed non-mainstream (in the sense that these games are all fairly "nerdy" compared to the average Facebook user) stuff with real budgets.
I'd have to disagree on the innovation point. Google continues to make dramatic improvements (imo) to many of their apps and services. As a developer building on Docs/Drive, I've seen that service continuously grow and expand, though much of the work remains below the waterline. Similarly, Maps, Now, Voice Search, Chrome, App Engine continue to be improved at a rate that outstrips what I'm used to at most other companies Google's size.
It's true that the visible feature changes have slowed significantly, but I'd attribute that more to the size and completeness of the existing products than anything else. It's also true that they aren't entering many new product lines, though for one thing I'm not sure that's something you'd lament and for another, I hear they've declared they won't be entering any new business that they expect to be below $1bn.
Google does iterate their products, but I don't see much innovation. Granted, I haven't tried Now, as I don't have an Android phone, but it does sound like real innovation.
I just don't see much happening with other products. Chrome? Just getting slower and more bloated. App Engine? Does nothing for me that Heroku doesn't. Docs, while impressive, came out years ago, and Drive is basically a Dropbox/iCloud clone.
Google actually made a huge reverse-innovation with Google+, which is essentially just Facebook rewritten for the Google ecosystem. It's pretty much as invasive as Facebook in how it attempts to smear the contents of your private life across an impersonal surface, and it seems to belong to another era of walled-garden services that don't integrate with anything other than itself (posts doesn't even support formatting other than bold and italic, how's that for retrograde?).
So as you suggested, lets simply want to ignore Now, Android, Maps, Glasses and Self Driving cars:
Chrome: A hell lot of features that are pushing web forward, arguably the best development tools, significant contribution to Webkit (now to Blink), becoming platform for Chrome OS, v8 engine that serves as basis for NodeJs.
App Engine/Drive: So when Heroku/Dropbox does it, it can be called innovation but when GAE/Drive does it, it is just iteration? That's an insane standard to work against.
> doesn't even support formatting other than bold and italic, how's that for retrograde.
There is no way you could argue that supporting lists and headings will suddenly make Google+ an innovative product out of nowhere. What I find awesome are Hangouts and circles. They work very nicely for me, YMMV. You can set the entire profile to be hidden and no one will be smearing contents of your private life anywhere. I am not sure exactly is this complaint coming from.
> Chrome: A hell lot of features that are pushing web forward …
There are technical innovations, but I thought we were talking about product innovations. Users don't care about WebGL or canvas or CSS3. Those things are not innovations to them.
The only significant user-facing innovation in Chrome is arguably the extension/app store. Maybe incognito browsing, although I believe Safari had that first.
> App Engine/Drive: So when Heroku/Dropbox does it, it can be called innovation
The word "innovate" derives from the Latin name for new. You don't innovate by copying. Heroku (as far as I know) launched a year before Google, and is clearly prior art. Dropbox launched years before.
> There is no way you could argue that supporting lists and headings will suddenly make Google+ an innovative product out of nowhere
I didn't say that. I said that the lack of support for formatting is old-fashioned (the opposite of innovative, really).
No, I'm saying that Google is innovating very little. Indeed, it's primarily innovating in areas not related to the web (which the article is about).
Search, Maps,YouTube have not evolved much the last few years; the last true innovation was Street View, and the last truly useful addition to Search was the fact database integration. Android is basically just following in Apple's footsteps. Wallet I don't know anything about, so I can't comment, Shopping looks to me like it's still the terrible old shopping search that isn't useful for anything. Google+ is basically a reimplementation of Facebook.
Go may have been created at Google, but it's really the work of Pike and Thompson; according to insiders, the internal language at Google is still mainly Java and C++; and I wouldn't call it innovation, exactly, since there is nothing innovative about neither the parts or the whole; rather, it's a very incremental evolution of the general-purpose computer language tradition of C plus Oberon/Modula.
In other words, your sarcasm is wildly misplaced, sir.
Too bad you are so hard trying to make your point you lose connection with reality.
Android, in its core, is so entirely different then iOS that saying "following in Apple's footsteps" is just wrong. What has changed in recent major (!!) iOS updates? Twitter & Facebook integration.. Seriously?
While Android 4 revamped the entire user interface, streamlined ui & ux and allowed for buttonless phones (apart from power).
Also, Google Maps recently added vector based maps, a great addition to the previous bitmap based maps.
Search has added countless quick results like instant currency conversion, quick answers to questions and instant results.
Gmail has litteraly changed web based mail and still continues to do so.
I do agree on youtube & go. Go isn't a revolution, it is one of the most boring languages ever. Which is one of it major plusses over "exciting" languages like ruby & python. Also, it isn't an offcial Google product, so stomping Go to the ground really shows how you are just bashing away.
Please don't say innovation has stopped when it clearly hasn't.
Those are not innovations, those are incremental improvements. (If you want to call all minor improvements innovation then, well, everyone's innovative.) Innovations are new products and new ideas.
Of course Android is following in Apple's footsteps; Apple came first, after all, and established everything that Android has since also implemented. Whatever Google is doing, it's an incremental improvement on that revolutionary approach to smartphones. Google Glass is innovative, possibly even revolutionary; but Android isn't.
> Google Maps recently added vector based maps
I doubt users notice that. (I'm a developer and I haven't noticed.) (Also, didn't Apple do this first, with the Maps app?) I'm sure there is lots of technical, low-visibility innovation happening at Google, but that's not what we are talking about here.
> Search has added countless quick results
Again, miniscule, evolutionary improvements.
> Gmail has litteraly changed web based mail and still continues to do so.
Gmail launched in 2004 and has hardly changed since then. Sure, it got priority inbox (a minor feature, hardly the revolutionary feature they claimed), GTalk and themes. Not really innovations in any meaningful sense. Gmail is possibly the worst example of all, since everything after 2004 has essentially been polish.
> Also, [Go] isn't an offcial Google product, so stomping Go to the ground really shows how you are just bashing away.
The parent was the one who mentioned Go, I merely responded.
I would argue that an open smartphone ecosystem is innovative. Not original, but innovative.
Google Now IS innovative.
Google's method for voice recognition is certainly innovative, as are the myriad ways in which they have implemented that core technology.
Google voice (grandcentral) was certainly innovative; the calling system and the text transcription in most specific.
My main problem with your exchange is my perception of you constantly moving the goalposts. I don't see how you can categorically reject 'technical, low-visibility innovation' unless your argument is presupposed.
Furthermore, most of these achievements are acquire/hires, and we have seen the big G push these purchased assets into new features or products. I would argue that this capability IS the basic facility to innovate the marketplace.
(gmail has indeed revolutionized webmail, both in size of free storage and in the mailbox organizational methods)
Symbian was an open smartphone ecosystem. Google is just taking it a step further (to serve its own ends, of course).
I am not moving the goalposts. The original article was about Google web products such as Chrome and Reader. The only non-productized item mentioned was OpenID, which concerns integration with the rest of the web and could be considered a feature of their user-facing products. These things are the things that matter to people when they view Google as a company. Not whether Maps has vector graphics.
So, yeah, for the purposes of this discussion, I do discount technical, low-visibility innovation. If we are talking purely about technology, then sure, Google is probably an innovation leader.
"Google voice (grandcentral) was certainly innovative; the calling system and the text transcription in most specific."
As an original GrandCentral user, I take this as a complete insult. Google bought GrandCentral and removed features. So chalk this one up to negative innovation.
"Let's be clear that this has nothing to do with revenue vs operating costs. Reader never made money directly (though you could maybe attribute some of Feedburner and AdSense for Feeds usage to it), and it wasn't the goal of the product.
Reader has been fighting for approval/survival at Google since long before I was a PM for the product. I'm pretty sure Reader was threatened with de-staffing at least three times before it actually happened. It was often for some reason related to social:
2008 - let's pull the team off to build OpenSocial
2009 - let's pull the team off to build Buzz
2010 - let's pull the team off to build Google+"
In my experience Google buys something, lures people into using it for years, lets it languish without improvements for years so long as it serves their purposes, then kills it off.
Whether they're "working against the potential of the open Internet" is another question altogether. They like head counts, but like certain fickle people in all of our lives, the idea of actually having a real enduring relationship never crosses their Aspergian heads. It's just business. We've already got enough of that ruining the world. Some of us actually yearn for a better future ... not just enduring life on the way to Alpha Centauri or whatever.
You must have not been paying attention. A long list of evidence has been posted here on HN on several occassionas, including dropping CalDAV, of Google turning against the open web.
It's nothing new either, it has been going on for years. They've even dropped their support for net neutrality years ago.
In the mean time Google has been heavily pushing the Google+ walled garden, their anti-privacy and anti-anonymity agendas, and has been pro-active in filtering their services on behalf of the copyright-exploitation industry.
This is not a conspiracy theory, it's just a matter of connecting the fairly obvious dots that barely need connecting because there are so many of them by now all that's missing is an official "fuck the open web" press statement.
3 if I count correctly: Reader closedown (which, in my opinion, not a hit to open web at all), XMPP Federation issue (It's fixed now) and CalDAV whitelist (Not closedown, whitelist).
Doesn't whitelisting amount to closing of interface? They may very well use the CalDav protocol which is open, but how good is it if the consumption interface is not open?
Perhaps it was done to prevent spam, or to prevent misbehaving clients from wreaking havoc on its servers.
From hearsay, I understand it's reasonably easy to get on the whitelist if you're a moderately-known app developer or a legit institution. This would lead me to believe Google's reasons are less nefarious in this case.
They dropped the Microsoft Exchange format for syncing contacts in favor of the open cardDAV format, so that's one piece of data the points in the other direction.
[Edit: originally typed "calendars" instead of "contacts".]
Google has made several mistakes re social products but it's definitely not against the open web. There's a lot of internal criticism every time one of these decisions is made but, at the end of the day, upper management gets to do whatever they want.
I've never met anybody at Google how was happy with the way G+ is being handled or liked Vic Gundotra. A lot of us rather he'd go back to Microsoft.
Most important thing is to not get so entrenched in one technology vendor or another. They are not part of you. You're not an Apple person or a Google person - that's just how companies want you to think. Don't let technology choices become part of who you think you are. Use tech that helps you until it doesn't. Always have an exit plan. Don't get emotionally attached to one company or emotionally put off another. They're corporations. The don't care about you. Thy offer a service. If that service comes as part of a trade you're comfortable with use it, else don't.
I don't think Google is 'actively working against an open web', but the shuttering of Reader in order to make way for that ghastly Google+ makes me reconsider every time they open up a new service (didn't even glance at Keep, for example. Remember what happened to Google Notebook?)
It's nice to have open source alternatives, and possibly to help them grow. If a lot more people start using, say, ownCloud, it will probably help develop it into a more robust and usable platform. Also, as a hacker, having a stack of my own software side-by-side with my current Google/Apple stack will probably help me learn more as I use it more, and will give me something to fall back on in case Google shutters it.
"the shuttering of Reader in order to make way for that ghastly Google+"
There's a lot of erroneous assumptions in there. Reader was never really a product with much support, it was more a labor of love of a small dedicated team. Reader was not shutdown to "make way for G+" anymore than any of the other spring cleaned services were shut down because of competing services. Even the original (ex-Googler now) Reader engineers have pretty much outlined many of the reasons, including the decline of RSS, which was killed off in large part by people moving to services like Twitter, Facebook, and Tumblr.
It's really regretable, but it's time to realize that the rest of the world moved on, and if we want federated, open services, it's going to have to built from the ground up, and in a way that users, not hackers, will want to use it.
I don't know about replacing Google with DDG. I'd prefer an engine that actually does its own indexing. Yandex is the only alternative that fits the bill in my mind: http://www.yandex.com
Also, so happy to learn about ownCloud. As a developer, I'm a little disappointed to see AGPL licensing, but it's probably a smart choice and I use that license in some projects.
DDG actually pulls its results from Yandex and several other sources. Why limit yourself to a single, old-fashioned crawler, when you can use one of the most innovative meta-search engines?
Meta-search is a pretty old idea too. And you're at the mercy of your sources and have less insight into the data you're searching and less ability to rank pages.
I'd like to give credit to Google where it is due. With takeout, it is very easy to get quite a bit of your information. You already could get your emails by IMAP or POP but still Google set a standard with Takeout :)
This makes it possible for someone to just pack his bags and leave. This is also the reason why I am staying.
I try to avoid these sorts of submissions, mainly because of their non-content and the subsequent familiar discussion, but somehow they keep reaching the front page.
It’s certainly your prerogative to use whatever you like but the incorrect assertions bother me, especially the prevalent one: “It's because I think that Google is now working against the potential of the open web”.
Here’s a rebuttal in the form of a partial list of links to Google initiatives that exist primarily to advance the “open web”:
I don't think the closure of Google Reader was any indication to the contrary, and all of these are certainly much more important to the web than yet another centralized RSS reader.
Other errors in that post: Chrome never ‘dropped decent RSS support’ as it never supported it to begin with, it was actually Firefox that dropped their support. Also there is no evidence that Reader was closed to “drive users to Google+”, there is no proof nor common sense explanation to support that assertion.
Here’s a rebuttal in the form of a partial list of links to Google
initiatives that exist primarily to advance the “open web”:
http://www.chromium.org
That's funny. I see Chromium as their OSS alibi for doing whatever non-standard they want with open-web HTML, which doesn't exist in any other browser. But now it's not "proprietary", because it's in a OS code-repo somewhere.
So now it's "standards" even though it hasn't been submitted, ratified or approved yet. And everyone else, if they dont want Google's stuff to work poorly in their browser, has to be a dog and follow Google's leash.
I consider Chromium some of the worst damage Google has done to the open web.
Interesting opinion. I hadn't considered it like that at all, but I will give it some thought. How much of the non-standard stuff is getting any use/traction (honest question)?
For me, currently, Chromium seems like nothing like a good thing. For example, their Linux sandboxing appears to be at least a step ahead of anything else so far.
owncloud was an interesting item on his replacement list. Has anyone else used owncloud and can vouch for it? If so, are you self-hosting it or using a commercial host? If the latter, which one?
owncloud was an interesting item on his replacement list. Has anyone else used owncloud and can vouch for it? If so, are you self-hosting it or using a commercial host? If the latter, which one?
I've asked multiple times about adding subdomains to distinguish repos from blogs, but it appears that this is a workaround that no subdomain reporting would detect
Google Maps has its share of little cities showing before big ones. I currently see a Digoin on the map of France whereas Saint-Étienne, Clermont-Ferrand, Bourges (or Laval) do not appear...
I have seen many of these posts recently and I honestly do not understand. I use Google products and it definitely beats out most of the competition and doesn't interfere with anything worse than any other product out there. Sure the internet is changing, and you can either go with it (or not). Switching to many different products to complete the same tasks (many of them worse than Google products) seems kind of silly to me.
If you're a user on a commercial system you didn't pay for (Google, Facebook, etc.) then you're not a customer, you're cattle. Your value is directly proportional to how much the company running the system knows about you.
I don't like where Facebook is going, and I think Google is following in their footsteps, albeit helped along by an excellent reputation for quality and fair play, especially amongst geeks.
Maybe I'm just being a curmudgeon, but I think Google is playing the same 'embrace and extend' card as Microsoft did back in the day, just for slightly different reasons.
> Maybe I'm just being a curmudgeon, but I think Google is playing the same 'embrace and extend' card as Microsoft did back in the day, just for slightly different reasons.
I see this meme a lot, but I don't get it how the analogy is supposed to work.
The key part of "embrace, extend, and extinguish" strategy was extending the standard in proprietary ways, thus making it incompatible and no longer implementable via open source software, thus killing it.
I don't get how any of this applies to any web company, where nearly the entire business is based on the web and the standards that back it. It's no wonder that many of these companies contribute back to the web standards and open source software. Sure, these contributions are in the company's interests--but that's the whole point. We reached a time when it's in interests of many big (and small) corporations to contribute to open source and standards (including Microsoft!).
Some people see efforts to improve standards or contribute new ones as somehow bad, "embrace and extend". When actually it's the opposite: investing in the commons to promote its welfare.
Obligatory disclaimer: speaking for myself here, not any employer past or present.
... except where it isn't in their interests, which is why Google is trying to kill off RSS with a multi-pronged strategy (ignore RSS in Chromium, kill off RSS reader, don't offer an RSS feed in G+).
If your platform is free-as-in-beer, you have to monetise your users to advertisers. You do this by learning more about them by keeping them within your ecosystem, not by allowing them access to your platform through open protocols.
I see it as a fundamental conflict between users of a system (you and me) and the customers (advertisers). Google has made it clear which side of that equation they care about. See e.g. their support of DRM in HTML.
Not only would that be a pretty poor multi-pronged strategy, it still has absolutely nothing to do with "embrace, extend, and extinguish", as the parent pointed out.
And, seriously, "ignore RSS in Chromium" is now kowtowing to advertisers? How about the lack of gopher support[1]? And no built in bittorrent client[2]??
I'm starting to agree with others that you have a point somewhere in here but you're missing it over anger about Reader.
Not exactly embrace and extend like MS did it, but similar in spirit: take an open protocol, embrace it for a while, gradually weaken it over time in favour of a parallel closed system, then once everyone is happily using it, kill it dead and watch the migration into the closed system.
If I had to guess, I'd say that torrent support was nixed for fear of offending Big Content; Opera has already showed that it's reasonable for a browser to support it. Also there's already a plugin for that protocol, so it may just be a low priority for the team. Odd that they flagged the request 'invalid' though.
(Please stop telling me that I'm angry about Reader. It's not that I'm angry: I've identified what I think is a pattern in Google's behaviour, figured out what their end goal is, and it troubles me. So I'm abandoning their platform to the greatest extent practical.)
That's not similar in spirit to "embrace, extend, and extinguish", and not even a good description of what they've done. There's no migration path from Reader to G+ (presuming that's what you mean by "the closed system"). There's not even a clear correspondence between the content in each, and meanwhile Google does provide a migration path to other RSS readers.
I think there is a clear argument for Google consolidating around APIs and their social network instead of federated protocols in the future. However, the whole "strategy to kill off RSS" thing is silly and undermines the other arguments you're making.
The bittorrent and gopher comments were facetious. It's not at all clear that all browsers should have a button that appears when a page has an RSS feed and, when pressed, opens a different web page to then enter the address of that RSS feed into your reader. Zawinski's Law was not meant as praise.
The lack of that RSS button is no more evidence of trying to kill RSS than the lack of gopher support is evidence of Google's plot to make sure that Gopher will never rise again like a phoenix and supplant the World Wide Web once and for all. Instead, you make sure extensions are able to build that button for those that want it (or put an option to enable it in about:config) and you call it a day.
99% of websites make money from ads. And I wouldn't have it any other way. Imagine if everyone even asked for $1 per month to sustain themselves. That would be unfeasible. Ads are here to stay.
This is not conscious consumerism. This is a childish temper tantrum.
Chrome has better developer tools. If your job is being a web dev and you purposely make your job harder because you're mad at Google for shutting down Reader, you're not being rational.
I'll still happily use Chromium for web development, as and where necessary. Just not signed in to Google for sync, etc. etc.
I do wonder though ... would you have described the formation of the FSF as a childish temper tantrum? I remember the days when to use Linux as a development OS was painful ... it worked out well in the end though :)
I don't entirely agree with the GP's phrasing, but it's worth pointing out that the FSF doesn't paint all a company's software with the same brush. They're happy to rail against non-free software while accepting contributions to GNU projects from the same developers.
FSF is an ideal. The ideal that all software is open source so that it's more secure and has all the other benefits of open source. What you're doing is being childish. "Boo hoo, big bad Google killed a product I liked, so I'm going to make some bullshit arguments to stop using ALL their products."
I don't use all of Google's products, but I use a subset because they get the job done well. If you think killing off reader was a bad idea, why not build your own and see how the cost/benefit ratio pays off. What problem are you even solving by doing this? You're just throwing a childish fit.
I don't think it was a bad idea, I think it was a very good idea from their perspective. I think that what they're trying to do is a bad idea for everyone, which is why I've changed platform.
That is one way to look at it. The other is: Google is creating a walled garden on Google Plus, and pushing it with all its might. Walled gardens are contrary to the ideal of an open web.
In that vein, boycotting Google is as much idealistic as boycotting closed software.
Your analogy doesn't work at all. The FSF is about a goal. It is a noble goal, and it has clearly shaped the software world for the better.
I ran Linux and did lots of development under it in the 90s. I quite enjoyed it and preferred it to Windows development at the time. I use Linux every day for work.
That doesn't mean I don't boot up Windows to play BioShock Infinite, even though I disagree with a lot of things Microsoft does.
I've never found Firebug to be lacking; what do the Chrome developer tools have that make it impossible to stop using Chrome?
In my experience Chrome is a PITA for web development due to its weirdly aggressive caching. I thought people were just making it up a few months back, but I experienced it recently and it's infuriating.
It's hard to nail down the difference between Chrome Dev Tools and Firebug with just one thing. For me it's not one killer feature it's a quality of life issue. It's all the little things that, IMHO, Chrome Dev Tools does right.
I have no problem using Firebug or even the Firefox Inspector when needed to actually find a Firefox specific problem but for working day in and day out, I prefer the experience of the Chrome Dev Tools.
RSS just isn't very popular. Firefox also removed that RSS icon from the address bar a few months ago. Do you think Mozilla did that because they "oppose the open web"?
No, of course they don't. They got rid of it because virtually no one used it.
Just like everybody else said, Google is not moving against the open web. Rather the opposite. The only thing I agree with is the part where Google tries to get everybody to use Google only, which makes sense considering Google can be compared to a small empire. I mean, has anyone seen the office buildings that Google has?
As for Chrome, I think Webkit (or now Blink) is where web happens fastest. All new web experiments are done with -webkit, not -moz-, and you gotta go where the majority goes. In this case anyway. I haven't used gmail for a long time tho', because I didn't like that the content of my emails get used for ads - so I set up my own email server for personal usage. Other then that, maps, search .. it does what I need it to do so whether it tracks me or whatever is just the cost of the service.
174 comments
[ 3.2 ms ] story [ 224 ms ] threadwhy not openstreetmaps?
Parts of the world in my case ~= Sydney, which has a decent number of geeks per capita to contribute. OSM is wonderful, but has a way to go before it's a viable solution for everyone.
I've just recently discovered (and love) TileMill.
http://basecamp.com/breeze
$20 one-time payment to create a group email list.
Secondly, Reader was not killed because of G+. If FriendFeed is finally killed off, will you say it was because Facebook needed the resources and engineers on a competing product? Consumers have moved on to desire the kinds of features that are inherent in services like Facebook, and RSS simply isn't suited to solving the problem of federated social networking. There is no open standard for this, remember, Google tried it with PubHubSubHub/WebFinger/OpenID/OAuth/ActivityStreams but it didn't work.
I favor federated feeds as well (see my essay http://timepedia.blogspot.com/2008/05/decentralizing-web.htm...), but honestly, for me personally, RSS was a HUGE step back from what I had on USENET in the 80s with RN/TRN. Someone must create a new, open federated social networking platform, but honestly, you can't put the cart before the horse. Google tried that several times and failed.
First, you've got to built a super successful platform consumers love, then you can standardize it. The history of doing it the other way is littered with failure. Remember OpenSocial?
I don't think Google has lost sight of the Open Web, I think it just realized that you must focus on the end user design issues first if you want to be successful. Ignore this at your peril, look at the way consumers flock to native apps on mobile. They care about experiences, not implementation. If the "open web" specs don't do the job, then you need to create a product first that consumers show they want, and then work backwards to figure out how to fix the specs.
You're also correct that RSS doesn't solve the problem of federated social networking. It was never intended to.
W.r.t. developing protocols for federated social networking: Google isn't interested; it would harm their bottom line if users on their systems could easily share content outside those systems. Hence why Google+ doesn't even offer an RSS feed.
Do you really, hand-on-heart, think that Google would support a federated social media protocol on Google+ should such a thing come into being? Do you think they're planning to build such a protocol?
If you look at G+, Google has taken a very very careful approach this time (after OpenSocial, Buzz, Wave, et al failed), building on it very incrementally, always concentrating on user experience at each step. Even to the extent that they don't have even have an API to post content to G+ programmatically. Whether or not it will eventually turn into some idea federated open network, I have no idea.
But I would not take G+ as somehow Google dropping support for the open web. Google is a very large company with lots and lots of product, and company culture just doesn't change overnight.
I'd love it if Google had done a disapora-like federated system. But honestly, if they had gone that route, we'd have threads all over the blog-sphere laughing at Google for yet another social networking failure.
Those kinds of projects earn the love and adoration of the hacker community, but they don't get grandma, teens, and celebrities on your site.
Want better counter-evidence? Look at WebRTC and Google Hangouts. Hangouts are a defining competitive advantage G+ has over all over social networks, and Google sponsors a spec that essentially makes them a commodity that anyone can implement now.
Clearly you don't though.
Perhaps we should resume this conversation in five years time? :)
I agree with you on the Android front, too. Although I'm still struggling to get a new qwerty after my pro+ died :(
You can argue that they're against certain open standards if you want, but the canceling of Reader isn't actually evidence of that. Simultaneously putting effort into G+ is also not evidence of that. It's not even symbolic of that. It is only evidence of shifting product priorities, not outright opposition to open standards.
The singular data point that I can think of as being anti-standard is the pending drop of CalDAV for Calendar, which I personally think sucks. But nobody ever cites that. Everybody's pissed that Google canceled a product that they liked, and that's what's driving this never-ending criticism.
Success like this does not breed innovation. Aside from some novel extra-Internet projects like Glass and autonomous cars, Google does not innovate much, and many of these services have stagnated, and Google does not seem to care much about Internet standards or about being ethical.
- you're joking right?
I really don't understand your angle with the second paragraph though. It's just the kind of stuff that's going to make this all devolve into a battle of words about who the best/worst/most evil/most creative/most underdog/most overvalued/undervalued/deserving/undeserving companies are. Frankly a generalization like that without any specifics or context is a fanboy thing to say. If you're trying to tell me that Google is a stagnating company doing more net harm than good, all I think it's worth to say is that I think you're terribly wrong, and I disagree.
Reducing your dependency on Google's support for open standards then becomes prudent.
Personally I'm sticking with a number of Google services, but I'm also taking precautions (backing up my data; my primary address is on my own domain so I can move away from Gmail easily if I want to (don't think they'd close it down, but they certainly can - and have - made changes that I find detrimental; I only stick with Gmail now because of a number of tweaks using Minimalist, for example)
It's not so much that Google has become horrible, but that they've taken a number of steps to be "less good" than what a lot of people have come to expect and depend on. They're on their way to being "just another company" instead of anything special.
If you are referring to the original article, the article makes it fairly obvious that the GReader event was the proverbial last straw, not the main motivator.
As for the second paragraph: My point is that once you have a certain amount of dominance, and a certain amount of traction in the market (of the kind that it's hard to switch from, such as Gmail or Reader or Docs/Drive), it's no longer important prioritize openness or sharing or standards compliance. Those things don't matter in the short run to your user base, many of whom are loyal by necessity (switching is hard) or inertia (don't really care, it's the default choice), or who just don't know or care. It doesn't really matter to your bottom line if you piss of a minor percentage (eg., Reader, or the recent post about Google not providing any kind of support), and the competition is so small that they don't matter much either.
Not really:
> many of these services have stagnatedAnd when they attempt to get out of markets so that other new companies can perform better, we get Reader like response.
> Google does not seem to care much about Internet standards
And how are you sure that FastMail and Vimeo (Alternatives suggested in the OP) are any better?
[1] http://videonuze.com/article/youtube-s-market-share-nudges-u...
[2] http://gigaom.com/2012/10/31/gmail-finally-beats-hotmail-acc...
[3] http://searchenginewatch.com/article/2255183/Google-Grabs-Mo...
> And when they attempt to get out of markets so that other new companies can perform better
I really doubt that they canceled Reader for such altruistic reasons.
> And how are you sure that FastMail and Vimeo (Alternatives suggested in the OP) are any better?
I don't know what their market share is, but I bet it's very small compared to Google's. In other words, they have to care about standards because they are nowhere near in control.
They are not monopolistic, like you said.
> they canceled Reader for such altruistic reasons
There is no evidence that it was done to bring more users to Reader (like the article suggested) either. They did allow you to takeout your reader content. So yes I do evidence that they hope that users find services that fit their needs.
Also, porn.
Sorry, you can't say "Outlook" when it's actually "Hotmail". Just because Hotmail had 400 million accounts, doesn't mean Outlook will have, too. Outlook only had 10 million accounts last I checked.
Can you please give a few examples of innovative companies these days? (And I am totally serious, no snark/sarcasm intended)
The YC portfolio has a lot of interesting, innovative startups. No products that I use myself at this point, though.
Right now, personally, the new idea I find the most exciting is crowd-funding computer games. Last year I spent a ton of money on Kickstarter to fund small indie developers such as Double Fine.
It's true that the visible feature changes have slowed significantly, but I'd attribute that more to the size and completeness of the existing products than anything else. It's also true that they aren't entering many new product lines, though for one thing I'm not sure that's something you'd lament and for another, I hear they've declared they won't be entering any new business that they expect to be below $1bn.
I just don't see much happening with other products. Chrome? Just getting slower and more bloated. App Engine? Does nothing for me that Heroku doesn't. Docs, while impressive, came out years ago, and Drive is basically a Dropbox/iCloud clone.
Google actually made a huge reverse-innovation with Google+, which is essentially just Facebook rewritten for the Google ecosystem. It's pretty much as invasive as Facebook in how it attempts to smear the contents of your private life across an impersonal surface, and it seems to belong to another era of walled-garden services that don't integrate with anything other than itself (posts doesn't even support formatting other than bold and italic, how's that for retrograde?).
Chrome: A hell lot of features that are pushing web forward, arguably the best development tools, significant contribution to Webkit (now to Blink), becoming platform for Chrome OS, v8 engine that serves as basis for NodeJs.
App Engine/Drive: So when Heroku/Dropbox does it, it can be called innovation but when GAE/Drive does it, it is just iteration? That's an insane standard to work against.
> doesn't even support formatting other than bold and italic, how's that for retrograde.
There is no way you could argue that supporting lists and headings will suddenly make Google+ an innovative product out of nowhere. What I find awesome are Hangouts and circles. They work very nicely for me, YMMV. You can set the entire profile to be hidden and no one will be smearing contents of your private life anywhere. I am not sure exactly is this complaint coming from.
There are technical innovations, but I thought we were talking about product innovations. Users don't care about WebGL or canvas or CSS3. Those things are not innovations to them.
The only significant user-facing innovation in Chrome is arguably the extension/app store. Maybe incognito browsing, although I believe Safari had that first.
> App Engine/Drive: So when Heroku/Dropbox does it, it can be called innovation
The word "innovate" derives from the Latin name for new. You don't innovate by copying. Heroku (as far as I know) launched a year before Google, and is clearly prior art. Dropbox launched years before.
> There is no way you could argue that supporting lists and headings will suddenly make Google+ an innovative product out of nowhere
I didn't say that. I said that the lack of support for formatting is old-fashioned (the opposite of innovative, really).
Btw, here are some Google products that it continues to iterate:
Google Maps YouTube Android Wallet Google+ Go AngularJS Shopping
However, if you don't want to count these ones, I guess you're right that most of Google's services have stagnated.
#sarcasm
Search, Maps,YouTube have not evolved much the last few years; the last true innovation was Street View, and the last truly useful addition to Search was the fact database integration. Android is basically just following in Apple's footsteps. Wallet I don't know anything about, so I can't comment, Shopping looks to me like it's still the terrible old shopping search that isn't useful for anything. Google+ is basically a reimplementation of Facebook.
Go may have been created at Google, but it's really the work of Pike and Thompson; according to insiders, the internal language at Google is still mainly Java and C++; and I wouldn't call it innovation, exactly, since there is nothing innovative about neither the parts or the whole; rather, it's a very incremental evolution of the general-purpose computer language tradition of C plus Oberon/Modula.
In other words, your sarcasm is wildly misplaced, sir.
Android, in its core, is so entirely different then iOS that saying "following in Apple's footsteps" is just wrong. What has changed in recent major (!!) iOS updates? Twitter & Facebook integration.. Seriously? While Android 4 revamped the entire user interface, streamlined ui & ux and allowed for buttonless phones (apart from power).
Also, Google Maps recently added vector based maps, a great addition to the previous bitmap based maps. Search has added countless quick results like instant currency conversion, quick answers to questions and instant results. Gmail has litteraly changed web based mail and still continues to do so. I do agree on youtube & go. Go isn't a revolution, it is one of the most boring languages ever. Which is one of it major plusses over "exciting" languages like ruby & python. Also, it isn't an offcial Google product, so stomping Go to the ground really shows how you are just bashing away.
Please don't say innovation has stopped when it clearly hasn't.
Of course Android is following in Apple's footsteps; Apple came first, after all, and established everything that Android has since also implemented. Whatever Google is doing, it's an incremental improvement on that revolutionary approach to smartphones. Google Glass is innovative, possibly even revolutionary; but Android isn't.
> Google Maps recently added vector based maps
I doubt users notice that. (I'm a developer and I haven't noticed.) (Also, didn't Apple do this first, with the Maps app?) I'm sure there is lots of technical, low-visibility innovation happening at Google, but that's not what we are talking about here.
> Search has added countless quick results
Again, miniscule, evolutionary improvements.
> Gmail has litteraly changed web based mail and still continues to do so.
Gmail launched in 2004 and has hardly changed since then. Sure, it got priority inbox (a minor feature, hardly the revolutionary feature they claimed), GTalk and themes. Not really innovations in any meaningful sense. Gmail is possibly the worst example of all, since everything after 2004 has essentially been polish.
> Also, [Go] isn't an offcial Google product, so stomping Go to the ground really shows how you are just bashing away.
The parent was the one who mentioned Go, I merely responded.
Google Now IS innovative.
Google's method for voice recognition is certainly innovative, as are the myriad ways in which they have implemented that core technology.
Google voice (grandcentral) was certainly innovative; the calling system and the text transcription in most specific.
My main problem with your exchange is my perception of you constantly moving the goalposts. I don't see how you can categorically reject 'technical, low-visibility innovation' unless your argument is presupposed.
Furthermore, most of these achievements are acquire/hires, and we have seen the big G push these purchased assets into new features or products. I would argue that this capability IS the basic facility to innovate the marketplace.
(gmail has indeed revolutionized webmail, both in size of free storage and in the mailbox organizational methods)
I am not moving the goalposts. The original article was about Google web products such as Chrome and Reader. The only non-productized item mentioned was OpenID, which concerns integration with the rest of the web and could be considered a feature of their user-facing products. These things are the things that matter to people when they view Google as a company. Not whether Maps has vector graphics.
So, yeah, for the purposes of this discussion, I do discount technical, low-visibility innovation. If we are talking purely about technology, then sure, Google is probably an innovation leader.
As an original GrandCentral user, I take this as a complete insult. Google bought GrandCentral and removed features. So chalk this one up to negative innovation.
Pretty much every product you said have not evolved is continually improving.
You know I say that? Because I USE them.
I'm 100% sure you have not spent time using these products.
Ok, so products created within Google by Google employees don't count?
What other restrictions do you have?
One of the more amusing typos I have written while sleep-deprived. Sorry.
What's clear is that:
- Google is seeking to increase the monetary value of its users
- the way to do that is with social media (see Facebook, who are winning this battle hands down)
- they will push open standards under the bus where necessary, in order to drive users to Google+
As the former PM for Reader puts it (https://www.quora.com/Google-Reader-Shut-Down-March-2013/Why...):
"Let's be clear that this has nothing to do with revenue vs operating costs. Reader never made money directly (though you could maybe attribute some of Feedburner and AdSense for Feeds usage to it), and it wasn't the goal of the product.
Reader has been fighting for approval/survival at Google since long before I was a PM for the product. I'm pretty sure Reader was threatened with de-staffing at least three times before it actually happened. It was often for some reason related to social:
Whether they're "working against the potential of the open Internet" is another question altogether. They like head counts, but like certain fickle people in all of our lives, the idea of actually having a real enduring relationship never crosses their Aspergian heads. It's just business. We've already got enough of that ruining the world. Some of us actually yearn for a better future ... not just enduring life on the way to Alpha Centauri or whatever.
It's nothing new either, it has been going on for years. They've even dropped their support for net neutrality years ago.
In the mean time Google has been heavily pushing the Google+ walled garden, their anti-privacy and anti-anonymity agendas, and has been pro-active in filtering their services on behalf of the copyright-exploitation industry.
This is not a conspiracy theory, it's just a matter of connecting the fairly obvious dots that barely need connecting because there are so many of them by now all that's missing is an official "fuck the open web" press statement.
3 if I count correctly: Reader closedown (which, in my opinion, not a hit to open web at all), XMPP Federation issue (It's fixed now) and CalDAV whitelist (Not closedown, whitelist).
From hearsay, I understand it's reasonably easy to get on the whitelist if you're a moderately-known app developer or a legit institution. This would lead me to believe Google's reasons are less nefarious in this case.
[Edit: originally typed "calendars" instead of "contacts".]
For free customers. It's still there for us paying customers. Google pays Microsoft a licensing fee for use of the EAS specs.
I've never met anybody at Google how was happy with the way G+ is being handled or liked Vic Gundotra. A lot of us rather he'd go back to Microsoft.
It's nice to have open source alternatives, and possibly to help them grow. If a lot more people start using, say, ownCloud, it will probably help develop it into a more robust and usable platform. Also, as a hacker, having a stack of my own software side-by-side with my current Google/Apple stack will probably help me learn more as I use it more, and will give me something to fall back on in case Google shutters it.
There's a lot of erroneous assumptions in there. Reader was never really a product with much support, it was more a labor of love of a small dedicated team. Reader was not shutdown to "make way for G+" anymore than any of the other spring cleaned services were shut down because of competing services. Even the original (ex-Googler now) Reader engineers have pretty much outlined many of the reasons, including the decline of RSS, which was killed off in large part by people moving to services like Twitter, Facebook, and Tumblr.
It's really regretable, but it's time to realize that the rest of the world moved on, and if we want federated, open services, it's going to have to built from the ground up, and in a way that users, not hackers, will want to use it.
Also, so happy to learn about ownCloud. As a developer, I'm a little disappointed to see AGPL licensing, but it's probably a smart choice and I use that license in some projects.
http://help.duckduckgo.com/customer/portal/articles/216399
This makes it possible for someone to just pack his bags and leave. This is also the reason why I am staying.
It’s certainly your prerogative to use whatever you like but the incorrect assertions bother me, especially the prevalent one: “It's because I think that Google is now working against the potential of the open web”.
Here’s a rebuttal in the form of a partial list of links to Google initiatives that exist primarily to advance the “open web”:
http://www.webrtc.org
http://www.chromium.org
And their various web speed efforts:
https://developers.google.com/speed/spdy
https://developers.google.com/speed/pagespeed
And of course:
https://fiber.google.com
I don't think the closure of Google Reader was any indication to the contrary, and all of these are certainly much more important to the web than yet another centralized RSS reader.
Other errors in that post: Chrome never ‘dropped decent RSS support’ as it never supported it to begin with, it was actually Firefox that dropped their support. Also there is no evidence that Reader was closed to “drive users to Google+”, there is no proof nor common sense explanation to support that assertion.
See my other comments on this item for rebuttal of your other points :)
So now it's "standards" even though it hasn't been submitted, ratified or approved yet. And everyone else, if they dont want Google's stuff to work poorly in their browser, has to be a dog and follow Google's leash.
I consider Chromium some of the worst damage Google has done to the open web.
For me, currently, Chromium seems like nothing like a good thing. For example, their Linux sandboxing appears to be at least a step ahead of anything else so far.
If you're a user on a commercial system you didn't pay for (Google, Facebook, etc.) then you're not a customer, you're cattle. Your value is directly proportional to how much the company running the system knows about you.
I don't like where Facebook is going, and I think Google is following in their footsteps, albeit helped along by an excellent reputation for quality and fair play, especially amongst geeks.
Maybe I'm just being a curmudgeon, but I think Google is playing the same 'embrace and extend' card as Microsoft did back in the day, just for slightly different reasons.
I see this meme a lot, but I don't get it how the analogy is supposed to work.
There is actual evidence that Microsoft in the 90's was trying to sabotage standard protocols and open source software, e.g. http://en.wikipedia.org/wiki/Halloween_Documents.
The key part of "embrace, extend, and extinguish" strategy was extending the standard in proprietary ways, thus making it incompatible and no longer implementable via open source software, thus killing it.
I don't get how any of this applies to any web company, where nearly the entire business is based on the web and the standards that back it. It's no wonder that many of these companies contribute back to the web standards and open source software. Sure, these contributions are in the company's interests--but that's the whole point. We reached a time when it's in interests of many big (and small) corporations to contribute to open source and standards (including Microsoft!).
Some people see efforts to improve standards or contribute new ones as somehow bad, "embrace and extend". When actually it's the opposite: investing in the commons to promote its welfare.
Obligatory disclaimer: speaking for myself here, not any employer past or present.
If your platform is free-as-in-beer, you have to monetise your users to advertisers. You do this by learning more about them by keeping them within your ecosystem, not by allowing them access to your platform through open protocols.
I see it as a fundamental conflict between users of a system (you and me) and the customers (advertisers). Google has made it clear which side of that equation they care about. See e.g. their support of DRM in HTML.
And, seriously, "ignore RSS in Chromium" is now kowtowing to advertisers? How about the lack of gopher support[1]? And no built in bittorrent client[2]??
I'm starting to agree with others that you have a point somewhere in here but you're missing it over anger about Reader.
[1] https://code.google.com/p/chromium/issues/detail?id=11345
[2] https://code.google.com/p/chromium/issues/detail?id=182399
If I had to guess, I'd say that torrent support was nixed for fear of offending Big Content; Opera has already showed that it's reasonable for a browser to support it. Also there's already a plugin for that protocol, so it may just be a low priority for the team. Odd that they flagged the request 'invalid' though.
(Please stop telling me that I'm angry about Reader. It's not that I'm angry: I've identified what I think is a pattern in Google's behaviour, figured out what their end goal is, and it troubles me. So I'm abandoning their platform to the greatest extent practical.)
I think there is a clear argument for Google consolidating around APIs and their social network instead of federated protocols in the future. However, the whole "strategy to kill off RSS" thing is silly and undermines the other arguments you're making.
The bittorrent and gopher comments were facetious. It's not at all clear that all browsers should have a button that appears when a page has an RSS feed and, when pressed, opens a different web page to then enter the address of that RSS feed into your reader. Zawinski's Law was not meant as praise.
The lack of that RSS button is no more evidence of trying to kill RSS than the lack of gopher support is evidence of Google's plot to make sure that Gopher will never rise again like a phoenix and supplant the World Wide Web once and for all. Instead, you make sure extensions are able to build that button for those that want it (or put an option to enable it in about:config) and you call it a day.
Chrome has better developer tools. If your job is being a web dev and you purposely make your job harder because you're mad at Google for shutting down Reader, you're not being rational.
I do wonder though ... would you have described the formation of the FSF as a childish temper tantrum? I remember the days when to use Linux as a development OS was painful ... it worked out well in the end though :)
I don't use all of Google's products, but I use a subset because they get the job done well. If you think killing off reader was a bad idea, why not build your own and see how the cost/benefit ratio pays off. What problem are you even solving by doing this? You're just throwing a childish fit.
Why do you assume I'm angry about it?
FSF is not about open source or security: https://www.fsf.org/about/what-is-free-software
Also, calling something/someone "childish" is not a good way to make your point.
In that vein, boycotting Google is as much idealistic as boycotting closed software.
I ran Linux and did lots of development under it in the 90s. I quite enjoyed it and preferred it to Windows development at the time. I use Linux every day for work.
That doesn't mean I don't boot up Windows to play BioShock Infinite, even though I disagree with a lot of things Microsoft does.
In my experience Chrome is a PITA for web development due to its weirdly aggressive caching. I thought people were just making it up a few months back, but I experienced it recently and it's infuriating.
It's hard to nail down the difference between Chrome Dev Tools and Firebug with just one thing. For me it's not one killer feature it's a quality of life issue. It's all the little things that, IMHO, Chrome Dev Tools does right.
I have no problem using Firebug or even the Firefox Inspector when needed to actually find a Firefox specific problem but for working day in and day out, I prefer the experience of the Chrome Dev Tools.
No, of course they don't. They got rid of it because virtually no one used it.
As for Chrome, I think Webkit (or now Blink) is where web happens fastest. All new web experiments are done with -webkit, not -moz-, and you gotta go where the majority goes. In this case anyway. I haven't used gmail for a long time tho', because I didn't like that the content of my emails get used for ads - so I set up my own email server for personal usage. Other then that, maps, search .. it does what I need it to do so whether it tracks me or whatever is just the cost of the service.
... which is why we all still use Internet Explorer.
Uh... That happens to not be true. But WebKit does have much better (and better-funded) marketing.