8 ms·
Mixed emotions here. I think it makes every sense for Opera to do this. The cost of maintaining their own rendering engine must have been huge and the advantage
by andybak 14y ago
Mixed emotions here. I think it makes every sense for Opera to do this. The cost of maintaining their own rendering engine must have been huge and the advantages it brought were slender.
It's also good to have another major player contributing to webkit.
On the other hand it's a step closer to an unhealthy monoculture in rendering engines. It's already the case for the mobile web that people are starting to define standards as 'whatever webkit does'.
- fpgeek 14y agoI wonder if, ironically, rendering engine diversity is something where the slow, incoherent Android update mess is actually a good thing. To the extent that "whatever WebKit does" gets defined as "whatever ugly, lowest-common-denominator thing that works in the stock Gingerbread browser" that might help other rendering engines stay in the race. In other words, legacy Android browsers might help by slowing down the spread of new WebKit-specific features (that they also don't support).
- goldfeld 14y agoWell, webkit being something open and contributed to by many players in collaboration, couldn't we think of it as part of the standard itself? There isn't some evil monopoly to be had in only having one rendering engine, as much as there isn't so in having web standard technologies such as HTML5 and CSS3. I think this is right on for Opera, it has always set itself apart by it's usability and features and I think browsers need to get innovating more on that front.
- gcp 14y agoThe problem of having the standard defined by an implementation is that it makes it almost impossible to have another implementation. This is fine if we agree here and now in 2013 that WebKit is the only rendering engine we'll ever need. That just doesn't seem like a smart bet to make. Opera was in some ways better than the WebKit browsers on mobile devices, except for broken Webkit only sites. That ain't going to get better now.
- simonw 14y ago"This is fine if we agree here and now in 2013 that WebKit is the only rendering engine we'll ever need." - this is a very smart way of putting it.
- d_j_b 14y ago> That just doesn't seem like a smart bet to make. Opera was in some ways better than the WebKit browsers on mobile devices, except for broken Webkit only sites. That ain't going to get better now. But a de facto standard (ie one defined by a popular implementation) forces sites to be compatible or be ignored. More monolithic standard => stronger coding conventions => more robust web. Or am I being totally idealistic?
- gcp 14y agoBut a de facto standard (ie one defined by a popular implementation) forces sites to be compatible or be ignored. No, it's totally the opposite. They only have to be "compatible" with this one implementation, and are free to rely on all implementation-specific bugs or implementation defined behavior when doing so. Think IE box model around the IE5/6 age. Or hell, supporting Office Documents. Even if you'd have the source, being compatible certainly wouldn't have gotten much easier. Note that WebKit is open source and Opera is having problems being bug-compatible with it.
- d_j_b 14y agoIndeed - in principle. But that was back when MS handed down IE binaries from the mountaintop whenever it wanted and most people ran different proprietary OSes. WebKit is open source and it runs on every major platform. Although there is a chance here for the -prefix-rabbit-hole to yawn wide, there's also an opportunity for a (nearly-)universally-supported rendering engine to emerge that could, one day, get into bed with the standards committee. Surely this would be a good endgame for the browser wars?
- kibwen 14y agoThe only worry here, as always, is that an implementation will come to define the standard rather than the other way around. Note that coding to an implementation rather than a standard does stifle innovation, because when you code to target the implementation you inevitably rely on bugs in the implementation, without ever knowing or trying to. From the perspective of an implementor, would you fix a bug even if it meant breaking an unknowably large number of websites? If not, you've adopted that bug for the rest of time, and every subsequent implementation, ever, will be forced to implement the bug as well when they could be busy implementing new features. Now compound this by thousands of bugs, and reflect on all the time spent implementing Quirks Mode in every browser engine that exists today. I do agree with you that in a perfect world we wouldn't need multiple implementations, because bugs would not exist and the lone implementation would track the standard perfectly, and because the standard would be controlled by neutral third-parties. But I think it's much too soon to declare the current era the browser endgame.
- flyinRyan 14y agoOn the other hand, if all browsers just used webkit then maybe we'd finally get "write once, run anywhere" JS, CSS, etc.
- drinchev 14y agoThat's the most scary thing of all. Although open-sourced webkit is mostly developed by big companies ( Apple, Google, Adobe .. ). Webkit is not perfect. There are a lot of bugs that nobody cares and will care less. Imagine what will happen if there are no competitor and webkit core engineers do whatever they want and still people use their engine. Prefixes like '-webkit-animation' will remain forever and w3c specs will not be a significant for them.
- marcedwards 14y agoIf there's bugs you care about, then you patch them. WebKit is open source, so anyone can fork it and build their own version with any fixes or changes they like. I don't see anything but positive news from this.
- quadhome 14y agoThat doesn't mean those patches will be accepted upstream.
- kibwen 14y ago> WebKit is open source, so anyone can fork it and build > their own version with any fixes or changes they like. You're committing an error here. Say you find a bug in Webkit. You patch it, but Apple declines to accept it upstream. You fork the project. Now how do you get your fork into the hands of your users? Unless you're secretly Google in disguise, you're SOL.
- gcp 14y agoIf there's bugs you care about, then you patch them. So now you have a fixed WebKit that nobody else uses.
- 14y ago
- panacea 14y agoIs a monoculture as bad as it might seem though? Front end web development is a clusterfuck. Webkit is open source, unlike the almost monoculture that ie6 represented. It can be forked and evolution can continue. Ditch -webkit -mos and -o. Like when the dinosaurs experienced a mass extinction event and mammals bloomed from a shrew into cats and humans.
- WiseWeasel 14y agoIs that where babies come from?
- gcp 14y agoIt can be forked and evolution can continue. Yes, but only on WebKit-derivates. To use your analogy, it's sort of like trying to make better dinosaurs and deciding that we might as give up on apes at this point, because they don't seem as powerful and get eaten by the dinosaurs anyway.
- coldtea 14y ago>Yes, but only on WebKit-derivates. Well, that's how evolution works. Some species DO get extinguished. This Opera species wasn't adaptive enough. If we want web engine evolution happening somebody should build a BETTER than Webkit engine (e.g the Mozilla Rust/Servo team). Keeping not-that-good engines for the sake of "competition" is not evolution, it's life in "life support".
- gcp 14y agoSome species DO get extinguished. Yeah, and I'm pointing out it's the ones with more hope for the future, rather than the ones that are obviously doomed in the very long run. If we want web engine evolution happening somebody should build a BETTER than Webkit engine Yes, and as already explained, this will become near-impossible if there is no standard, but just a bunch of webpages that need the renderer to do "whatever WebKit does". A big factor in Operas decision was already that for mobile webpages, any renderer that isn't WebKit is already dead. Not that they thought their own engine sucked. This is stopping evolution, not helping it.
- jerhewet 14y agoUnhealthy? I've been longing for the day that all browsers are based on WebKit, because it means a real web programming language will be that much closer to replacing kiddiescript. EDIT -- from http://wtfjs.com http://wtfjs.com: parseInt('06'); // 6 parseInt('08'); // 0 Your language is bad, and you should feel bad.
- brownell 14y agoI think you're missing something... parseInt('08', 10); // 8
- michael_h 14y agoThis comes up every now and then. That code makes perfect sense. You write octal numbers by prefixing them with a zero, the same way you write hexadecimal numbers by prefixing them with a '0x'. strtol("06", NULL, 8); //6 strtol("08", NULL, 8); //0 Is C bad? Should Kernighan and Ritchie feel bad?
- T-hawk 14y agoC wasn't bad for making that design decision in 1973, to include syntactical space for octal numbers. Programmers actually used octal notation then. It made sense in an environment where contemporary tech included the PDP-8's 12-bit words (four octal glyphs) and displays of seven-segment numeric readouts (where octal is useful, as letters for hexadecimal can't be displayed and base-10 needs conversion logic.) Javascript was bad for making that design decision in 1995, when nobody seriously used octal for anything, so the leading zero was vastly more likely to introduce a class of WTF bugs instead.
- papsosouid 14y agoNo, because strtol gives you the ability to see that the parse failed and where. You chose to give it NULL there, but you could choose to use the function correctly. You can't do it correctly in the javascript and PHP cases. In the PHP case, it is actually just a bug in the PHP codebase that octal digits are supported at all, and they don't use strtol correctly. Note that perl, python and ruby all support octal digits correctly, there really is no excuse for PHP and javascript not to.