Discussion
Loading...

Post

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Tim Chambers
@tchambers@indieweb.social  ·  activity timestamp 2 months ago
@yoasif @gedankenstuecke @anthropy True, they are focused on their strategy: maximizing their future o. differentiation through their unique UI and features and walking off Chromium privacy issues …while remaining on the Chromium base for compatibility and development efficiency — and if Servo or others can mature and be compatible they have said in future they’ll see.
  • Copy link
  • Flag this post
  • Block
yoasif
@yoasif@mastodon.social replied  ·  activity timestamp 2 months ago
@tchambers @gedankenstuecke @anthropy So zero investment. Just sounds like a hope and prayer -- or more likely, just a way to market themselves to people who want them to care about the open web -- even though they don't care to invest even a penny.

They support Chromium, not Servo.

  • Copy link
  • Flag this comment
  • Block
Tim Chambers
@tchambers@indieweb.social replied  ·  activity timestamp 2 months ago
@yoasif @gedankenstuecke @anthropy This convo is going circular. I said from get go their strategy is what I said, but that they are open to future tech like Servo should it get to where it could. They have proven their commitment to the open web and privacy to my satisfaction. And I think their choice on rendering engine makes sense given the givens with Geko and Mozilla's fading. On that note, Ill step out of this convo as its starting to just repeat itself.
  • Copy link
  • Flag this comment
  • Block
yoasif
@yoasif@mastodon.social replied  ·  activity timestamp 2 months ago
@tchambers @gedankenstuecke @anthropy 🤷 Vivaldi's own blog posts don't support what you claim, so I can understand why it feels circular.

PS: I looked for any statement from anyone at #Vivaldi confirming that they would be open to using Servo in the future -- I can't find anything like that -- not even a hint. Just community members asking, and other members saying that maybe it might be possible in the future.

You don't have to link to it, but I *am* curious if someone can find evidence.

  • Copy link
  • Flag this comment
  • Block
Tim Chambers
@tchambers@indieweb.social replied  ·  activity timestamp 2 months ago
@yoasif @gedankenstuecke @anthropy Moving to assuming my bad faith is not a good look.

"How likely is it that down the line we’ll change our chosen engine or develop our own? "

Their ansewer: would depends of the state of future engine and integration:

"The short answer is that we depend on the many modifications we have made to the Chromium code, and 'translating' these to a new engine would not make much sense ... *at the moment.*"

So what I said, they'd see. https://vivaldi.com/blog/vivaldi-different-from-chrome/

  • Copy link
  • Flag this comment
  • Block
yoasif
@yoasif@mastodon.social replied  ·  activity timestamp 2 months ago
@tchambers @gedankenstuecke @anthropy I wasn't moving to bad faith, I was opting you out of providing a response, since the conversation had grown tiresome.

Nothing on that post about Servo.

I can understand you "think" that #Vivaldi can support #Servo in the future, but unless there are further comments you aren't linking, they hardly seem interested.

They seem just as interested in moving to WebKit (that is, not at all).

  • Copy link
  • Flag this comment
  • Block
Tim Chambers
@tchambers@indieweb.social replied  ·  activity timestamp 2 months ago
@yoasif @gedankenstuecke @anthropy Apologies if I misread your comment: I thought you were suggesting my motive for dropping out of convo was due to reasons other than what I stated.
  • Copy link
  • Flag this comment
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.0-rc.3.21 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login