new opera since v12 is rude way
-
A Former User last edited by
i cannot use new versions because its primitive poor instruments.
plz, bring back instruments from v12! -
-
-
Deleted User last edited by
i cannot use new versions because its primitive poor instruments.
plz, bring back instruments from v12!You should not test Opera NEXT or DEVEOPER versions, if you want Opera 12.
Use Opera 12. Why do you want to use Opera 21 test versions?
-
jaanesen last edited by
You're free to continue using 12, only thing is that it isn't being developed any further.
-
A Former User last edited by
i cannot use new versions because its primitive poor instruments.
plz, bring back instruments from v12!Not exactly a constructive comment is it? Or original. The back end engine in New Opera is a VAST improvement over old Opera and means Team Opera can move forwards with new features and innovations across all their browsers knowing they at last have the potential to become a competitive browser. Either use it or move on.
-
pjk0 last edited by
i cannot use new versions because its primitive poor instruments.
plz, bring back instruments from v12!Not exactly a constructive comment is it? Or original. The back end engine in New Opera is a VAST improvement over old Opera and means Team Opera can move forwards with new features and innovations across all their browsers knowing they at last have the potential to become a competitive browser. Either use it or move on.
"Innovations"?
I should write up a list of "innovations" that have been added in Opera Next, compared to features that were removed in Opera Next wrt to Opera 12.
The list of "removals" would be TEN TIMES the size of "innovations".
The current Opera 2x series seems like a completely simplistic toy for children, by comparison.
You do not need to remove all UI features simply because the rendering and javascript engine under the hood is different.
-
elvennoia last edited by
VAST improvement
I might be wrong in my linguistic understanding but, if you have an old car and replace it with new engine, you don't get VAST improvement, you EXPECTED that improvement because you replace with the new one. So basically, team opera is moving forward WITH the new "copy&paste" engine. Thus, means they ditch the features and innovations that may have VASTLY improve the old opera with the sparkling new bundled engine from google.
So, closing of opera was innovation? no bookmark was innovation? uniform UI is innovation? no mate, there is no innovations. -
Deleted User last edited by
I'm sorry mr. @w40in, the current reality is that Opera Classic is not being developed, and Opera Next is a very different product.
You are best off sticking to Opera Classic (v12) if you need that, and use other browsers on the side to cater for difficult websites.
I am using the name "Next" in this way but the confusion is not mine; the Opera team has not given the new browser a name.
-
A Former User last edited by
"Innovations"?
I should write up a list of "innovations" that have been added in Opera Next, compared to features that were removed in Opera Next wrt to Opera 12.
The list of "removals" would be TEN TIMES the size of "innovations".
The current Opera 2x series seems like a completely simplistic toy for children, by comparison.
You do not need to remove all UI features simply because the rendering and javascript engine under the hood is different.I might be wrong in my linguistic understanding but, if you have an old car and replace it with new engine, you don't get VAST improvement, you EXPECTED that improvement because you replace with the new one. So basically, team opera is moving forward WITH the new "copy&paste" engine. Thus, means they ditch the features and innovations that may have VASTLY improve the old opera with the sparkling new bundled engine from google.
So, closing of opera was innovation? no bookmark was innovation? uniform UI is innovation? no mate, there is no innovations.So you are both aware of Opera's reasons they had to abandon Presto as it was holding them back with too many security flaws and page rendering issues that became a chore to fix??
Innovations, as in what's to come in the future, clearly there are some UI developments in the pipelines. The UI features from v12 were removed because this is a completely different browser built from scratch and they have to be re-written if they are to be put back which isn't a 5 minute job. They didn't remove them just to piss people like you off. And I do believe the improvements to page rendering is a VAST improvement. It doesn't matter to me how many unique features a browser has, if it has many problems rendering sites correctly, I'm not going to use it. Believe me, I tried to use Opera (Presto) many times over the lat 14 years but poor page rendering always got in the way.
-
staiger last edited by
cozza wrote: "Innovations, as in what's to come in the future, clearly there are some UI developments in the pipelines."
Are you sure? In a new thread I'm asking if that is, in fact, true. There seems to have been little or no development effort on the desktop browser recently. How long is it since we got a significant new feature? Ages.
Steve
-
christoph142 last edited by
Yet another one... CLOSED
Feel free to chime in to one of the other whining-and-lamenting-threads.
