csulok's comments

I don't think it can be solved without origin specific permissions - to allow using local fonts and whatnot used on the canvas, at the same time I don't think that would be an issue.

Tesla is operating at a loss, but Model S and Model X are sold at a high margin comparable to other cars in their category. Source: share holder letters.

Wouldn't Let's Encrypt offset any significant benefit of this change? Is it somehow difficult or counterproductive for these sites to add a certificate?

Is Mac support planned? Not really familiar with the internals, so I can't tell if the Linux branch is a generic (enough) branch for Unix and alike.

Well they did have Opera Beta with webkit as a separate app in the appstore for quite a while, that's a good solution for not-liking-thus-downgrading issue.

Also, on the Play Store publishing page, there are features for beta and alpha testing, not sure what they do, but I feel they are relevant as well.

on arstechnica.com.

it's highest everywhere else.

Have you tried onx?

https://www.onx.ms

it's funny how nothing changed in the last 5 years. Just replace ie10 with ie9 or ie8 in the comment and not too long ago those were true.

what happens at 35k? what milestone is that beyond a random round number?

and nothing of value was lost

>> I find it sad (to annoying) that these projects still use actual form elements instead of `contenteditable`, even though they're quite obviously full-JS (and probably not going to be submitted through HTML forms), given the difficulty of correctly styling, integrating and interacting with form elements.

I think this is because of performance. form elements are rendered differently and actions mostly result in a limited repaint and a couple events fired. contenteditable DOM elements are a lot more work to update.

when setting the recipients, at the right there's a "cc" and "bcc" link, next to them is a "from" link as well. few more clicks then with the old interface, but that's fine for me. my only problem with this new UI is that reply cannot be popped out into this separate window

In service discovery is just convenient. With SOAP libraries, using a web service is as easy as 2-3 lines of code. The library handles loading the wsdl file, generating functions with appropriate parameters, sending requests and parsing response and exception handling. Without this ability, it's a lot more code.

It's not necessarily harder, but it's more code nevertheless.

having started my programming career with web stuff, i just cant stand the full blown IDEs because of their slowness and bloatedness. sublime text feels like having my cake and eating it too. it has most of the required features but its still amazingly fast and extendable.

i think it's pretty obvious they are happy with their decision - you get your android upgrade when you go from galaxy s2 to s3 and alike.

Money is powerful and everything, especially if you don't have it, but I think Opera knows it best it will lose a significant part of its core usergroup if this goes through. They would essentially ruin what they fought for all these years

No, don't get me wrong. I don't want to hold the development back. Websites, design wants to evolve fast, faster than anything ever before. I think vendors get this on some level, that's why they let us use these properties, but they need to do a better job as a collective: the working groups that draft the standards. If they standardize faster, there won't be any change in your ability to use brand new technology at the current rate.

For example: webkit devs think of a new property. They build it, they like it, they make it publicly available. Chrome guys enable using this in the dev and beta channel. In a couple weeks they have feedback on performance and stuff. Whatwg convenes, they finalize the details, webkit guys make a few adjustments (and it's fine because there's only 2 webpages on the entire internet that's been using it for a month tops) and then soon it hits the stable channel. This is what we need. Fast updating browsers could rape the benefits of such a system very nicely, fast updating is what we need to let the web evolve fast enough anyway. Slow updating browsers can go die in a fire, they are just as slow with supporting everything else.

Also, not to nitpick, but opera on the mobile front isn't unimportant. It's the only alternative to webkit, it's nearly ubiquitous and not a bad experience on mobile.

The root cause of this issue is that prefixed properties are prefixed for too long as the standardization speed doesn't match the reality of how fast the web evolves and wants to evolve.

Fast releases and automated updates only make it worse, as two minutes after a prefixed property is thought up, a seriously large number of users will have support for it, developers will play with it and then the css code gets stuck on the internet.

By now most developers are in the mindset that it's okay to let a page differ in some browsers as long as the difference is only minor/aesthetic and not a functional handicap. And matching this vendors are perfectly happy with letting developers use prefixed properties as if they were stable.

Since these vendors make up the whatwg and w3c, they need to get their shit together and standardize faster and in the meantime developers need incentives to only use prefixed properties on test sites, which could be as simple as a console message that it should be removed (like how they did with the event.layerx deprecation) or having the user enable test mode in their browser configuration.

why not a magnetic shield? like what earth has