23 votes

New browser on the block: Flow

7 comments

  1. [3]
    mrbig
    Link
    No relation to WebKit, Gecko, or Blink Supposedly faster than the above Not open-source You cannot download it yet
    • No relation to WebKit, Gecko, or Blink
    • Supposedly faster than the above
    • Not open-source
    • You cannot download it yet
    21 votes
    1. pvik
      Link Parent
      tagging along on this thread to add some more bullet points about the post Being developed for STBs/TVs Also targeting Linux Mac and Android (no official Windows support) Uses SpriderMonkey as JS...

      tagging along on this thread to add some more bullet points about the post

      • Being developed for STBs/TVs
        • Also targeting Linux Mac and Android (no official Windows support)
      • Uses SpriderMonkey as JS engine
      6 votes
    2. dblohm7
      Link Parent
      I see it playing the same role as Servo, TBH.

      I see it playing the same role as Servo, TBH.

  2. skybrian
    Link
    From the interview:

    From the interview:

    Why did Ekioh decide to create a new browser?

    In 2006 we started developing an SVG engine for user interfaces in the set-top box market. No existing browser was full-featured, or was fast enough on the low-powered set-top box chips available at the time. User interface developers wanted HTML, but couldn’t get the performance they needed, especially in animations. SVG seemed better suited to user interfaces as there was no time spent in complex box model layout.

    A user interface running on our SVG engine was much faster than any of the HTML browsers at the time and was very popular in this niche market with millions of STBs running it across most continents.

    Over the next six or so years, STB chips started to move to multi-core GPUs, at the same as TV resolutions were moving to 4K. HTML was becoming fast enough on set-top boxes. On the other hand, a 4K TV has four times as many pixels as an HD TV, and a multi-core GPU doesn't make each individual core any faster. Thus, a single threaded browser won’t really see any significant speed improvements. That's why we decided to make Flow multi-threaded.

    Dabbling with HTML/CSS layout seemed equally fun technically as building an SVG browser, so that’s been the main focus since. It started off being an XHTML/CSS layout engine on top of SVG, but we got carried away and over time moved to full HTML.

    But, really, I suppose we did it because it would be fun to do it.

    5 votes
  3. [2]
    unknown user
    Link
    I'll be honest, I don't exactly understand the reasoning here...

    Is Flow open source?

    It’s not. There’s no current plan for that as we don’t have a large corporation backing our development.

    I'll be honest, I don't exactly understand the reasoning here...

    4 votes
    1. skybrian
      Link Parent
      My guess: they are focused on serving specific customers (set top box manufacturers), they charge a lot, and if it were open source, their customers might not need to pay them anymore? This isn't...

      My guess: they are focused on serving specific customers (set top box manufacturers), they charge a lot, and if it were open source, their customers might not need to pay them anymore?

      This isn't to say there's no way to make it happen, but it would change their business model.

      1 vote
  4. Wes
    Link
    Very cool. KHTML is great, but it's fun to see these completely different takes on the browser.

    Very cool. KHTML is great, but it's fun to see these completely different takes on the browser.