We and Mozilla are working together to make the web awesome(plus.google.com) |
We and Mozilla are working together to make the web awesome(plus.google.com) |
Also, Google is a lot better off having an ally in Mozilla. Not so much because they don't want Bing to get a lot of users, but because together with Mozilla they have over 50% of the browser market share, and since the whole total of that market share includes very modern browser versions(Chrome always on latest version, Firefox not too far behind with the old ones), Google and Mozilla can pretty much dictate where the web is going now. I wouldn't be surprised if for those $300 million they also got Mozilla to accept using Native Client in Firefox later on. I think this part of the partnership matters more than just stopping Bing from becoming the default search on Firefox.
If you're suggesting that Mozilla would do something bad for the web for money, then I think you couldn't be more wrong. Mozilla is a nonprofit exactly for this reason.
(Worth noting that the for-profit Opera opposes Native Client too - it isn't just nonprofits that have values.)
Imagine how much easier it will be in the future when ever very intensive programs can be written, and run, on the web.
I think...
Chrome is an extension of that effort and has played a large part in driving adoption of new web technology.
But I don't buy the part about Google not being as interested in having users. Chrome is the operating system that runs the Google applications. They have increased their marketing spend this year by 69% to $4.9 billion dollars.
Google, marketing, something they never used to do and were known for not spending on. A lot of that marketing is for the chrome brand. The reason so many average PC users know about chrome is because of the market. They even hired Lady Gaga to do a Chrome ad, and I don't think they would go to the trouble of doing that if they were not interested in attracting users.
It is ok that Google want users for Chrome - nothing wrong with it. They have done so much to help users and the web with their investment in browser technology that there is no shame in marketing the product and wanting the world to use it.
Chrome advances the web. It does this because it's damn good. It's forced others to be good. None of this has anything to do with the point being made in the OP he's responding to.
Everything between the user and the monetization mechanism (advertisement) is strategic to Google. To believe otherwise is to be delusional. It's like the people who thought they could partner with Microsoft in the 90s and it'd be good for them.
I can see why a guy on the Chrome UI team would dismiss a valid business strategy of hedging against the IE + Firefox user-base that uses the search bar and address bar for 100% of their searches (vs. going to http://www.google.com directly) ... having their default search engine switched on them.
To him, owning a share of the browser market is not really important to Google, in that way, because he has this image of himself and Google being the good guys and doing to no evil.
Someone drank the kool-aid.
This is actually a bit frustrating. There's a bunch of people writing sub-optimal web-pages; not understanding the features or the security; and then there's a bunch of browser engineers trying to keep up.
Security still needs huge amounts of research and energy to progress beyond the broken model (username and pass everywhere / single weak social media login for everything) to something that most users can cope with.
I sound like a luddite, but I miss the days when you could do a Google search for something and the first page would be people who knew a lot about that subject, and who'd written some great text about it, and given it a bit of markup.
Honestly, ideal web pages for me are those but with CSS.
A lot of the web now feels like it's been designed by people who grew up with Geocities and <blink> and <marquee>.
Unfortunately i'm not sure people will adopt it. It's only good for the user. It doesn't bring money.
So unlike Mozilla Google is not practically irrelevant on mobile platforms, why then should they invest more money?
Mozilla, on the other hand, seems to be making mobile a priority with all of the work they are doing in WebAPI. Their browser is updating a lot faster than Android's, which I believe still only updates with OS upgrades.
the point, right there.
And it always remember all my sites so to go to hacker news i just write an "n" and it writes the rest... and i can even delete the suggestions with shift+delete.
So yeah, i also don't have any idea what the parent comment was triyng to say.
Also one small way to improve the search experience, is easy search in multiple search engines. Firefox's search box is one way of doing so, But it has been removed in chrome. Does it really improve the web ?
Does limiting the power of adblocking relative to firefox for example , really improves the web ?
Do giving better/faster experience for youtube and google(no data but few anecdotes from me and friends) , for chrome users is improving the open web ?
And if we talk about moving the web forward , privacy is one of the biggest issues the web currently has. privacy from big companies , privacy from advertisers , privacy from other people doing searches on you and privacy from being needed to show your real name publicly on the web.
Privacy is probably much more important than technical issues like current javascript speed.
Does google really help "move the web forward" on the issue of privacy ?
Making sure the web is an open platform make sure no one control the technology, therefor Google have more opportunities to display ads. And also people have more opportunities to compete with Google too.
Nothing forces you to visit Google properties, etc.
A:yes
Q: does google donatethis money?
A: no.
Q: what is TFA worth then?
A: oh, wait.
so.yeah. right.
Business is not warm and fuzzy. For that, you need to go non-profit. Look at these and you can see that Mozilla is really warm and fuzzy: http://www.mozilla.org/en-US/firefoxlive/
We're not going to implement things that we think are bad for the web just because Google says so. You can look around to see what Brendan Eich (CTO of Mozilla, a higher up by any definition) has to say about Dart and NaCl. Google's money doesn't buy our cooperation on these kinds of issues (and it's worth noting that we work with plenty of people who aren't paying us money, such as Facebook, the same way that we work with Google).
I don't think you can accuse Mozilla of caving in to Google demands at all :)
Which, while annoying for you if you happen to want to push one of those things, is a fantastic thing for the Web. We all simply want to build a better web - and out of the disagreements, we get clarity how to do that.
iOS users are in the same boat, but Apple has been providing much more support to older devices.
- have you seen the specs of the latest high-end phones and tablets? 1GiB of RAM is the norm now
- the number of concurrent open tabs can be limited. It has already been done on Android and iOS (and might still be the case).
According to this HTML5 compliance test, the ICS browser scores 230 (out of 450), while Chrome 15 desktop browser scores 342. Why would these browsers have such distant scores if they shared the same browser core? For comparison, the Firefox 8 desktop browser scores 314 and the Firefox 8 mobile browser scores 314.
There is some work to try to make it portable, but it is unclear how it will end up (how portable, how fast, how secure, etc.).
Partly because of this, NaCl is not standardized or even a proposed standard, which is another problem for the web.
I do admire the NaCl technology though - it's very neat. Although it's bad for the web, it is good for lots of other things.
Not true: http://www.chromium.org/nativeclient/reference/arm-overview
Yes, you can build for more than one arch. But if you have x86 and x86_64, you are missing ARM. If you add ARM, you are missing PowerPC (consoles) and MIPS (some phones). If you add those, you are still missing new archs that will be invented later.
For this reason Google is working on PNaCl - but it has other issues.
In your original comment, were you referring to the fact that Opera also runs on money from deals with search providers, yet doesn't support proposals from them if they disagree?
In any case, Opera has always been one of the biggest supporters of the open web, through working on standards, opposing things that are bad for the web, etc.
What _isn't_ fixed client behavior on the web? Browsers don't just interpret HTML any which way that they want to.
So it is in fact one of the worst things that could happen to the web.
NaCl run on x86-32, ARM and x86-64.
More importantly, content using NaCl would not run on any new hardware platforms that might appear.
So if the web were to use NaCl to an appreciable extent, new platforms would be unable to get any traction in any context that relied on the web. We'd be stuck with ARM or X86 forever for any mobile devices we might have.
Maybe you think that's ok; I think that's a terrible idea; an attitude like that toward the web in the late 1990s would have meant that ARM phones that appeared in the late 2000s would not have been able to browse the web!
(Also, note that I said "hardware _platforms_", not what you asked above.)
You say that because you're not the one actually using hardware built on those chips. And presumably you don't care whether people who _are_ can use the web. But some other people do care.
> X86 and ARM is where its currently at
Key word being "currently". That's fine, but we don't want to make the web _require_ this.
> So it does make sense to target these platforms first.
Sure, but with NaCl you _can't_ target other ones later. You'd have to recompile the code server-side to add any other platforms. This isn't the case with JavaScript, say, where all a new platform would have to do is write a jit for itself and existing content would just work.
PNaCl, if they ever get it working, might not have this particular problem, by the way. If that ever gets off the ground, I'd be happy to revisit this discussion.
> So we can run other languages in the browsers, at full > speed
And forever lock all computing in the world into the ARM and x86 architectures. No thanks.
Or are you talking about software that you only want to run this month and will never want to run again?
Moving from a hardware independent web to one where a full experience would be limited to a few "where its currently at" hardware platforms isn't a step backwards? Heck, while you're at it, why don't we just specify an iOS, Android, and Windows web only?
You're also, by the way, talking about the decline if not the death of a view-source web, a semantic web, and a hypermedia focused web, and probably some other things I'm missing.
By all means, feel free to write native client-server apps for any reason that pleases you, whether it's that you don't like JavaScript as a language or are working on something that truly demands native speed. Just don't advocate destroying the features that have made the web successful.
The important word is currently. As the GP said, 10 years ago "archs where its currently at" would not include ARM, and the ARM success on phones and tablets would have been impossible, because they wouldn't have been able to run the web, if the web used Native Client!
10 years from now, we could have entirely new architectures, and if we lock the web into the currently popular ones, we might miss out on those.