Because, you know, "Best viewed in Chrome" is a thing, and somebody is becoming the new IE. It's saddening.
Why Is Google Blocking Inbox on Firefox?
71–80 of 217 posts
Re: Why Is Google Blocking Inbox on Firefox?
#72[deleted]
Re: Why Is Google Blocking Inbox on Firefox?
#73Earlier quoted context omitted.
When one can run Visual Studio on OSX/Linux...
That's not going to happen any time soon. Not because they don't want to but because the whole process would be monumentally complicated and expensive. I suspect we'll see a new 100% managed code IDE in the next 3-5 years that will fit this area nicely. It'll have bits of Visual Studio in it and it may even be called Visual Studio but it won't be what we have now.
Or may be ... soon ... http://www.geekwire.com/2014/net-visual-studio-microsoft-ope...
Re: Why Is Google Blocking Inbox on Firefox?
#74Google is not the same it wanted to be back in 2009 [1]: Today, we base our developer products on open standards because interoperability is a critical element of user choice. [1] http://googleblog.blogspot.com/2009/12/meaning-of-open.html
I think this slide explains everything about how Google has changed the way of handling their business. http://www.slideshare.net/ericschmidt/how-google-works-final... They are more focusing on managing their business which is limiting their contributions to open standards.
Which of the 54 slides?
Re: Why Is Google Blocking Inbox on Firefox?
#75Earlier quoted context omitted.
I disagree. They're short cuts you might take to get a product out and get early feedback, the same sort of shortcuts most of us have taken when pushed to release something sooner. This is a product in Beta, not the finish article. Even if everything work in theory just dropping multi-browser testing would save time. If their aim is a beta product for early user testing, I really don't think what they've done is unre…
You have to admit it seems a little shady when it comes from the browser vendor. It would be fine if the message said, "we haven't tested this, it might not work, YMMV". Instead, the message says, "click here to download our product", the implication being they'd like you to convert to only ever using their product.
I might agree with some things but not with e-mail, it's too important to most people say "hey this is probably OK but who knows".
And because of that there is the risk of reputational damage around one of their core products. Working in tech you understand what a Beta really means and you can make that call on an informed basis but that's not true of a typical G-mail user today.
Re: Why Is Google Blocking Inbox on Firefox?
#76Earlier quoted context omitted.
I don't think the issue is as much with the clients as it is with the spam filtering Google provides. The sheer volume of emails they handle allows them to have the best spam filtering in the world. Something, that will be very difficult to duplicate through OSS.
The issue is with sending mail. Running my own mail server just feels like a loosing proposition as inevitably it'll be blocked because it's not a well known one.
I've never had a problem. I have a VPS I use as a smart relay.
Re: Why Is Google Blocking Inbox on Firefox?
#77Earlier quoted context omitted.
I disagree. They're short cuts you might take to get a product out and get early feedback, the same sort of shortcuts most of us have taken when pushed to release something sooner. This is a product in Beta, not the finish article. Even if everything work in theory just dropping multi-browser testing would save time. If their aim is a beta product for early user testing, I really don't think what they've done is unre…
Getting a product out in the web development world includes getting it out for other browsers than the browser you develop in house. Otherwise, you won't get the early feedback you wanted. Especially when your application is working, with some minor glitches. It's not like the application is completely broken in Firefox with the fixes mentioned. Bypassing CSP for your own domains feels like a hack that you shouldn't…
Given how over subscribed the beta is I think they're getting feedback.
Remember with this sort of product the questions they have are "is this interesting?", "is this useful?", "do people like what this does?".
Can we get this running on Firefox simply isn't an interesting question to them - they know the answer, it's yes if they throw resource at it, but for a new product team with questions over whether this product should even exist that's not a priority.
Remember, this is Google who have a long history of canning this sort of project. If I were the company who produced Wave, I'd probably look at how I could reduce the cost and time to feedback for my next new thing too.
As an aside, I've tried Inbox and, to me at least, it's the next Wave, not the next Gmail.
Re: Why Is Google Blocking Inbox on Firefox?
#78A $400B company cannot get their app to work securely & performantly in Firefox, so they’re blocking access via UA sniffing. Seems legit.
Re: Why Is Google Blocking Inbox on Firefox?
#79Earlier quoted context omitted.
The issue is with sending mail. Running my own mail server just feels like a loosing proposition as inevitably it'll be blocked because it's not a well known one.
Certainly this is what will happen if everyone thinks the same way as you... (I have been my own SMTP server (hosted by OVH) for a few months now. I was blocked exactly once, by custom filtering from a small provider where the delivery status notification said to appeal to abuse@, I emailed them and they fixed it in minutes.)
Similar story. I couldn't email msn (or exchange, etc.) but there was a web form I could fill out. Annoying, but I got to have some fun describing the type of emails I sent to my "list" and its "unsubscribe process".
Re: Why Is Google Blocking Inbox on Firefox?
#80Earlier quoted context omitted.
Yes there is. It's the world wide web. An interoperable universal interaction standard. Or it was until Google started pulling an IE6 game. I use Firefox for everything because there is no central motivation to specialise. If a site doesn't work well, it doesn't get my business.
Well, yes, that'd be nice if we had a "interoperable universal interaction standard." But now the majority (and soon, almost everyone) will be using the internet on tiny personal computers (smartphones) that run native apps. Using a web browser will become less and less important or even relevant. In such a case the costs of optimizing for multiple run-times makes little sense. Really, abandoning the browser for nati…
I use gmail everyday on my phone and have not bothered with downloading its app. It is pointless as I get a good enough experience on the browser and I do not want to deal with updates.
And native apps are good for things like Microsoft Office or things you expect to use offline and frequently. But if you make me download an app for Facebook or gmail and get me to update it every now and then, I will get pretty annoyed.