Snapshot 1.2.485.14 - Bugfixes following a short week
-
So far as I know, Vivaldi are NOT building on top of Chromium (which is a complete browser with its own UI), but rather on top of Blink and V8, which are the foundation of Chromium and part of the Chromium Project. It would make little to no sense to build a UI on top of a UI. The advantage that "native" Chromium browsers have over Vivaldi is speed. The advantage that Vivaldi has over them is development speed and flexibility.
-
To the conversation we're all having above, if Vivaldi really is using NW.js, but on top of Chromium and it's UI, then couldn't Vivaldi eventually build all their stuff in NW.js, strip away unused parts of Chromium they don't need like the UI code, and become more and more independent from Chromium? Brave does the same thing, but with Electron, and they only use just the rendering part of the Chromium engine, and maybe a little more. If Vivaldi could do the same with NW.js and strip away all the Chromium garbage they don't need and want and build whatever they need in NW.js, then that would be the best and most efficient solution for them, wouldn't it?
-
Yes, but Brave uses Electron for everything in their browser their way, and uses not much more than Chromium's rendering, if anything. So they probably back-port the security fixes in new Chromium versions too when they can. So Vivaldi can do the same but with NW.js, right?
-
It's getting better. I notice you added some features that make it more Mac-like. I really want to use this. But appearance is an important feature as you know. I can work with a browser that looks good. Chrome does. That is why I stick with it. Vivaldi looks too boxy to me. I think you need to work on that. More pleasant themes are needed too. That would help. The add-ons from Chrome are too boxy too. I will keep checking back.
-
KISS would, of course, be the antithesis of the Vivaldi philosophy.
OldeOpera only had a 2% share of web users, but the way it captured that share was by offering everything under the sun. NO ONE ever needed everything Opera had to offer, but a few hundred thousand wanted this, a couple million wanted that, another half a mil wanted this third thing, etc., etc., etc. and by serving hundreds of tiny constituencies, they cobbled together a large and loyal following. It is all those millions of people that loved OldeOpera and are no longer happy with anything else, but for NUMEROUS separate reasons, that Jon was targeting with this project. There were about 18 million users, when Vivaldi started, still using Opera 12. Jon WANTED (and still wants) those guys. He can't get them by dumbing things down, even temporarily, to polish up a simplified browser. He has to keep going full steam ahead to try to reach the same level of power and flexibility that Opera had.
You will notice that the users who complain of annoyances and bugs are mostly ones from Chrome and Firefox. The ones who complain of completely missing features are the ones from OldeOpera. These latter are the ones Jon wanted to capture first, because the entire REASON vivaldi was started was because such users no longer had a home.
-
I have a question for you; did you find that your "reborn" Bookmarks file [ie, after the HTML Export/Import] was MUCH smaller than before?
Yes, amazing. The Bookmark file skunk from 27.3mb to 1.64mb. A huge reduction. I'm really glad you tried that and then posted your method!
(Re: Path. Yep, I thought to change it to Fred but there are loads of Garry's in the world so didn't worry to much about it :-). )
-
To clarify: I DON'T KNOW if Vivaldi is using NW.js. I just said I could understand if they did.
-
"I didn't know Vivaldi used NW.js." I don't know if they do, either.
-
Ah, well then, we should find out if they do or not. Cause then the solution for them in Chromium would be pretty simple. But if they don't, then I hope they consider one of these ways in the future if it'll mean less bloat, but that's gonna be a lot of work.
Edit: Okay, I just found some more information on some of what they use: vivaldi.net/en-US/forum/vivaldi-browser/3761-technologies-used-to-build-vivaldi#28632
So, it doesn't actually say NW.js, but we don't know. It does say things like React.js, Polymer, Node.js, and basically a bunch of open source web technologies.
Hard to say if it's running on NW.js, but it's probably running on a lot of things.
Now, the question is: Can Vivaldi eventually strip Chromium code it doesn't use, like the UI, flags stuff that Vivaldi can't even use anyway, etc. and build everything using these web technologies, and replace Chromium stuff with their own stuff on these web technologies API's, until they're kind of like Brave, where they only use little more than just the rendering of Chromium? Because then they could be independent, have a better, faster, more secure browser that they can control, and won't be subject to the whims of Chromium. Then the Chromium team and Google will be very unlikely to screw them over, and at the very most, Vivaldi can back-port security fixes and have the rest of the browser with Vivaldi's code. Is that possible and will it be worked towards?
I know you said they also are going to target the old Opera users, and try to put as many features as possible. I want those features too, and I also want a great, polished browser. I hope they can have both someday.
-
Two "R"s in Garry is kind of unusual. It's the same as my older brother's first name.
-
As far as I remember: this one is already known and work is in progress. Although this doesn't affect all of the search engines bing and one or two other still work fine
-
Mmh I was just wondering if there is - or will be - an option to clear cached images and data every time I close Viv?
I know that I can reach this option via vivalid://history but I would like it to have the possibility that the "Clear Browsing Data" option window appears at the end of a browsing session or at that I can define a standard behavior what should happen when I close Viv. -
It's sure to come in time.
-
OMG. Ouch.
-
"It is all those millions of people that loved OldeOpera and are no longer happy with anything else" –> never truer words spoken. I "blame" OO entirely! If i hadn't been so utterly spoiled & indulged by the richness of OO's talents, why who knows, maybe i'd even be kinda sorta half-happy with today's lobotomised browsers. Having once tasted OO though, everything else is simply disappointment... til the advent of V. Yay Jon!!
-
Two "R"s in Garry is kind of unusual. It's the same as my older brother's first name.
Yes, but it's the best way to spell it as your parents understood.
-
LOL! "Skunk". Just noticed now. Supposed to be "shrunk."
-
So posts have Quote and Reply links; some only have Quote. Weird.
-
"Some" posts. :roll: Agggh! And some can't be edited! It's late and I can't even type properly. Hang it, I'm gone.
-
Thank you both