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

Google Inbox

googleblog.blogspot.com

Post reply on HN
Print view View original

421–430 of 472 posts

Re: Google Inbox

#421

Post by LukeB_UK »

MCRed wrote: post #268

New Rule: I'm officially done with artificially segregating people into "cool people" who have an invite and the rest of us who have to get in line. Simple was the worst offender-- I should have known with the multi-year wait, to be capped off by bigoted comments from a cofounder to me on twitter (about an unrelated matter. But hey, your CxO makes a bigoted comment- I'm no longer your customer!) But it's not just Sim…

It's pretty much a standard thing. It allows them to test it as it scales up and iron out any issues.

Re: Google Inbox

#422

Post by bzbarsky »

cromwellian wrote: post #317
jgon wrote: post #310

Earlier quoted context omitted.

What an incredibly disingenuous reply. Chrome is truly this decade's IE, and watching Google try to play this kind of crap off would be disappointing if it wasn't so insulting. "There's no intent to exclude Firefox", it just turns out you've done that for like 2 major product releases in a row along with a giant flashing button suggesting that the user downloads Chrome. I'm not stupid, you don't have to lie to my fac…

I take offense to someone calling me a liar. Try typing this into a JS Console: var xx = []; xx[30000000]=42; var yy = xx.slice(0); It took almost a week to track down this problem where FF was taking 13 seconds to startup. We've spent a lot of time working on this and it is always in the cards to support this on all the other browsers. We've fixed tons of bugs and have gotten closer to it working the way it should,…

Unfortunately, V8 implements slice() fast at the expense of correctness. A basic edge-case testcase like https://bug1087963.bugzilla.mozilla.org/attachment.cgi?id=85... fails.

That said, it's clearly possible to do this fast _and_ correctly (e.g. IE manages this).

But as a note, some V8 folks would like to remove the buggy-but-fast thing completely. See https://code.google.com/p/v8/issues/detail?id=3612#c2

Re: Google Inbox

#423

Post by crazygringo »

veidr wrote: post #293
GuiA wrote: post #19

Congrats to Google on shipping! Side question: am I the only person fully satisfied by my email workflow? I practice inbox 0- if an email is in my inbox, it means something needs to be done about it (whether it's replying, filing a bug report, writing a patch, etc). Once it's done, it gets archived. I star the stuff that I'll need to refer to later, like tickets for a flight or concert. I then have a few server side…

Nope you are not alone. IMAP (despite being a technical mess behind the scenes) is my favorite computer technology of all time and has benefitted my life immensely. I would rather have today's email and no modern web than the reverse. I don't do inbox zero, I do inbox 50k. I just let mail pile up--why not? It only stresses you out if you let it (I don't). Even with a million messages, it's instantly searchable with a…

I agree and am mostly the same.

The only thing I also do is intentionally leave e-mails I still need to respond to, as unread, and keep my inbox sorted with unread e-mails at the top.

It works great. The only thing that annoys me is that most (?) e-mail clients automatically mark an e-mail as read as soon as it's opened. I'm constantly pressing "Cmd+U" in Gmail to go back to the inbox, while leaving the item as unread.

Re: Google Inbox

#424

Post by tedmielczarek »

cromwellian wrote: post #317
jgon wrote: post #310

Earlier quoted context omitted.

What an incredibly disingenuous reply. Chrome is truly this decade's IE, and watching Google try to play this kind of crap off would be disappointing if it wasn't so insulting. "There's no intent to exclude Firefox", it just turns out you've done that for like 2 major product releases in a row along with a giant flashing button suggesting that the user downloads Chrome. I'm not stupid, you don't have to lie to my fac…

I take offense to someone calling me a liar. Try typing this into a JS Console: var xx = []; xx[30000000]=42; var yy = xx.slice(0); It took almost a week to track down this problem where FF was taking 13 seconds to startup. We've spent a lot of time working on this and it is always in the cards to support this on all the other browsers. We've fixed tons of bugs and have gotten closer to it working the way it should,…

I can sympathize with you because cross-browser development can be frustrating at times. However, when you ship a product and only support one browser (which happens to be the browser your company makes) you're making a statement (even if it's only implicit) that you don't really care about the open web. You personally may care about the open web, and I'm glad the issue is fixed internally, but releasing a major web application with support for only one web browser is a big "fuck you" to the web.

Re: Google Inbox

#425

Post by cromwellian »

bzbarsky wrote: post #422
cromwellian wrote: post #317

Earlier quoted context omitted.

I take offense to someone calling me a liar. Try typing this into a JS Console: var xx = []; xx[30000000]=42; var yy = xx.slice(0); It took almost a week to track down this problem where FF was taking 13 seconds to startup. We've spent a lot of time working on this and it is always in the cards to support this on all the other browsers. We've fixed tons of bugs and have gotten closer to it working the way it should,…

Unfortunately, V8 implements slice() fast at the expense of correctness. A basic edge-case testcase like https://bug1087963.bugzilla.mozilla.org/attachment.cgi?id=85... fails. That said, it's clearly possible to do this fast _and_ correctly (e.g. IE manages this). But as a note, some V8 folks would like to remove the buggy-but-fast thing completely. See https://code.google.com/p/v8/issues/detail?id=3612#c2

Thanks Mozilla for the quick reaction. We were not really blocked on this as a for-in/Object.getOwnPropertyNames loop is an easy workaround, it's more that finding the cause of an unexplained slow down took a bit of time (the usage comes from another engineer's rpc-serialization library)

