The 3-year old "Implement RSS natively in Chrome" bug just changed to "WontFix"
code.google.com
code.google.com
Not this cryptic bullshit. It's like breaking up with someone by just never returning their calls.
(Which is fine by me. Chrome doesn't need to try to be everything to everybody. For that, there's the Mozilla SeaMonkey suite.)
This story seems like people jumping at another chance to further shame google on the Reader front, which is fine, but this seems like a somewhat dishonest opening for it, especially considering the directness of the closing comment.
Besides, there's a lot of web content that requires plugins and extensions to view properly. I don't see why that can't be the case here.
RSS is -- the essential concept was even included in the initial vision for the web:
>With help from Robert Cailliau, [Berners-Lee] published a more formal proposal (on 12 November 1990) to build a "Hypertext project" called "WorldWideWeb" (one word, also "W3") as a "web" of "hypertext documents" to be viewed by "browsers" using a client–server architecture.[4] This proposal estimated that a read-only web would be developed within three months and that it would take six months to achieve "the creation of new links and new material by readers, [so that] authorship becomes universal" as well as "the automatic notification of a reader when new material of interest to him/her has become available."
You've got lots of bookmarks. Much as browsers recently started downloading and displaying "favicons" (well, maybe not so recently, I'm an old timer), there is no reason a browser can't download the RSS feed from a site and compare the date of the most recent update to the latest date in the browsers history log. In other words if there's something new, its "bold" in my bookmarks and if not, its regular.
Now this is opt-in spamable, if you're running a journalist site or ecommerce, of course you doctor your sites feed to always appear new in someone's bookmarks even if its the same old recycled garbage. But there's more to the 'net than online stores and tabloid journalism.
Another novel user experience would be the trend of turning the "address/URL bar" into a search gateway bar. I think it fairly logical that if I use the "search" bar it should search and prioritize results from RSS feeds I subscribe to, below my own bookmarks and above generic web search results (aka google)
I don't think RSS is very interesting as "content" or an "app" but it could be pretty useful as metainformation.
Well, I can understand that it might not have been for everyone, but it was super convenient to be able to read RSS "folders" in Firefox. I'm a Chrome/Chromium fanboy these days--I use it on all of my devices--but I still miss that feature. If you don't want to use a certain functionality, it's easy to just avoid it; you can't ever use something that isn't implemented, though.
Clicking on a bookmark and seeing the most recent BBC headlines, for example, was awesome.
Some people want a random subset of news for entertainment. G+ is great for that. Here's a great big pile of recent stuff from everyone, a circle, or a community.
On the other hand, lets say I want to verify I read every story from certain sources (perhaps the BBC?) exactly, precisely once. I don't see a way in the G+ UI to "mark as read" or "only display unread" or whatever. Might exist or might be a weird way to hack it in, but its not intuitive.
For some reason option #1 is semi-popular among news readers, social networking, and old fashioned or online broadcasting, but option #2 is nearly universal among email clients and podcast clients. You'd never use an email client with a UI of "here's a random collection of some recent emails" with no way to tag them as read or deleted. I'd LOL at the idea of a podcast client with "here's a random cast that you may or may not have already heard"
Another horrible UI fail is time based. G+ can only do one linear "newest to oldest" sort. Even the dumbest RSS feed readers have some kind of tag/save/star feature. So you can skim the whole feed, star/save/tag good stuff for later detailed reading. Then once there is no "unread" left, start reading the star/save/tag stories in detail, perhaps much later. This "workflow" is impossible in G+ as near as I can tell.
Finally no one using the "RSS" workflow uses G+, so you get the chicken and the egg thing, where there's no demand for even the most primitive of workflow management in G+ because anyone wanting anything like that uses RSS. So the BBC is a bad example in that their social networking people are probably required to use both, but I suspect that 99% of my RSS feeds are not available in G+ because they self segregate by workflow. You'll need a bigger shock to the system than cancelling goog reader. I switched to newsblur once the crushing demand let up a bit. I'm not going to abandon everything I currently enjoy to watch cat videos on G+.
Another alternative on Windows is surprisingly IE. The user interface is actually similar to GR where you can read multIple feeds at once when you organIze them In folders. I used it before I switched to GR. It can also import/export OPML
Embrace, extend, extinguish.
Embrace, unembrace.
They have extinguished all the profits from the market as long as Reader existed.
Will that recommence? Perhaps, but there as a bit of the old Microsoft tactics at play here.
Which brings me to the next point: what market are you even talking about? There were never any profits in the RSS reader market. The only real market was one of interest by users, which Google Reader pretty legitimately competed in and still retained a large number of users (even if by "it's good enough to not bother switching").
There are still a ton of feed readers still around and still free (it's just consuming XML, after all). The ones that people are jumping to are the ones that have worked on their usability and are offering to take money to guarantee the feature that google didn't: storing feed history.
They're Google: the only sense they have to make is AdSense.
They didn't need to extend, because virtually everyone using RSS was using their reader.
In a way you could say they "extended" the readers, by providing a better one than existing ones. Better enough, that "nobody" cared to make a competitor, until it was clear it was going to die.
So yeah, it's close enough to embrace, extend, extinguish to me.
Not to mention, that we can not really say they extended the readers, because the extensions didn't make them incompatible and so prevented people from moving, like the EEE did.
I'm glad people are losing some misplaced trust in Google, but let's not blindingly apply labels to this.
Wait, what?
Can't say it's so in this case, but trust me it's the best way to be in some cases :-)
Cutting off comments make sense as well as there isn't going to be constructive discussion at this point. Constructive discussion has already been had and a decision was reached. Having comments open at this point just inviting people to grind their axes.
...there have never been any plans to implement this natively in Chrome.
I don't know why this bug has been left open for years, making it look as
if we're considering this, when we're not. It just gets people's hopes
up, and then makes them bitter when years go by with no action.
This about sums it up for me, and it's completely understandable.I mean... when something is widely displayed in the middle of a list of things that includes
* Gmail
* Google Docs
* Google Calendar
* Google Photos
* Google Search
and nothing else, then I would naively consider it to be roughly as "core" as the other things on the list. You wouldn't? Why not?
They've closed the threat containment phase (Reader) and are finally openly out to kill it.
1 ad per week on a RSS feed vs 1 ad per week on an entire website
and the answer would still turn out to be Ad Supported Websites. RSS users are an insanely small group compared to overall users on the web. So yeah, Google probably just decided that supporting RSS just isn't worth their money/time regardless of how it compares to its other services.
Virtually no content site puts its entire article into the RSS feed. They want to monetize with ads even more than Google wants them to. If RSS was a threat to anything it would be social news services like G+ which depend on a non-federated model to maintain their walled gardens.
https://play.google.com/store/apps/details?id=com.google.and....
So for those people who claim that Google doesn't care at all about RSS, Currents is certainly a counter-example.
And by the way, Google is a big enough company that to claim that a corporation as a whole as an opinion about any subject or any protocol is a little silly. Take for example, "IBM Loves Lotus Notes; therefore IBM must hate SMTP." Absurd. There is a part of IBM that make a lot of money off of Lotus Notes, yes. There are also lots of IBM engineers and former IBM engineers who hated it with a hot blazing passion. I'm aware of one IBM division which supplied its engineers with a Lotus Notes-free e-mail address because it was necessary for them to do their jobs. Specifically, interact with the open source community with a mail product that wouldn't destroy whitespace in patches....
I have no inside information, but from reading the proverbial tea leaves and following his career, I think Sundar Pichai might have a similar prerogative and management style with respect to shedding things that are "un-Googley" Particularly things that run locally & sync with their services, e.g. Google Gears, Goolge Desktop, now CalDAV, etc.
Oh, you mean, like everybody. Ok!
Accusations of an attempt to extinguish the RSS format probably can't be considered until they kill Feedburner, which constitutes a massive portion of the web and all RSS trafic.
I think it's sad. RSS is a lot more open than the alternative: Twitter.
Google seems to think that the result of an end to RSS will be good for them. Unless they are planning on buying twitter, I doubt it will be.
Even apps that make use of it will be moving away from the user being directly aware of it.
I've considered doing it as a stopgap, but it's just too laborious for sets of feeds numbering over 100, and will be inconsistent because some feeds will undoubtedly lack Twitter accounts.
Also posted as a tweet, because fuck being evil: https://twitter.com/martindale/status/313148391624417280
It's clear to me that the right approach is an extension specific to your preferred RSS reader. I understand that some browsers have an RSS reader built it, but that still doesn't make it a core feature that's going to be used by a big portion of their users.
1. have an indicator in the browser interface that an rss feed is available for the current page.
2. have a preview of rss feeds rather than unstyled xml. It is just a matter of adding style for some xml files the way shiira[1] first did or the way safari[2], opera[3] or firefox do.
It is clear to me that the second is nice for the user even if the chromium developpers do not intend to implement a full rss reader as it just consists in making some common web documents readable directly in the browser, it is far more logical for a web browser to display rss than to display pdf... The first point is said to distract the user and clutter the interface so I can understand why it should be an extension (firefox voluntarily suppressed this indicator a few years ago).
[1]: http://i1-news.softpedia-static.com/images/reviews/large/shi... [2]: http://media.arstechnica.com/images/tiger/safari-rss-big.jpg [3]: http://www.problogdesign.com/wp-content/uploads/2009/01/wind...
I'm also going to become less reliant on Google services because when they decide other open standards are less profitable than getting more eyeballs Google+ I don't want to be stuck like I am now.
I hope Opera continue to evolve their platform, WebKit engine or not. :/
Firefox is pretty much the polar opposite of Opera in terms of features, although I like their work on open standards like Opera's.
Can i get a source on this?
Not sure if they still do this, but Mozilla used to give new hires a little toy and say, "This is your million users; try not to abuse them too much." That concept is built-in to the culture there. Why take up space and memory for the 93% of users who don't use that feature, when an add-on can do just as good a job for the 7%?
It's just that companies like Facebook and Google are trying to lock in users on their own platforms.
Makes you wonder what is ahead for Blogger. It will probably be assimilated eventually.
Since only a minority of Chrome users are RSS users, it makes sense to have it as an extension. They're not stopping anyone from building one. So, hack away.
Firefox is basically at par with Chrome.
If your particular Firefox is slow, I suggest you reset your profile:
http://support.mozilla.org/en-US/kb/reset-firefox-easily-fix...
But Google is different. I swear. They don't even care about Wall Street. They said so.
It's like Google is operating without a head. It's turned vicious and acting offensively against a specific technology.
RSS will live on, of course. Amazing that Google is also so pompous.