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

We are pausing upcoming Chrome and Chrome OS releases

blog.chromium.org

Post reply on HN
Print view View original

71–79 of 79 posts

Re: We are pausing upcoming Chrome and Chrome OS releases

#71

Post by rovr138 »

retpirato wrote: post #41
LanceH wrote: post #39

Earlier quoted context omitted.

I updated a couple weeks ago and every tab was discarded when I tabbed away, reloaded when I tabbed back. It's better now. I can only imagine the problems that would cause for a school with a couple hundred of these checked out.

install session buddy from the chrome web store. it saves your tabs automatically, & even restores sessions containing a mix of tabs & web "apps" accordingly.

The only reason this is needed is because something was messed up with the core functionality. Same thing could happen with an API.

The focus on stability for now makes sense with a lot of people going remote.

Re: We are pausing upcoming Chrome and Chrome OS releases

#72

Post by JCharante »

jontro wrote: post #64

Google Play Store app publishing is delayed as well. Currently the message says: "Due to adjusted work schedules at this time, we are currently experiencing longer than usual review times. Please expect review times of 7 days or longer."

I wonder how this will impact educational apps that are trying to get last minute features for use in environments with a teacher. I know drops is trying to roll out an update at the moment.

Re: We are pausing upcoming Chrome and Chrome OS releases

#73

Post by throwGuardian »

munificent wrote: post #57
throwGuardian wrote: post #22

Remote work now is likely lower in productivity than normal-times WFH. If a software company cannot adjust to remote delivery, albeit at lower than normal productivity, the rest of the economy has no hope. I don't understand Google's decision here - I wish they simply predicted a longer than normal release cadence, versus none at all

> I don't understand Google's decision here - I wish they simply predicted a longer than normal release cadence, versus none at all It's reasonable to not understand their decision, but it's also reasonable to give them the benefit of the doubt that they know what's best for their team and product (and in that order). Googlers (like myself) are probably the least materially affected by COVID-19. We are well compensat…

> At the scale of shit the world is dealing with right now, it just doesn't matter.

There are different ways to cope with adversity. The "Keep calm and carry on" method is a contrasting formula, which applied to Chrome, would see maybe one release versus three or four, even in the midst of an adversity.

As much ubiquitous suffering as there is currently, the comfort of at least a (slower than usual) browser release can be a ray of hope in an otherwise bleak horizon. Heck, if my browser won't even update, forget fixing a massively multivariate system/problem like public health, or the economy.

Your/Google's self awareness of privilege is much appreciated. But if you really want to make a difference, a slower release cadence is much more uplifting than resigning to the virus.

Re: We are pausing upcoming Chrome and Chrome OS releases

#74

Post by EdwardDiego »

_nalply wrote: post #69
nixpulvis wrote: post #53

Earlier quoted context omitted.

2010?

> Guess the "decades run from 1 to 10, not 0 to 9" people won that argument. Like: the twenties run from 2021 to 2030, not from 2020 to 2029. Because the year after 1 BC is 1 AD. There is no year zero. This is one of the weird things of our calendar. More about that see Wikipedia: https://en.wikipedia.org/wiki/Year_zero . So, the first millennium is from 1 to 1000, the second from 1001 to 2000 and the third from 2001…

Not snarky at all - an attempt at an humorous aside. I thought about trying to tie it to Lua / Erlang / Julia coders vs. C / .NET / Java etc., but thought that a bit of a stretch. :)

Re: We are pausing upcoming Chrome and Chrome OS releases

#75

Post by Gaelan »

enneff wrote: post #31
LanceH wrote: post #30

Earlier quoted context omitted.

Local schools are leaning heavily on chromebooks. They have checked them out to students without computers. Adding an os update to this would contribute to the chaos.

OS updates on ChromeOS are seamless and mostly go unnoticed by the user, FWIW.

IIRC my school district (in WA state) pinned Chrome OS versions for a long time because the state standardized testing software required a specific Chrome version. Not sure off hand if that's still a problem.

Re: We are pausing upcoming Chrome and Chrome OS releases

#77

Post by exikyut »

eitally wrote: post #55
zeveb wrote: post #34

Earlier quoted context omitted.

> There are a lot of obstacles for temps/contractors to gain remote access at google. I thought that Google were all-in on BeyondCorp, which doesn't require a secure perimetre. Did they not actually convert everything, or is it still in progress? (edit: removed a non-constructive suggestion)

BeyondCorp gives you basic access to unprotected things on the network (intranet, google apps, etc), but not to secure systems, source code, etc.

Out of curiosity, how does that work? VPN? Remote desktop? Both?

Re: We are pausing upcoming Chrome and Chrome OS releases

#78

Post by kseifried »

enneff wrote: post #31
LanceH wrote: post #30

Earlier quoted context omitted.

Local schools are leaning heavily on chromebooks. They have checked them out to students without computers. Adding an os update to this would contribute to the chaos.

OS updates on ChromeOS are seamless and mostly go unnoticed by the user, FWIW.

Not everyone has access to a ton of bandwidth.

Re: We are pausing upcoming Chrome and Chrome OS releases

#79

Post by ThePowerOfFuet »

Gaelan wrote: post #75
enneff wrote: post #31

Earlier quoted context omitted.

OS updates on ChromeOS are seamless and mostly go unnoticed by the user, FWIW.

IIRC my school district (in WA state) pinned Chrome OS versions for a long time because the state standardized testing software required a specific Chrome version. Not sure off hand if that's still a problem.

>the state standardized testing software required a specific Chrome version

Sounds like that's the root cause of the issue.

Post reply on HN