Vivaldi now has the option to disable inline auto complete inside the address bar, I requested this option from Opera for a very long time and they didn't care. Now I can type the stuff I really want inside the address bar without anything being added in front of it. Vivaldi all the way.

Although disabling auto complete would be nice, I get around that by tapping the spacebar after I've typed some words to search - no big deal.

:'D

... his pockets are not deep enough
... nor are advertisers going to want to flock to support his suite
... It cannot succeed in the long run
... Vivaldi is dead in the water...

You've made some pretty absolute and categorical statements there. I have no idea of the depth of Jon's pockets nor just how Vivaldi will fare in the months/years to come. I only wish I had your sense of certainty about browsers in order to apply other areas of my life.

Making a suite complete with a plethora of features similar to Presto Opera is only attractive to an exceedingly small group of users.

I would say those who complain that Opera isn't the same any more are 'an exceedingly small group of users'. Maybe as a percentage of Opera users it's quite a lot but in overall browser usage, most likely tiny. It will initially be this tiny amount of users who will use Vivaldi and I wouldn't see it being enough to make long term development of the browser worthwhile...or profitable.

There have always been essential minorities, and it's such minorities that have always driven the humanity. The progress, the science, the arts... Majorities are those who is driven, they've never been the primordial drivers - they could only PASS the impulse, reverberate, etc. - in cases of those revolutions, wars, etc. (those revolutions themselves have always been made by certain minorities initially, I believe).

I agree though that scientific research, most arts, sports require money...

Personally, I much prefer the idea of including as many features as possible into the browser itself along with user options to employ them or not, PLUS including the ability to utilize extensions as well. This is what Vivaldi is attempting to do, though how well it turns out is yet to be fully revealed.

You're right. It depends on the engine though - OR if the developers are of genious enough to overcome some "built-in" awkwardness of it.
I imagine the structure would better be lego-like in order for each and every element to get replaced with a better one if needed.

Don't you think, perhaps, they're trying to catch the yester day?
I imagine a browser like Opera (now) or Firefox, where I can put any needed extension to improve capacity/comfort/usability - and it'll most probably work. If it wouldn't, I'll dump this and try another, or something...
Like that home page, like my speed dial in Firefox - by extension...

And when Firefox switches to their new extension API to accommodate Chrome extensions (soon, as in their next major version or so, as explained by their roadmap), all those wonderful and unique Firefox extensions you may rely upon for important (to you) features will have their code broken. Broken, that is, until the extension authors get around to learning the elements of the new API and coding their products accordingly or unless a similar Chrome extension exists. Obviously, there will be a transition period so the old extensions won't 'go away' quite so suddenly, but there are indeed a number of key extension coders who have already stated there's no possible way they can do what their extensions do currently in Firefox if forced to use the new API - so they'll be bailing out and their extensions (and all those users) will eventually just go 'poof' into yet another kind of "yester day".

The reality is that if the browser itself doesn't deliver a feature that a user wants, that feature either will remain missing or the browser must rely on a third party to deliver it via extension. When the browser sustains major redesign, it forces all the third-party extension authors to do likewise, whatever the costs or impact to them. And even if they do redesign, a smooth and reliable outcome is not guaranteed, particularly since the browser developers are under no obligation to help make things work. On the other hand, if the browser does contain a feature the user wants, its own developers have the full responsibility to keep making it work even if the browser is heavily redesigned, or else publish that the feature is being discontinued - in which case, they must face a potential user firestorm similar to what Opera has endured over the last two years.

Personally, I much prefer the idea of including as many features as possible into the browser itself along with user options to employ them or not, PLUS including the ability to utilize extensions as well. This is what Vivaldi is attempting to do, though how well it turns out is yet to be fully revealed.

vivaldi --disable-gpu-compositing

They don't have a GUI option to disable it. It's also throwing errors on a VM and on a live install and on a normal install with Ubuntu, Lubuntu, and Linux Mint. I've not tried anything else.

I was thinking the same, weird name.

Ok, I have done some thinking. Vivaldi was a componist and he wrote some operas

UI is very sluggish.

Yeah, i hope they improve it soon

A huge performance bug was fixed recently. So the next public developer build (soon! ;)) will be mostly fine for anybody not using very high screen resolutions.

Otter is closer to old Opera than Vivaldi. Vivaldi is a better Chropera, but still Chropera.

Yeah, I am thinking now if the dev will keep the Otter, now the Vivaldi Browser came out. Anyone knows?

Jon is in contact with him. Time will tell. :sherlock: