The Web's Fairy Godmother joins Vivaldi


  • Vivaldi Team

    I'm very pleased to share the good news that Molly E. Holzschlag has joined Vivaldi to help us forge closer connections to the developers who help shape the web. Molly needs little introduction but I will still attempt to do so.

    See the full blog post here



  • Hello Molly!

    What ideas are you guys thinking for creating a bigger, more open web, and forge closer relationships with devs who shape that?

    You guys have big goals. Would love to hear them! 🙂


  • Moderator

    Welcome to the team Molly!



  • That's an odd way to sit on a chair 😛



  • For some reason, my comment above disappeared.

    Anyway, hello Molly!

    What are the ideas you guys are thinking of bringing towards a bigger, open web and forging stronger relationships with developers who shape the web?

    You guys have big goals. I would love to hear them! 🙂


  • Moderator

    Awesome. The goddess of webstandards fighters

    Molly, Proud to have you in team!



  • Welcome, Molly!
    It seems that I keep hearing about you wherever I wander on the web – and now you're here! I'm so glad that you've joined the Vivaldi team. 🙂


  • Moderator

    That would doubtless be (for Molly) being an evangelist and ambassador for web standards and interoperability.



  • What an impressive addition to the team !

    Does this mean the chromium core will be dismantled "just enough"?





  • Welcome 🙂



  • Our family is getting bigger! Welcome Molly. 🙂



  • Amazing! 🙂 🙂



  • So, she would get Vivaldi as a program up to par and more compatible to open web standards? Sounds interesting. I almost felt a hint of something about removing some Chromium bits in the blog post, but maybe it's just me.



  • That's what I was thinking too. If this means that they will be trying to remove some Chromium core that Vivaldi's own code has replaced for a while, for further efficiency and flexibility.



  • Wow, Molly! Thanks for that explanation! So, this will ultimately bring devs together for a better, open web and really help with the web industry. I can see that your job is a big one, and I probably won't understand the whole scope of it until I see some more future blog posts. So I'm definitely looking forward to reading your posts in the future.

    Is part of that also helping to shed some Chromium code that Vivaldi isn't using because it's already using it's own Vivaldi code for it? For example, Vivaldi's UI code is it's own code made with web technologies, but if I understand correctly, it's written on top of Chromium's UI code. Is there a way to shed whatever Chromium fat you're not using, and have just the Vivaldi's code there for greater code efficiency?

    If I get it right, this would also affect the outcome of whatever happens in Chromium being out of Vivaldi's control, and shedding Chromium code that Vivaldi has already replaced with it's own code would help Vivaldi have more control over the course of it's own browser. If you look at browsers like Brave, they apparently use not much more than just the rendering part of Chromium/Blink, and the rest of the browser comes from their own code in Electron. This is apparently why Brave is less memory-hogging and less bloated than standard Chromium is.

    Other things that I hear are taken up in Chromium code that Vivaldi replaces and sits on top of are things like vivaldi://flags, bookmarks, UI and so on, all things Vivaldi won't need to use because they've already written their own code on it.

    So, what I would like to know is if this situation is true, that Vivaldi's own code is sitting on top of Chromium code that they can shed off and not need, and be able to remove that Chromium bloat that they're not using. If this is true, they could replace more and more Chromium stuff in the future like with the History page, notifications, font rendering, etc. etc. etc. and become more and more independent, less hogging, faster, and have more control over it's own browser.


  • Moderator

    all the best:)



  • #awesomesauce. If you are going to be a player, why not draft the best player available. Vivaldi has done just that with Molly's hire. Soon, Browser Championships!



  • Oh, almost skipped this one.

    So glad someone focused on standards and UX joins Vivaldi. Thanks for joining them! And thanks Vivaldi for hiring.
    I miss Hakom 😞

    If you don't mind my opinion, my biggest concern for Vivaldi right now it's performance (let's say "click-to-UI-feedback-response-time"). Vivaldi right now takes a long time to start up, and with several tabs opened, switching tabs takes more time than acceptable (more than 0.5-0.7s, I think, isn't acceptable in 2016).
    In comparison, Edge (the MS new browser) is making leaps regarding performance. I already started using it for some small tasks.


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.