Is there a point of contact for rendering/paint performance issues? We've had problems in Chrome where we had to work around excessive invalidation/paints, but those were diagnosed by using Chrome's layer/paint debugging tools and talking to Blink engineers, things may go quicker if when we encounter problems, there's someone we can email for help or a fix.

Re: Google Inbox

#426

Post by VerGreeneyes »

cromwellian wrote: post #425
bzbarsky wrote: post #422

Earlier quoted context omitted.

Unfortunately, V8 implements slice() fast at the expense of correctness. A basic edge-case testcase like https://bug1087963.bugzilla.mozilla.org/attachment.cgi?id=85... fails. That said, it's clearly possible to do this fast _and_ correctly (e.g. IE manages this). But as a note, some V8 folks would like to remove the buggy-but-fast thing completely. See https://code.google.com/p/v8/issues/detail?id=3612#c2

Thanks Mozilla for the quick reaction. We were not really blocked on this as a for-in/Object.getOwnPropertyNames loop is an easy workaround, it's more that finding the cause of an unexplained slow down took a bit of time (the usage comes from another engineer's rpc-serialization library) Is there a point of contact for rendering/paint performance issues? We've had problems in Chrome where we had to work around excess…

If you just file a bug on Bugzilla (https://bugzilla.mozilla.org/) in the Core: Graphics component with a reproducible testcase that will probably get people looking at it pretty quickly. For more one-on-one contact I'd suggest the #gfx channel on the Mozilla IRC, although that tends to work best if you know who to reach out to specifically. The gfx newsgroup (https://groups.google.com/forum/#!forum/mozilla.dev.tech.gfx) might also work to call attention to a particular issue. You can probably setup an e-mail contact through one of those channels if that's what you prefer.

Re: Google Inbox

#427

Post by ryanpardieck »

Lewisham wrote: post #153

I've been using Inbox at El Goog for a while now, and I am happy to answer questions (in between dealing with a newborn...) FWIW, I really like it, and use it exclusively for my work and personal accounts. Inbox functions very much more like a ToDo list than it does an email client. Here are the workflows I have: Work: I filter all mailing lists into different clusters that I have appear at 7AM every morning. I then…

"Inbox functions very much more like a ToDo list than it does an email client."

That's exciting to hear, since I've recently started turning Mailbox into a combination email client/to-do list/evernote replacement. I've found that having all those concerns in different apps meant that I never wound up using any of them often enough.

The shared concern seems to be the triaging of things that hit an "inbox" of sorts. Email hits the literal inbox, to do's hit my "stuff I need to do" buffer, and notes hit my "categorize these notes later" buffer (I compulsively note things down for later). Ultimately triaging things as their hit the Mailbox inbox is most effective for me, so I've turned it into my single source of triaging.

I'll definitely give this a shot if/when I ever get an invite ...

Re: Google Inbox

#428

Post by superglu »

kulkarnic wrote: post #327
Lewisham wrote: post #153

I've been using Inbox at El Goog for a while now, and I am happy to answer questions (in between dealing with a newborn...) FWIW, I really like it, and use it exclusively for my work and personal accounts. Inbox functions very much more like a ToDo list than it does an email client. Here are the workflows I have: Work: I filter all mailing lists into different clusters that I have appear at 7AM every morning. I then…

I wrote a review of the Inbox on facebook (that was my deal with the person that invited me). Cross-posting here if it interests you. My review of Google's new Inbox, based on two hours of use (thanks [redacted] for the invite). First the good parts: 1. I really like bundles. The idea that I can "Sweep" all the promotional emails I get in one click fills me with glee (and marketers with anxiety, I imagine). It's also…

I'd appreciate an invite as well. gary.x.lu@gmail.com

Re: Google Inbox

#429

Post by bnchrch »

kulkarnic wrote: post #327
Lewisham wrote: post #153

I've been using Inbox at El Goog for a while now, and I am happy to answer questions (in between dealing with a newborn...) FWIW, I really like it, and use it exclusively for my work and personal accounts. Inbox functions very much more like a ToDo list than it does an email client. Here are the workflows I have: Work: I filter all mailing lists into different clusters that I have appear at 7AM every morning. I then…

I wrote a review of the Inbox on facebook (that was my deal with the person that invited me). Cross-posting here if it interests you. My review of Google's new Inbox, based on two hours of use (thanks [redacted] for the invite). First the good parts: 1. I really like bundles. The idea that I can "Sweep" all the promotional emails I get in one click fills me with glee (and marketers with anxiety, I imagine). It's also…

if any invites are going out I'd be happy to take one juice.is.good@gmail.com

Re: Google Inbox

#430

Post by eitally »

mathattack wrote: post #413
Lewisham wrote: post #153

I've been using Inbox at El Goog for a while now, and I am happy to answer questions (in between dealing with a newborn...) FWIW, I really like it, and use it exclusively for my work and personal accounts. Inbox functions very much more like a ToDo list than it does an email client. Here are the workflows I have: Work: I filter all mailing lists into different clusters that I have appear at 7AM every morning. I then…

"Inbox functions very much more like a ToDo list than it does an email client." This is very important. I've started using Evernote, and thought, "I really want to keep track of what gets done and who is doing what via email, without adding any complexity or forcing others into a system." I hope Inbox does this for me.

It won't. It's not a shared task system (Trello/GQueues/etc).
Post reply on HN