3 ms·
But WebRTC makes use of WebM and WebP is really starting to get huge. And then there's all the other techs I already mentioned. About Chrome Apps, you really
by patrickaljord 13y ago
But WebRTC makes use of WebM and WebP is really starting to get huge. And then there's all the other techs I already mentioned.
About Chrome Apps, you really don't know what you're talking about as Jess Austin just demonstrated https://news.ycombinator.com/item?id=6021899 https://news.ycombinator.com/item?id=6021899
Most Firefox contributors are paid employees thanks to Google's money. It doesn't happen for free. Of course dollars matter. Plus, Chromium is open source too and Chrome gets unpaid contributions too.
> And, as for the open web, Mozilla is the only one fighting for it on mobile via Firefox OS
So is Google. Who was the first huge company to release a 100% web centered OS? Google Chrome OS. They also ported Chrome to Android but right now, the web is just too slow compared to native (and it's going to last http://sealedabstract.com/rants/why-mobile-web-apps-are-slow/ http://sealedabstract.com/rants/why-mobile-web-apps-are-slow...) so it doesn't stand a chance. Look at how ridiculously slow FirefoxOS apps are. Google is realistic enough not to do the same mistake but still, they ported Chrome to Android and it supports all the things that FirefoxOS does plus AOSP is open source so it shows that Google actually care about openness even when the web is not a good fit. Oh, and any idea what FirefoxOS uses as a base? Yep, Google's Android.
- JohnTHaller 13y agoWebP is huge in apps but not on the open web due to lack of support. It saves Facebook a lot of bandwidth in their native app, though. WebM could have been swapped out for MPEG in WebRTC. It would actually be better due to hardware support. Chrome apps are still web apps packaged for a single browser in a proprietary app store. It's not the open web. You do realize there are a ton of Firefox contributors that don't work for Mozilla, right? And, for the third time, Google is paying Mozilla for a service that Google makes a TON of money on. It's not charity as you seem to keep implying. Without Mozilla, Google wouldn't be where it is today. And vice versa. But you seem to only harp on the latter. You mean the other techs I already acknowledged but you continue to harp on? On speed, Firefox OS isn't bad for a 1.0 on middling hardware. It'll get faster (remember, Android was a DOG in its initial released on the TMobile G1, which I still have sitting on my desk). And ASM.js will make things interesting, too (and is far more open than Google's native code in the browser attempt). And the article you mentioned is talking about mobile Safari mostly which, don't forget, is completely gimped for packaged web apps on iOS due to Apple's anti-competitive 'you can't use the faster Javascript engine' stance for everything except Safari. Google Chrome OS is a web-centered OS but it's not an open web OS like Firefox OS is. It supports Chrome apps but it don't think they have any plans to support other ones. It's also funny that you mention Chrome OS and that the web is too slow in the next sentence. Firefox OS uses the Android internals as a base, which is in turn built on top of Linux. I'm aware of all of that as I've tested it. And I have an Android phone. I think I'm missing your point here as it's unrelated to what we're discussing. In the end, I have a lot of respect for Google and the contributions they've made. I think they can be a force for good when they want to. And, honestly, I'd love the chance to work at a company like that. But let's keep a balanced eye on their motivations and contributions compared to Mozilla. You make it sound like Google has done everything and Mozilla nothing. I get that you're a Google fan. I am, too. But I'm also a fan of Mozilla and their commitment to openness and a level playing field for everybody.