Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We don't have official RSS feed support for now, but we're working on a solution

developer.chrome.com

Post reply on HN
Print view View original

231–240 of 253 posts

Re: We don't have official RSS feed support for now, but we're working on a solution

#231

Post by freedomben »

lapcat wrote: post #209
listmaking wrote: post #204

Earlier quoted context omitted.

The freeze "until after the new year" is just the end-of-year freeze to avoid production breakage when a lot of people are on vacation: it's an extension of the principle of not deploying on Friday evenings / weekends; lots of companies have such a freeze. Once you've decided a couple of months earlier to do a migration, doing it "before the freeze" is also a natural deadline to pick, for migrating to the new infrast…

> The freeze "until after the new year" is just the end-of-year freeze to avoid production breakage when a lot of people are on vacation There was production breakage! The RSS feeds broke. That's the entire point of this HN submission and discussion. > Once you've decided a couple of months earlier to do a migration, doing it "before the freeze" is also a natural deadline to pick, for migrating to the new infrastruct…

I don't really disagree with you, but I've been on the other end of this before and there was a major incentive to get it in before the break: all the context in our heads.

If we waited several weeks until after the christmas break, we'd lose a lot of mental context. It's also a horrible dark cloud hanging over your head. When dealing with a big migration, it's really ideal to do it while everything is still fresh. Context switching can be very expensive

Re: We don't have official RSS feed support for now, but we're working on a solution

#232

Post by reddalo »

SanjayMehta wrote: post #16
reddalo wrote: post #10

People don't understand how much RSS is useful... I'm still angry at Google for killing Reader. It was the best way to consume content on the web.

NetNewsWire on ios+macos+icloud for sync That’s the best solution if you’re on Apple.

I love NetNewsWire on my Mac, but I also use Linux and Android, so I'd love if there was something as perfect as NetNewsWire on those platforms!

Re: We don't have official RSS feed support for now, but we're working on a solution

#233

Post by listmaking »

lapcat wrote: post #209
listmaking wrote: post #204

Earlier quoted context omitted.

The freeze "until after the new year" is just the end-of-year freeze to avoid production breakage when a lot of people are on vacation: it's an extension of the principle of not deploying on Friday evenings / weekends; lots of companies have such a freeze. Once you've decided a couple of months earlier to do a migration, doing it "before the freeze" is also a natural deadline to pick, for migrating to the new infrast…

> The freeze "until after the new year" is just the end-of-year freeze to avoid production breakage when a lot of people are on vacation There was production breakage! The RSS feeds broke. That's the entire point of this HN submission and discussion. > Once you've decided a couple of months earlier to do a migration, doing it "before the freeze" is also a natural deadline to pick, for migrating to the new infrastruct…

Sorry that this conversation is going in circles. At first, I was talking about the culture of migrating to a new system when it supports ~75% of the features (by importance) of the old, rather than closer to 100%. I would find it reasonable for some team to judge that RSS support is not in the crucial 75% (and its lack would not constitute production breakage); clearly you disagree. That's fine.

As for the rest, I was just explaining the general idea of a production freeze. If you're going to stop trying to make changes by a certain date "to be safe"; then that's the freeze date. Equivalently: people keep trying (and sometimes rushing) to do things until the actual freeze date. The date is early enough (quite a bit earlier than Dec 24) so that there's still enough time and people left to fix things or roll back, if there are genuine emergencies. This replaces the risk of production breakage with the risk of embarrassment/questions from asking for approval for an emergency fix during the freeze period, so people will still only do things they're fairly confident will be safe. Anyway, none of this is relevant unless lack of RSS support is considered a production breakage, which is the very point of disagreement here.

Sorry about the "few weeks / months" comment; I was editing it out while you were posting your comment. But yes, when deciding whether something is a blocker, it's safer to assume that it can take indefinitely long (until it actually exists), even if you think (or have been promised) that it will be quick. It's the difference between taking the mean versus the 95th percentile of the distribution of time estimates.

Re: We don't have official RSS feed support for now, but we're working on a solution

#234

Post by freedomben »

walls wrote: post #219
kinlan wrote: post #206

Earlier quoted context omitted.

We don't do Christmas bonuses...

Sorry, how about: 'Needed this to be done for my year end review' instead?

The extreme cynicism really surprises me. The dude is here participating directly in the convo and giving super straight-forward answers! If that doesn't already seem like a good enough reason to be reasonable, then perhaps remember that you're talking to/about an actual human, not just a randomly generated text string

Re: We don't have official RSS feed support for now, but we're working on a solution

#235

Post by smusamashah »

al_borland wrote: post #198
smusamashah wrote: post #118

When chrome started taking over, all other major browsers (probably even internet explorer) had native RSS read support (read at least). They use to show rss icon in the url bar or some other indictor that this site has RSS available. But Chrome ever since has been throwing raw xml at you when you try to open an rss feed link and never indicates if there is RSS here. I believe this to be the main reason for decline o…

I have to wonder if it just never caught on with the mainstream as average users didn't really get it? Apple went so far as to name a release of their browser, "Safari RSS" [1]. Even with this level of focus from Apple, I never really heard anyone talk about it or start using it. Those who already used RSS had better readers, and those who didn't use RSS never really saw the value with this implementation. [1] https:…

