this post was submitted on 13 Dec 2023
1 points (66.7% liked)

Vivaldi Browser

1 readers
1 users here now

A community for Vivaldi - the private, customizable and powerful browser.

Rules

  1. Stay on topic
  2. Behave yourself
  3. No trolling, spamming etc.
  4. Follow lemmy.ml's code of conduct

Useful Links

founded 4 years ago
MODERATORS
morrowind@lemmy.ml
I_Mod_Things@lemmy.ml
1
CEO @jon talks about our choices and the challenge of going against #BigTech as a small company (social.vivaldi.net)
submitted 10 months ago by Zerush@lemmy.ml to c/vivaldi_browser@lemmy.ml
5 comments fedilink hide all child comments
 

(The Interview is in Norwegian, use the inbuild translator of the browser or the Linguist Translator extension https://github.com/translate-tools/linguist )

you are viewing a single comment's thread
view the rest of the comments
[–] sneezycat@sopuli.xyz -1 points 10 months ago* (last edited 10 months ago) (1 children)

Boo hoo, building a browser engine from scratch is hard

Then fork Firefox instead of Chromium, you absolute clown

[–] HKayn@dormi.zone 2 points 10 months ago (1 children)

The only clown here is you, for not doing any research.

At the time, we found that the Chromium engine was secure and the most widely used – that was important to us. Moreover, Chromium was becoming the de facto web standard meaning that if we wanted web pages to not break, we’d have to fork Chromium.

Other pieces of code were either unavailable or undergoing significant re-writes (think Gecko).

https://vivaldi.com/blog/vivaldi-browser-vs-google-chrome/

And before you say what I know you're going to say next: No, Vivaldi cannot afford to cease development for one or multiple years just to switch to Gecko now.

[–] sneezycat@sopuli.xyz 1 points 10 months ago (1 children)

I'm not saying it wasn't a good decision at the time, but why propose building a browser engine from scratch -which takes more work- instead of forking a different browser? It would still take a lot of work, but certainly less than the alternative.

To clarify: I'm not saying it's viable for them to do this, but it's more viable than what they're proposing.

[–] HKayn@dormi.zone 1 points 10 months ago (1 children)

Where did anyone propose to build a browser engine from scratch?

Did you actually read the post you're commenting on?

[–] Zerush@lemmy.ml 2 points 10 months ago* (last edited 10 months ago)

Switching the engine in a browser IS developing the browser from scratch, the team had worked over 4 Years in Vivaldi for iOS, because it needed to work with WebKit, due the restrictions of Apple, and this despite WebKit is way more related to Blink than Gecko. Vivaldi is a small Emloyee owned cooperative, with less than 40 devs for 6 different OS (Windows, Linux,MacOS, iOS, Androit and Android Auto). apart the activism for a free internet, together with DDG, Proton, different consumer organizations and legislators, recently also with Mozilla, which until now has remained somewhat passive due to its relationship with Google.

Blog from 2017

2021

2023