4 ms·
An important comment in the code // Whitelisted apps must be served over https.
by denzil_correa 13y ago
An important comment in the code
// Whitelisted apps must be served over https.
- josteink 13y agoSecurity issues aside, it still reeks bad taste though. Google is saying that everyone on the internet has to dump plugins, dump Flash and create pure HTML solutions. HTML should be good enough for everyone! Everyone except themselves, apparently. They can just jump to native code on their websites whenever they like. So much for their credibility when it comes to web-standards, eh?
- true_religion 13y agoIsn't it entirely possible they want to dog food their own new code via Chrome before they open up the API to the world?
- josteink 13y agoIf they were genuinely interested in dogfooding their own stuff to ensure it works properly, they should also be dogfooding the process of white-listing plugins and websites, not to mention handling graceful fallback when the user cant or wont do that. That's a big part of getting the end-user experience to work well and can't just be "tacked on" later.
- true_religion 13y agoYou're just adding things that probably aren't within the scope of the project. For instance graceful fallback is a 'nice to have' but not necessary. If you deny flash or javascript, essentially most sites simply break. I imagine a native client plugin would have the same results if you don't enable it. As for white listing, why can't it simply be handled with the same dialogs used for whitelisting all the other existing extensions per site?
- wmf 13y agoAs of yesterday(?), everyone is allowed to use PNaCl.