Having an RSS indicator in the URL bar used to be the first step to subscribing a feed. How do you get it if its not there. When a feature is removed, slowly everyone will forget that it was even a thing once.

Opera (my main browser back then) use to have so much stuff built in (RSS, email, IRC, note taking, mouse gestures). Chrome use to have a resizable extension bar recently. OneNote use to have a more colorful and compact UI. Start menu and taskbar used to be useful before windows 11/10/8.

Reminds of an article posted here about removing less used keys/letters from keyboard. https://www.marginalia.nu/log/48-i-have-no-capslock/

Re: We don't have official RSS feed support for now, but we're working on a solution

#236

Post by BHSPitMonkey »

thatoneguy wrote: post #228
culi wrote: post #165

Earlier quoted context omitted.

when roughly would you place the "old Google" turning point?

I quit in 2015 because the place was becoming like any other big company and I’d already been there for a decade. Larry becoming CEO in 2011 again probably started it…once he took the helm, Google soon got really concerned about expenses, likely because his net worth was tied to pleasing Wall Street. CFO Pichette left and bean-counting CFO Porat got hired who came from Morgan Stanley with a mandate to cut expenses. A…

Are you saying Reader was killed to funnel people into Google+?

Re: We don't have official RSS feed support for now, but we're working on a solution

#237

Post by walls »

freedomben wrote: post #234
walls wrote: post #219

Earlier quoted context omitted.

Sorry, how about: 'Needed this to be done for my year end review' instead?

The extreme cynicism really surprises me. The dude is here participating directly in the convo and giving super straight-forward answers! If that doesn't already seem like a good enough reason to be reasonable, then perhaps remember that you're talking to/about an actual human, not just a randomly generated text string

It's a person likely making $500k+/year for a two trillion dollar company. They absolutely could have waited, but this individual personally prioritized their year end goals over a feature that many things/people depend on.

Their participation in the thread complaining about it doesn't make it any less egregious.

Re: We don't have official RSS feed support for now, but we're working on a solution

#238

Post by 0cf8612b2e1e »

b112 wrote: post #160
TazeTSchnitzel wrote: post #141

Earlier quoted context omitted.

And since then, the other browsers have removed their native RSS/Atom feed support. Firefox and Safari both used to have it and have since removed it. Visiting an RSS feed in Safari now shows you a page that resembles a 404, telling you that Safari no longer supports feeds.

Yup. For firefox, having features that chrome doesn't, seems silly to them. It's not like they need market share or anything! Just remove fully functional, mature and feature complete code, cause why not? No FTP, RSS, etc.

FTP is the one that really annoys me. It was a minimal implementation which would let me download a few ad hoc files as required. Now I have to launch a separate program every time.

At least with RSS, I can manually parse the XML in a pinch.

Re: We don't have official RSS feed support for now, but we're working on a solution

#239

Post by lapcat »

listmaking wrote: post #233
lapcat wrote: post #209

Earlier quoted context omitted.

> The freeze "until after the new year" is just the end-of-year freeze to avoid production breakage when a lot of people are on vacation There was production breakage! The RSS feeds broke. That's the entire point of this HN submission and discussion. > Once you've decided a couple of months earlier to do a migration, doing it "before the freeze" is also a natural deadline to pick, for migrating to the new infrastruct…

Sorry that this conversation is going in circles. At first, I was talking about the culture of migrating to a new system when it supports ~75% of the features (by importance) of the old, rather than closer to 100%. I would find it reasonable for some team to judge that RSS support is not in the crucial 75% (and its lack would not constitute production breakage); clearly you disagree. That's fine. As for the rest, I w…

> its lack would not constitute production breakage

Of course it's production breakage. You can't redefine it to not be "production" breakage just because you make a distinction between essential and non-essential features to pull the trigger on the migration. If the migration only supports 75% of the previous features, then 25% of the previous features are broken in production after the migration. If you're ok with that, then ok, but let's not pretend there's no production breakage. The RSS feeds were in production, and then they broke. That's production breakage. What else would you call it?

> As for the rest, I was just explaining the general idea of a production freeze.

I don't need that explained.

> Anyway, none of this is relevant unless lack of RSS support is considered a production breakage, which is the very point of disagreement here.

I think you're the only one who doesn't think RSS support isn't production breakage. Otherwise, Google wouldn't be "actively working on a solution."

Re: We don't have official RSS feed support for now, but we're working on a solution

#240

Post by Taurenking »

JohnTHaller wrote: post #213
listmaking wrote: post #153

This is hilarious big-company shit, that engineer on Chrome devrel team finds it easier to actually just write his own unofficial RSS feed-generator and make it public [1] — the feed for this blog is at [2] — than for the "Internal issues have been filed with the DevSite team" to get worked on [3]. And who knows when this will rise to a priority for that team? In the old Google, it would have been easier for anyone t…

Not sure how old 'old Google' was. There was a bug in the Contacts web app where the states were out of order. They were ordered by 2 digit state ID but shown as state name. A simple order by mixup in SQL. This meant users in New York couldn't tab to the state and start typing the state name to get the state. It was a filed bug. Known by people within Google who wanted it fixed. It was finally fixed this year after n…

[dead]
Post reply on HN