News for hackers. Stuff that matters.
Re:Why Is Google Blocking Inbox on Firefox? by pilif on Friday November 14, 2014 @08:39AM (#8607016)
On the HN thread accompanying the release of Google Inbox, a (supposed) engineer working on Inbox was saying that the reason for the exclusion of Firefox was a performance issue with accessing sparse arrays with huge indexes.

Link to the post: https://news.ycombinator.com/item?id=8495498

Link to the bugzilla entry: https://bugzilla.mozilla.org/show_bug.cgi?id=1087963

Re:Why Is Google Blocking Inbox on Firefox? by diggan on Friday November 14, 2014 @08:44AM (#8607037)
Thanks a lot for that information! Will include it in the post when I get a chance.

The performance is kind of bad in Firefox but I'm not sure it justifies blocking the entire browser because of that. For a comparison, Google Photos is slow as hell in Firefox, but you could still use it if you want to.

Re:Why Is Google Blocking Inbox on Firefox? by freehunter on Friday November 14, 2014 @10:12AM (#8607441)
Google blocked Windows Phone from accessing Google Maps in the browser (both the desktop and mobile versions) with the claims that IE was unsupported, even though Google Maps UK worked just fine.

Google does have a history of blocking browsers they don't support, no matter how functional it may seem.

Re:Why Is Google Blocking Inbox on Firefox? by Touche on Friday November 14, 2014 @10:41AM (#8607609)
Yeah, they seem to use the whitelisting strategy for all of their properties. If something isn't QAed it doesn't get enabled. I suppose at that scale the support cost isn't worth the "let them use it in a degraded way" mantra most of the web community follows.
Re:Why Is Google Blocking Inbox on Firefox? by msandford on Friday November 14, 2014 @11:06AM (#8607785)
SUPPORT COST?! HA HA HA HA HA!

You can't get support out of Google at any price, unless you're an advertiser. But in that case, it's only help for your ads and nothing else.

You can't talk about "support cost" when it's zero.

Re:Why Is Google Blocking Inbox on Firefox? by sosborn on Friday November 14, 2014 @11:15AM (#8607833)
"Support cost" doesn't apply only to customer support.
Re:Why Is Google Blocking Inbox on Firefox? by pbhjpbhj on Friday November 14, 2014 @11:44AM (#8608041)
Go on, I'm interested - what extra cost do Google have if I use the same service in FF as I would otherwise have to switch over to Chrome to use; given that they say up front that other browsers aren't supported and that this is a beta so expected to be shonky.

What cost is there?

If I've switched UA string Google might not even be able to tell, without actively seeking out the information, that other browsers are using it - how then could that be an extra cost?

School me, please.

Re:Why Is Google Blocking Inbox on Firefox? by sosborn on Friday November 14, 2014 @12:18PM (#8608251)
It takes resources (mainly developer time) to ensure that an application is working properly on multiple browsers. If you read the article you can see that a simple UA string change does not fix the problem.
Re:Why Is Google Blocking Inbox on Firefox? by msandford on Friday November 14, 2014 @02:11PM (#8608904)
There's a big difference between "provided a degraded experience in non-Chrome browsers" and "actively blocking non-Chrome browsers by means more invasive than UA checking"

Remember, there isn't any kind of really legitimate API for 100% determining which browser you're running in. There's a lot of ad-hoc methods which usually work.

These folks spent extra effort to block it from even TRYING to run in FireFox.

How are the FireFox devs supposed to see the bad performance that they need to fix for Inbox to work right if they can't run it at all?

Re:Why Is Google Blocking Inbox on Firefox? by sosborn on Friday November 14, 2014 @04:04PM (#8609482)
There is also a big difference between "provided a degraded experience in non-Chrome browsers" and "you have to actively disable CSP (a global setting) for it to work in Firefox."

Also, with respect to performance, this comment in the article might shed some light:

"Also see Bugzilla entry. The use of spare arrays with huge indexes was a performance issue in Firefox. It's been fixed in Inbox and in FF but not shipped in FF yet. (https://bugzilla.mozilla.org/show_bug.cgi?id=1087963)"

Re:Why Is Google Blocking Inbox on Firefox? by pbhjpbhj on Friday November 14, 2014 @06:35PM (#8610186)
But we're specifically talking about not hobbling other browsers not supporting them - you (or whoever) said that there are still support costs even when a browser isn't being "supported" (ie enabled to operate with a site at a suitable level).
Re:Why Is Google Blocking Inbox on Firefox? by sosborn on Friday November 14, 2014 @11:41PM (#8610842)
Did you read the part in the article about CSP?
Re:Why Is Google Blocking Inbox on Firefox? by Touche on Sunday November 16, 2014 @11:33AM (#8614589)
Even if they don't support customers they still have to support internal customers (everyone that works for Google). I worked on a project recently that didn't support IE8. Nevertheless, the day after release there were a ton of emails from one particular office that the site didn't work. There was a bit of a panic, various theories thrown out (it's working for everyone else, why is it not working for this office, networking issues?). A couple of hours (and who knows how much money) was wasted in an all-hand-on-deck meeting to fix the issue before it was found out that this particular office had an IT department that only allowed XP+IE8 machines.

When you get bug reports from internal customers it's never "the site isn't working in Firefox 33 with all extensions turned off. It loads but is a little slow.". The bug report you get is simply "it isn't working, you get a blank page".

Answering those types of emails cost real money.

Re:Why Is Google Blocking Inbox on Firefox? by talkingstove on Friday November 14, 2014 @11:15AM (#8607834)
Support cost doesn't mean customer support.
Re:Why Is Google Blocking Inbox on Firefox? by ManFromUranus on Friday November 14, 2014 @11:29AM (#8607925)
This probably has more to do with undermining WP (which is competing with android in the low end phone market) than anything to do with browser support. They would block iOS too if they could, but they can't so that's why safari is 'supported'.
Re:Why Is Google Blocking Inbox on Firefox? by 72deluxe on Friday November 14, 2014 @10:42AM (#8607619)
Were there differences between the IE on mobile and desktop though?

I recall back in the IE5 days that IE on Mac was a significantly different beast than IE on Windows despite being named the same.

Re:Why Is Google Blocking Inbox on Firefox? by freehunter on Friday November 14, 2014 @03:26PM (#8609293)
The engine was supposedly exactly the same on WP7, on WP8 the entire browser is the same with the exception of the UI (obviously). Google Maps UK worked fine on both the mobile and desktop site views of IE on Windows Phone.
Re:Why Is Google Blocking Inbox on Firefox? by phpnode on Friday November 14, 2014 @09:24AM (#8607221)
If they'd supported Firefox from the start everyone would be slating them for "crippling" Firefox, or they would have had a poor user experience that would turn a non trivial percentage of early adopters off the entire product. They cannot win here, it was a bug in FF, it is now fixed, presumably they'll stop blocking when the fix is more widely available.
Re:Why Is Google Blocking Inbox on Firefox? by shadowmint on Friday November 14, 2014 @09:43AM (#8607315)
They could have made the effort to make this work on firefox from the start, but someone decided the effort wasnt worth it.

The 'would have been bad experience to new users' is a strawman arguement. Solution: dont release product until it works. Firefox is fast enough if you write code with it in mind.

...but hey, who cares about anything except chrome right? If someone visits play.google.com on an ipad and safari crashes screw them for not using android right?

Its Business Politics at play, not technical restrictions.

Re:Why Is Google Blocking Inbox on Firefox? by Tehnix on Friday November 14, 2014 @10:16AM (#8607478)
>The 'would have been bad experience to new users' is a strawman arguement. Solution: dont release product until it works

Not really. And here's a list of arguments why it's okay to focus on one browser (at least at first):

1) It's in beta, so you want to get it right before focusing on making it work everywhere

2) Developing for multiple browsers adds overhead to developers. I imagine they like to utilise some experimental webkit features, which are either not available in Firefox/gecko

3) Related to 2), they would add a lot of overhead making sure the UI and UX is the same, using multiple vendor prefixes and workarounds for other things.

And just to point out,

>dont release product until it works

is probably the worst advice ever to give to people. You want people to actually test your application. You can never catch all the edge cases that can/will happen, in your mind, and sometimes your assumptions are wrong. This is a pretty basic concept or Lean UX etc.

Re:Why Is Google Blocking Inbox on Firefox? by endemic on Friday November 14, 2014 @10:46AM (#8607641)
I'm sure it's different for large projects, but for my own work, if I wait until the app is "finished" (or at least in a workable state) before working on cross-browser compatibility, I hate my life and want to die. YMMV, but I find that working on compatibility from the start is the way to go. That said, if there indeed is a big performance bug in Firefox, that would totally be a valid reason not to support it (for now).
Re:Why Is Google Blocking Inbox on Firefox? by Touche on Friday November 14, 2014 @10:43AM (#8607621)
My counter is that "fix it later" never comes. Unless business sees browser support affecting the numbers they will not allocate the time to fix it. Some dedicated developers might fix it by working over time but that's essentially free labor. It has to take a strong engineering department to say "we will not ship until it works".
Re:Why Is Google Blocking Inbox on Firefox? by shadowmint on Friday November 14, 2014 @10:21PM (#8610727)
It's well documented that the technical debt you accumulate from prototyping and supporting only one platform is extremely significant; to the point where many people never go back and fix / rework / remake products.

If you plan to support cross platform, do so from the start.

You can argue about feature parity and 'first user experiences' all you like, but practically speaking, if you don't support the target platforms from the start, you're dooming yourself to FOREVER have 1st class and 2nd class platforms.

You see this all the time in apps; flagship on iOS, rubbish half implemented android version that launches 6 months later and never always gets updates 3-6 later, broken, with bugs. Or vice versa.

I'm not in any way saying that you should to be cross platform, or what platforms people should support. That's a business decision each business has to make. ...but it's not a technical decision. Technically, if you know what platforms you support from the start, you can implement the product with that in mind.

I've literally only ever heard this sort of ridiculous rhetoric from people who've never suffered through retroactively having to go back and support additional platforms. I dare say, business people who make decisions but don't have to actually deal with the consequences of them.

I honestly feel for the Inbox team. I'm sure there a lot of really tedious days ahead of backporting and bugfixing ahead for them (if google decides to make firefox support a thing).

Re:Why Is Google Blocking Inbox on Firefox? by Tehnix on Saturday November 15, 2014 @04:34AM (#8611293)
>It's well documented that the technical debt you accumulate from prototyping and supporting only one platform is extremely significant; to the point where many people never go back and fix / rework / remake products.

Maybe in GUI applications, but not so much in web browser applications.

>If you plan to support cross platform, do so from the start.

You are already close to automatically supporting all platforms. The point of "not supporting" a browser, is to avoid tedious and time consuming testing of said browser, because CSS and JS works differently in every browser (although close to the same in webkit browsers like chrome and safari).

>I've literally only ever heard this sort of ridiculous rhetoric from people who've never suffered through retroactively having to go back and support additional platforms.

Again, your arguments might apply to a OS application, but not to web browser "applications".

Generally, I also subscribe to the mindset of: make it right for one OS. Instead of: make it shit for all OSs, but usable.

Finally. Going out of your way to support platforms that _might_ be used, for an application that you don't really know if people will use in the first hand, is absolutely idiotic.

You need to know how, why and if people actually will use it, before spending time and money on supporting multiple platforms/browsers.

Just to finish of,

>I've literally only ever heard this sort of ridiculous rhetoric from people who've never suffered through...

I've literally only heard this from people that have never developed for multiple platforms, and expect that "once it works on X, it must work on Y". It just isn't so. Implementations, however neat, always differ in GUI-land.

Re:Why Is Google Blocking Inbox on Firefox? by shadowmint on Saturday November 15, 2014 @10:27AM (#8611826)
If you put 'applications' in 'quotes' when you refer to websites, we are so far from being on the same wavelength its not even worth continuing the discussion.

I can only recommend you seek additional input from your immediate peers before writing your next web 'application'.

(hint: the considerable negative feedback re inbox not working in firefox is the kind of bad press companies would rather avoid)

Re:Why Is Google Blocking Inbox on Firefox? by abraham on Friday November 14, 2014 @10:36AM (#8607574)
*experimental Blink features
Re:Why Is Google Blocking Inbox on Firefox? by TeMPOraL on Friday November 14, 2014 @10:22AM (#8607511)
> The 'would have been bad experience to new users' is a strawman arguement. Solution: dont release product until it works.

Except that almost no one does it nowdays. MVPs, early launches, etc. Why Google should be held to one standard while every "innovative startup" is held to a completely opposite?

By the way, did no one read what Google itself has to say about Inbox? It's explicitly stated as not a replacement for GMail. They're playing around with UX idea. You can look at it as a very elaborate A/B test.

Re:Why Is Google Blocking Inbox on Firefox? by aroberge on Friday November 14, 2014 @10:13AM (#8607454)
If it had worked in Firefox and Chrome, but not on Internet Explorer, what should they have done? Think about that...
Re:Why Is Google Blocking Inbox on Firefox? by andybak on Friday November 14, 2014 @10:15AM (#8607472)
> Its Business Politics at play

Or alternatively it's economics. Maybe someone, somewhere had to make a decision similar to "If we want a good experience that includes Firefox users from day 1 it will cost $x and delay launch by y weeks". And he had to sell that to his boss.

Even in a company as awash with money as Google, someone has to justify budget choices.

Re:Why Is Google Blocking Inbox on Firefox? by msabalau on Friday November 14, 2014 @10:20AM (#8607496)
I would have expected this sort of comment in most forums, but not necessarily in a community where many members actually deal and grapple with questions of "what platform gets supported when" and understand that "effort not worth it" is not the same thing as "business politics"

I believe many people know and understand that it's not unheard of for Google to release app updates on iOS a couple of weeks before the Android version comes out.

And while I've wanted to visit app stores cross platform to add items to a wish list while on the go, and been a little frustrated by not being able to do so, it does seem like a bit of an edge case. Although I suppose with both iTunes and Google Play edge cases can still be huge.

Re:Why Is Google Blocking Inbox on Firefox? by danielweber on Friday November 14, 2014 @10:05AM (#8607416)
This is an ancient lesson in software development. IIRC back in the early 1990s there was a beta build of Microsoft Office sent out to early adopters with full debugging turned on, and one of them wrote a newspaper review about how slow the new version was, despite the adopter being explicitly told it was a debug build and would be slower. "It's just to show off new features, not new speed."
Re:Why Is Google Blocking Inbox on Firefox? by akavel on Friday November 14, 2014 @09:30AM (#8607249)
In other words: performance is a feature. And thus, not wanting to ship a product with an important feature missing should be understandable.
Re:Why Is Google Blocking Inbox on Firefox? by louthy on Friday November 14, 2014 @09:41AM (#8607306)
Quite. Performance is definitely a feature of Google Inbox and it's very much appreciated. I think it's an excellent tool, and the rapidness of action responses is definitely a huge part of that.
Re:Why Is Google Blocking Inbox on Firefox? by res0nat0r on Friday November 14, 2014 @11:39AM (#8608000)
Don't say "blocking" (or maybe that is preferred since the tone of the post is to insinuate Google is being evil) and say "not supported yet" since the product is still in beta.
Re:Why Is Google Blocking Inbox on Firefox? by mikeash on Friday November 14, 2014 @11:48AM (#8608069)
To me, "not supported" means that no effort has been put into making it work and you can't expect any help, but also that no effort has been put into not making it work. If the only problem is performance, then "not supported" would imply that it can be used, but it will be slow and you shouldn't complain about it being slow because you're doing something to supported. If there's code explicitly added to make it not work on Firefox, then "blocking" is a perfectly good word to use.
Re:Why Is Google Blocking Inbox on Firefox? by dblohm7 on Friday November 14, 2014 @01:24PM (#8608611)
I'd also like to point out that, if you read the bugzilla bug, it was fixed on the same day that it was reported!

Nobody from Google bothered to file any bugs against Firefox; it wasn't until a Mozilla engineer saw the Google engineer's complaint on the HN thread that he filed it and fixed it himself!

Re:Why Is Google Blocking Inbox on Firefox? by iamchrisle on Friday November 14, 2014 @08:56AM (#8607088)
FWIW, Safari (webkit) is mostly working. IE is, unsurprisingly, a train wreck.
Re:Why Is Google Blocking Inbox on Firefox? by userbinator on Friday November 14, 2014 @10:58AM (#8607722)
performance issue with accessing sparse arrays with huge indexes

...what? Why would they need "sparse arrays with huge indexes" anyway? This sounds more like a problem with the developers doing something ridiculous, and not the browser. Maybe Chrome is faster at it, but that's like saying "compiler X has a performance issue with bubblesort."

More precisely, I'd like to see what exactly they're trying to do with this sort of code. Optimising "sparse arrays" sounds like matrix algebra and scientific computing, not an email client.

Re:Why Is Google Blocking Inbox on Firefox? by bzbarsky on Friday November 14, 2014 @01:47PM (#8608772)
It should be noted that the Inbox folks didn't bother to report the issue, and that once it was reported it was fixed within a few hours....