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,…
Google Inbox
441–450 of 472 posts
Re: Google Inbox
#442Re: Google Inbox
#443Re: Google Inbox
#444Earlier quoted context omitted.
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…
(SpiderMonkey engineer here) What VerGreeneyes says is true for our JS engine, too: you can always file bugs in our bugzilla (in the "Core/ JavaScript Engine" component). We react to such bugs very promptly (as you can see in bug 1087963[0] which was fixed six hours after being filed) and, in many cases, can uplift patches from Nightly to Aurora and maybe Beta, so they'll reach release builds more quickly. If for som…
I'll make sure we file bugs as repro-case-able issues come up, but if we get stuck on a deeper mystery, we may need some more direct help. We've made a lot of progress, and from a logic and speed issue, a lot has been resolved and mostly working, but animations are janky, and from "subjective" speed point of view, it unfairly makes FF look bad. Based on previous experience with Chrome, hitting the sweet spot of 60fps is usually where the JS developers need help from the rendering engine folks.
Re: Google Inbox
#445Earlier quoted context omitted.
I did that. It was remembering to switch the account when composing new messages. I ended up sending work emails from my personal account on a few occasions.
I meant going to Accounts and choosing the "Reply from... radio". That way it will always choose the "destination email" as reply.
Re: Google Inbox
#446Earlier quoted context omitted.
(SpiderMonkey engineer here) What VerGreeneyes says is true for our JS engine, too: you can always file bugs in our bugzilla (in the "Core/ JavaScript Engine" component). We react to such bugs very promptly (as you can see in bug 1087963[0] which was fixed six hours after being filed) and, in many cases, can uplift patches from Nightly to Aurora and maybe Beta, so they'll reach release builds more quickly. If for som…
Thanks for the info. I'll make sure we file bugs as repro-case-able issues come up, but if we get stuck on a deeper mystery, we may need some more direct help. We've made a lot of progress, and from a logic and speed issue, a lot has been resolved and mostly working, but animations are janky, and from "subjective" speed point of view, it unfairly makes FF look bad. Based on previous experience with Chrome, hitting th…
Re: Google Inbox
#447I'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 hate Bundles. I rarely if ever have more than 5 emails in my inbox. Hiding things from me is counterproductive.
#. WAY too bright and big. Regular gmail fits 3x as much information in the same space, and I was already unhappy with how bright and big regular gmail is.
#. Love snooze. I've been using boomerang for ages.
#. No idea where the compose-suggestions are coming from; they're for people I haven't communicated with since before gmail even came out.
#. In general, just feels very clunky compared to Gmail.
Re: Google Inbox
#448Meta note: That is one of the smoothest and pleasant scrolling experiences I've had on the web! Kudos to the web devs!
It's funny, because for me the scrolling on their page ( https://www.google.com/inbox/ ) doesn't work at all, on Safari 8.0/OSX.
Re: Google Inbox
#449Earlier quoted context omitted.
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