Opera Browser Updates

For web devs and testers like me it would be lesser work. Less styling issues to fix and webkit specific styling that works on chrome and safari would work on opera as well. Floating inline blocks on opera mobile has been pain in a** in my last project.
 
this move is being made so that they do not have to spend resources on replicating features that are already part of webkit.

as a result a bunch of people have already lost jobs at opera (i know a few on twitter). more might be fired in the coming times.

instead of working on their own rendering engine, they can now just submit patches to webkit which they have already started doing.

so what they can do now is to focus on the more important things like user interface, and extensibility. and of course the areas which makes them money... opera for devices.

opera using webkit also means that they would have a proper browser on Apple ios (opera ice was showcased recently so today's news is not exactly a surprise). they would also have a browser that would compete against chrome on android devices.

they can actually steal a lot of users away from google and apple on mobile platforms. and more market share would mean more money from search and other deals (google for search, and localized deals like here in india opera browser is full of shite from airtel).

For web devs and testers like me it would be lesser work. Less styling issues to fix and webkit specific styling that works on chrome and safari would work on opera as well. Floating inline blocks on opera mobile has been pain in a** in my last project.

lol. to be fair, opera has been closest to web standards than any other web browser in the market. web developers out there would tell you that if something is not working in opera, the problem is usually with their code that is not in compliance with actual web standards.

so basically, the same thing is happening again. web developers are coding for webkit and gecko. which are not really the best followers of web standards (google especially).

--

read this post from a google developer who explains it why opera has held a special place in the browser market despite its minuscule market share. the opera we have today is not the opera i fell in love with more than 10 years ago sadly. but then they are doing what they need to do to survive. they are a public company and have investors to please.
 
I am not able to get 1 point till date how is that IE10 throws OPERA, CHROME & FIREFOX completely out of water when it comes to a basic Sunspider Javascript Benchmark from WEBKIT :smartass:MY Score on Various browsers-IE 10 - 101 msChrome - 154msOpera - 171msDifference is quite huge considering how much criticised IE is
 
lol. couple of things. but you probably already know them... 1. IE10 is amazingly fast. There are no doubts about it. But it is also restricted to just two operating systems Windows 7 and Windows 8. 2. Benchmarks do not prove anything. Microsoft could have optimized IE10 to perform better on this benchmark. Though unlikely. They of course have their own benchmarks where they do much much better compared to competition. 3. IE10 has hardware acceleration on I imagine a lot of things. Being part of the Windows OS probably makes it easy for Microsoft to do that. Google Chrome create problems for me in default setting with hardware acceleration and I have to disable it to make it work on my machine. in the end, browsers are more about usability and user experience than they are about raw speed.
 
Yup, thats the reason chrome has been my default browser for almost 2-3 years now (previously firefox). You just can't beat the simplicity & usability of chrome especially accross all platforms
 
Read the post that you mentioned. It was an emotional post. I would like to add some more emotions here. Apart from the obvious / known / stated reasons there are other factors which influence too...

As web/app development shifts from simple notepad / gedit / text editors to content management systems (CMS) (read: already shifted) like wordpress, drupal joomla jquery mobile, appcelerator etc. not many ppl (especially new joiners) are familiar with the old school ways of development. Not that I am against these things, these things have helped grow web at light speed but there are some disadvantages to them too. Using CMS would automatically do styling for you and it mostly gets it right all the time. But problems arise when they don't do the job for you in specific cases on some browsers. Sometimes due to bugs in rendering and other times non-compliance to standards. On some occasions, when fixing them takes a lot of time, these issues make you wonder if using CMS is a good thing or not.

What CMS does for you is that they add lot of classes (forgive me for getting bit technical here.... the class attribute is are primarily responsible for CSS styling). When you have a rendering problem at hand you are left to figure out which one of those the thousand classes (exaggerating here) could have caused the problem. Figuring out the problem is only half way, adding a new browser specific styling and nullifying the effect of the misbehaving class it also a huge task coz the class does not exist in the static html but was added dynamically either by the CMS or javascript library and also removing it would cause rendering problems in other browsers. I could just go on here.. but the point I am trying to make is that with more and more professional work going high level (read: CMS) and not much low level (read: notepad), and regardless of whether Opera's rendering engine follows W3C standards or not, if the engine fails to render the standard CMS layout they are at a disadvantage compared to other browsers that do. Because public opinions matter for a business. Consider it like judiciary vs democracy. W3C standards being judiciary and Webkit like popular democracy. As more and more websites use CMS, it is THE CMS that starts dictating the standards and not W3C (However, I would like to unequivocally state that jquery mobile and wordpress have undoubtedly given more to web than taken back.).

Which is why I accept this move by Opera with mixed feelings. There is not doubt that it makes by job for me as well as thousands of other web developers/testers easier, but we have gone one more step closer to monopoly (not that close as gecko and trident are still very popular).

Moral of the story is that: More often than not business logic as always trumps scientific logic.
 
not that close as gecko and trident are still very popular

not on the mobile front. this is where personal computing has starting to shift big time. when was the last time you use trident or gecko on a smartphone or tablet? :)
 
not on the mobile front. this is where personal computing has starting to shift big time. when was the last time you use trident or gecko on a smartphone or tablet? :)
Forgive me as I always tend to forget that mobile is getting more popular than laptop. I am still hung up in the desktop vs laptop era when ppl have moved to mobile discarding the laptop as well. Not that I don't use mobile... but desktop is still is a significant part of my personal as well as professional life (.. personally speaking, economics and NOT technology is the main reason for that) :)

quicky... also would like to add that windows phones are awesome (though i personally use micromax andorid) and ppl using WP often use IE and therefore trident
 
opera today also revealed that they now have more than 300 million users. guess where most of these users are. mobile. now i am not sure how the switch to webkit affects opera mini which probably has the biggest user base for opera. it does not use the regular presto rendering engine. processing is done on opera servers and a very simple code is delivered to the user's device. still. majority of these users are on mobile devices. which means that webkit becomes even bigger on smartphones and tablets. mozilla continues to struggle with firefox on android. in my own experience, firefox is horrible on android despite the support for extensions and all that. anyways. i am hoping that they do not mess up the core opera experience which had already started deteriorating after the 9.2 release when they started changing opera's own behavior to make it work more like competing browsers.lol at windows phone. i am sure if microsoft allow competing browsers to work on their platform, people would start using a webkit based browser. using internet explorer on windows phone is a compulsion not a choice. windows rt again has the same problem. microsoft is restricting third party browsers. in fact, google's own search app on windows 8 is using the trident engine.
 
I agree that Opera has lot to offer despite them leaving presto behind. As far as comparing the opera mini compression tech with other rendering engine is like comparing apples and oranges as the single column rendering and the server end rendering's primary purpose is saving bandwidth for end user. This is a different market no doubt that it is important one but what we fail to consider here is the loss of rendering engine to another popular one even if it makes my life easier we moving closer towards monopoly. there are some interesting points that the dev had raised in the article that you pointed regarding the font rendering.. these are the things that we would be loosing...Note: Fonts remind me of Steve Jobs and how the calligraphy course that he did proved important in Apple
 
Back