Poll: What do you think about Opera switching to WebKit? comments
Page 4 of 4(169 comments)
Left under the original article, as archived.
FireFFFUUUThursday, February 21, 2013 5:44:11 PM
Originally posted by M-Z:
Most of us have chosen Opera despite some compatibility issues, but we are not willing to give up features.
+++++1
Originally posted by M-Z:
I don't believe Opera has too much marketing power - they cannot "suggest" using different browser on major portals - so it makes a necessity to deliver quality. If they don't they are doomed.
+++++1
The irony is that with the possible purchase of Facebook had been able to obtain marketing power, but this was rejected.
Kobzar2WebFriday, February 22, 2013 8:34:20 PM
Originally posted by slash4real:
And YES, Opera would be one of the few softwares that I would pay for.
>
Me: too!..
IlgazTuesday, February 26, 2013 11:40:22 AM
Even a screenshot showing a familiar site such as m.imdb.com showing side by side with new and old (!) engine would settle me.
Opera is star of mobile layout and interaction with artificial intelligence like behavior. Google and Apple have different targets. That is the part which makes me anxious.
Guy FlemingWednesday, February 27, 2013 6:05:46 PM
"Update, November 22nd 2012: Please note that Opera 12.00 final shipped with 64-bit and OOPP support, and that as of version 12.02, OOPP is disabled for Windows 32-bit."
ChirpieThursday, February 28, 2013 9:11:47 AM
Originally posted by teresaejunior:
Gecko and Webkit are open-source and no hobbyists have destroyed them so far.
Gecko and WebKit both have or had professional organizations actively using and promoting them (Google was one of the biggest Firefox contributors before they made Chrome, remember). WebKit started out as something Apple was putting big money into. Presto will get no such support.
ChirpieThursday, February 28, 2013 9:12:19 AM
Originally posted by Virusboy:
I think my friend put it best "What do you think of Opera going from Presto to Webkit" "Welcome to Safari 2.0"
Chrome is Safari 1.5?
Morons who don't understand the difference between engine and UI don't deserve to speak freely.
ChirpieThursday, February 28, 2013 9:13:33 AM
Originally posted by ichbinluda:
Will you slowly abandon Desktop version completely now that you spent 150 mil $ for that firm for mobile video streaming and something?
What a stupid comment.
Why would they abandon the desktop version (a whole 3rd of Opera's revenue) because of some random acquisition? Do you think Opera doesn't want to make money?
ChirpieThursday, February 28, 2013 9:14:22 AM
Originally posted by CREEPER:
I fear the same. Somehow I feel that Opera is giving up competition on Windows-based PCs and starts focusing on Android-based mobile devices.
So are they giving up on Android-based mobile devices too, since they're dropping Presto there as well?
Your logic is non-existent. Use your brain instead of spewing nonsense.
Without a solid PC product, Opera will lose many users both on PCs and mobiles. With Webkit browser they have only one shot. If they miss, they are doomed.
Bullshit.
ChirpieThursday, February 28, 2013 9:15:21 AM
Originally posted by crash71:
In 13 years since Opera 5.x - Opera 12 has been the buggiest version to date
Bullshit. Stop spewing your inane crap.
ChirpieThursday, February 28, 2013 9:18:39 AM
Originally posted by M-Z:
The problem is porting features to Webkit. No sane person will accept loosing most of Opera's capabilities, just to satisfy some managerial decision (which are frequently targeted at short term profit).
Except the decision was made by the engineers at Opera, as stated in Norwegian interviews. Take your inane conspiracy crap and shove it.
How on earth does this result in short term profit anyway? Opera was already had record profits. Switching is going to be damn expensive, so they will lose money in the short term.
Clearly this is a long-term decision to secure Opera's future.
I don't believe Opera has too much marketing power - they cannot "suggest" using different browser on major portals - so it makes a necessity to deliver quality. If they don't they are doomed.
Yawn. Another crazy doomsday prophet.
M-ZThursday, February 28, 2013 9:15:52 PM
Originally posted by Chirpie:
Except the decision was made by the engineers at Opera, as stated in Norwegian interviews. Take your inane conspiracy crap and shove it.
Really? I thought in corporations it is the management who "call the shots". I don't know how long have you been Opera user, but I use it since version 6.0. In those days Opera was ground-braking, now it follows the herd. So I think I have an experience in this matter. And if you became user lately and see Opera as just another Chrome clone - because they are trying really hard to mimic Google's browser - don't tell us "hardened" users what we shouldn't be afraid of.
How on earth does this result in short term profit anyway? Opera was already had record profits. Switching is going to be damn expensive, so they will lose money in the short term.
I don't know - I don't attend Opera board meetings. But one scenario is to fire half of developers, lower costs and pump profits. Maybe their polls showed that many users use Opera just like any other browser. So why not let someone else do the developing? I don't know - future will tell us who is right. But don't tell me there is NOTHING to be worried about.
Clearly this is a long-term decision to secure Opera's future.
Let's hope so...
Yawn. Another crazy doomsday prophet.
If it is just crazy business, why don't you just disprove my theories? I don't have technical knowledge about browser engines and how closely are they interlinked with UI, but in the worst case scenario they are very closely interlinked. So all good Opera features we love will be gone (spatial navigation, fast back [which is kinda broken anyway], disable plugins/animations, good session management etc.). Now your task is simple - instead of ranting find some arguments, why should anyone use Opera if it is the case?
ChirpieFriday, March 1, 2013 8:45:45 AM
Originally posted by M-Z:
Really? I thought in corporations it is the management who "call the shots".
Yeah, but there are engineers managing things as well, and these can advise the management higher up. A Norwegian interview stated that the decision was made by engineers.
I don't know how long have you been Opera user, but I use it since version 6.0. In those days Opera was ground-braking, now it follows the herd.
Bullshit. Some of Opera's most important inventions came long after Opera 6.
And if you became user lately and see Opera as just another Chrome clone - because they are trying really hard to mimic Google's browser
More bullshit. A clean UI is not patented by Chrome. In fact, Chrome stole Opera's features and looks (tabs at the top, speed dial, etc.).
Originally posted by M-Z:
I don't know - I don't attend Opera board meetings. But one scenario is to fire half of developers, lower costs and pump profits.
More bullshit. They didn't fire half of their developers. 90 people left or were fired. Less than half of those were developers. With hundreds of developers, 20 or so leaving is irrelevant.
Maybe their polls showed that many users use Opera just like any other browser. So why not let someone else do the developing?
Again, this is bullshit. They are not letting someone else do the development. As you can see on Android they made their own UI.
Originally posted by M-Z:
If it is just crazy business, why don't you just disprove my theories?I don't have technical knowledge about browser engines and how closely are they interlinked with UI, but in the worst case scenario they are very closely interlinked. So all good Opera features we love will be gone (spatial navigation, fast back [which is kinda broken anyway], disable plugins/animations, good session management etc.).
You are talking bullshit as always. The engine doesn't make the UI. The UI is made separately. No matter what the UI looks like and what features it has, that doesn't depend on the engine. It depends on the people designing the UI.
yellowfourSunday, March 3, 2013 4:14:43 AM
The technical aspects of Opera is only a means to an end. Opera is a movement. Freedom from monopolistic corporate tyranny. Freedom of user to customize their tool and experience to their needs and preferences. Freedom of web developers to develop their sites to cater to all web browsers and not settle for and surrender to a single platform. Freedom to not dumb down and slow down web surfing experience to the lowest denominator.
yellowfourWednesday, March 6, 2013 9:31:48 PM
I tried the new Opera webkit beta. If I wanted a webkit browser, I would have stayed with Dolphin. But fact is Opera Mobile provides the best web browsing experience on a smartphone by far.
Webkit layouts waste a lot of screen space, requiring more unnecessary zooming, panning, and scrolling. Gesture based interface puts more strain on hands and fingers compared to buttons. This beta is missing many options, like default zoom size, which would help a lot with the inferior webkit engine. Sizes are all over the place. Headers are way too big, while regular text and images are way too small and blurry. No opera:config, why? No way to use custom css or js.
I used to be able to double tap and Opera mobile would render perfectly. Text and image sizes were uniform. Scrolling and panning was brisk and responsive. opera:config also present, so I can customize the browsing experience exactly how i want, not how stupid developers want (bloat, slowness, eye sore), and definitely not how webkit wants.
FransWednesday, March 6, 2013 10:10:07 PM
Originally posted by yellowfour:
I used to be able to double tap and Opera mobile would render perfectly. Text and image sizes were uniform. Scrolling and panning was brisk and responsive. opera:config also present, so I can customize the browsing experience exactly how i want, not how stupid developers want (bloat, slowness, eye sore), and definitely not how webkit wants.
+1
Also thanks to the Webkit beta I discovered Webkit hasn't even unprefixed linear-gradient yet. I wonder how long that prefix will remain once they finally do add support for unprefixed…
DoTheEvoWednesday, March 6, 2013 11:21:02 PM
Can we know what will be the designated version number of the desktop opera-webkit?
12.50 seems undeserving, will it be 13.00?
s/ashWednesday, March 6, 2013 11:33:54 PM
Originally posted by DoTheEvo:
Can we know what will be the designated version number of the desktop opera-webkit?
14 I guess. It seems like they skip v13. Other companies skip some versions too, especially v4 and/or v6 - nobody wanted to see a "Winamp 4 skin".
scipioMonday, March 11, 2013 1:46:05 PM
A "Not sure" for me. As stated by others, I'll have to see if features that make Opera irreplaceable for me will remain (M2, mouse gestures, dev tools, userjs/css, single-key shortcuts, ...).
FireFFFUUUThursday, February 21, 2013 5:44:11 PM
Originally posted by M-Z:
+++++1
Originally posted by M-Z:
+++++1
The irony is that with the possible purchase of Facebook had been able to obtain marketing power, but this was rejected.
Kobzar2WebFriday, February 22, 2013 8:34:20 PM
Originally posted by slash4real:
>
Me:
too!..
IlgazTuesday, February 26, 2013 11:40:22 AM
Opera is star of mobile layout and interaction with artificial intelligence like behavior. Google and Apple have different targets. That is the part which makes me anxious.
Guy FlemingWednesday, February 27, 2013 6:05:46 PM
http://dev.opera.com/articles/view/64-bit-opera-and-out-of-process-plug-ins/
If this does get removed Opera will have no reason foe me to use.
Rafael LuikWednesday, February 27, 2013 10:43:08 PM
Originally posted by Virusboy:
"Update, November 22nd 2012: Please note that Opera 12.00 final shipped with 64-bit and OOPP support, and that as of version 12.02, OOPP is disabled for Windows 32-bit."ChirpieThursday, February 28, 2013 9:11:47 AM
Originally posted by teresaejunior:
Gecko and WebKit both have or had professional organizations actively using and promoting them (Google was one of the biggest Firefox contributors before they made Chrome, remember). WebKit started out as something Apple was putting big money into. Presto will get no such support.
ChirpieThursday, February 28, 2013 9:12:19 AM
Originally posted by Virusboy:
Chrome is Safari 1.5?
Morons who don't understand the difference between engine and UI don't deserve to speak freely.
ChirpieThursday, February 28, 2013 9:13:33 AM
Originally posted by ichbinluda:
What a stupid comment.
Why would they abandon the desktop version (a whole 3rd of Opera's revenue) because of some random acquisition? Do you think Opera doesn't want to make money?
ChirpieThursday, February 28, 2013 9:14:22 AM
Originally posted by CREEPER:
So are they giving up on Android-based mobile devices too, since they're dropping Presto there as well?
Your logic is non-existent. Use your brain instead of spewing nonsense.
Bullshit.
ChirpieThursday, February 28, 2013 9:15:21 AM
Originally posted by crash71:
Bullshit. Stop spewing your inane crap.
ChirpieThursday, February 28, 2013 9:18:39 AM
Originally posted by M-Z:
Except the decision was made by the engineers at Opera, as stated in Norwegian interviews. Take your inane conspiracy crap and shove it.
How on earth does this result in short term profit anyway? Opera was already had record profits. Switching is going to be damn expensive, so they will lose money in the short term.
Clearly this is a long-term decision to secure Opera's future.
Yawn. Another crazy doomsday prophet.
M-ZThursday, February 28, 2013 9:15:52 PM
Originally posted by Chirpie:
Really? I thought in corporations it is the management who "call the shots".
I don't know how long have you been Opera user, but I use it since version 6.0. In those days Opera was ground-braking, now it follows the herd. So I think I have an experience in this matter. And if you became user lately and see Opera as just another Chrome clone - because they are trying really hard to mimic Google's browser - don't tell us "hardened" users what we shouldn't be afraid of.
I don't know - I don't attend Opera board meetings. But one scenario is to fire half of developers, lower costs and pump profits. Maybe their polls showed that many users use Opera just like any other browser. So why not let someone else do the developing?
I don't know - future will tell us who is right. But don't tell me there is NOTHING to be worried about.
Let's hope so...
If it is just crazy business, why don't you just disprove my theories?
I don't have technical knowledge about browser engines and how closely are they interlinked with UI, but in the worst case scenario they are very closely interlinked. So all good Opera features we love will be gone (spatial navigation, fast back [which is kinda broken anyway], disable plugins/animations, good session management etc.).
Now your task is simple - instead of ranting find some arguments, why should anyone use Opera if it is the case?
ChirpieFriday, March 1, 2013 8:45:45 AM
Originally posted by M-Z:
Yeah, but there are engineers managing things as well, and these can advise the management higher up. A Norwegian interview stated that the decision was made by engineers.Bullshit. Some of Opera's most important inventions came long after Opera 6.
More bullshit. A clean UI is not patented by Chrome. In fact, Chrome stole Opera's features and looks (tabs at the top, speed dial, etc.).
Originally posted by M-Z:
More bullshit. They didn't fire half of their developers. 90 people left or were fired. Less than half of those were developers. With hundreds of developers, 20 or so leaving is irrelevant.Again, this is bullshit. They are not letting someone else do the development. As you can see on Android they made their own UI.
Originally posted by M-Z:
You are talking bullshit as always. The engine doesn't make the UI. The UI is made separately. No matter what the UI looks like and what features it has, that doesn't depend on the engine. It depends on the people designing the UI.yellowfourSunday, March 3, 2013 4:14:43 AM
yellowfourWednesday, March 6, 2013 9:31:48 PM
Webkit layouts waste a lot of screen space, requiring more unnecessary zooming, panning, and scrolling. Gesture based interface puts more strain on hands and fingers compared to buttons. This beta is missing many options, like default zoom size, which would help a lot with the inferior webkit engine. Sizes are all over the place. Headers are way too big, while regular text and images are way too small and blurry. No opera:config, why? No way to use custom css or js.
I used to be able to double tap and Opera mobile would render perfectly. Text and image sizes were uniform. Scrolling and panning was brisk and responsive. opera:config also present, so I can customize the browsing experience exactly how i want, not how stupid developers want (bloat, slowness, eye sore), and definitely not how webkit wants.
FransWednesday, March 6, 2013 10:10:07 PM
Originally posted by yellowfour:
+1
Also thanks to the Webkit beta I discovered Webkit hasn't even unprefixed linear-gradient yet. I wonder how long that prefix will remain once they finally do add support for unprefixed…
DoTheEvoWednesday, March 6, 2013 11:21:02 PM
12.50 seems undeserving, will it be 13.00?
s/ashWednesday, March 6, 2013 11:33:54 PM
Originally posted by DoTheEvo:
14 I guess. It seems like they skip v13. Other companies skip some versions too, especially v4 and/or v6 - nobody wanted to see a "Winamp 4 skin".
scipioMonday, March 11, 2013 1:46:05 PM