Browsery QE21.C65 2018

Browsery SB321.5.M4 I26 2019

Browsery TR679.5.S54 2018

Browsery TX315.T46 2019

Browsery E185.86.M244 2019

Browsery UG400.W35 2018

Browsery PQ2668.A314 C6713 2018

Browsery TX763.G89 2018

Browsery TX833.5.M674 2018

Browsery LC212.42.S44 2019

Browsery TX807.R7845 2018

Browsery TX801.G55 2018

Browsery TX724.5.A1 M38 2018

Browsery HQ1163.W66 2019

Browsery E185.97.B337 A3 2019

Browsery GF75.W36 2019

Browsery QH438.7.P64 2019

Browsery BD215.G67 2019

Browsery PS3610.E46 A6 2018

Browsery E184.M5 C395 2018

Browsery HQ1237.C745 2019

2020 is only three weeks old, but there has been a lot of browser news that decreases rendering engine diversity. It’s time for some good news on that front: a new rendering engine, Flow. Below I conduct an interview with Piers Wombwell, Flow’s lead developer.

This year alone, on the negative side Mozilla announced it’s laying off 70 people, most of whom appear to come from the browser side of things, while it turns out that Opera’s main cash cow is now providing loans in Kenya, India, and Nigeria, and it is looking to use 'improved credit scoring' (from browsing data?) for its business practices.

On the positive side, the Chromium-based Edge is here, and it looks good. Still, rendering engine diversity took a hit, as we knew it would ever since the announcement.

So let’s up the diversity a notch by welcoming a new rendering engine to the desktop space. British company Ekioh is working on a the Flow browser, which sports a completely new multi-threaded rendering engine that does not have any relation to WebKit, Gecko, or Blink.

The last new rendering engine to come to the desktop was KHTML back in 2000 in the form of the Konqueror browser. Later Apple adapted KHTML into WebKit. And then Google forked WebKit to become Blink. And ... well, almost everyone browses with a KHTML descendant now. Let’s not forget how it all began.

It is far too early to tell if Flow will have a similar impact, but the news was reason enough for me to conduct an interview with lead developer Piers Wombwell.

PPK: Hi Piers, could you please introduce yourself?

PW: I’m Piers Wombwell, the co-founder of Ekioh, the company behind the Flow browser. I’m also the architect of the project and one of the software engineers on it.

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.

How far along is Flow? Can people download it and use it right now?

Well, it can render and interact with Gmail quite well. It’s pretty much perfect on a few sites we’ve targeted as focuses during development, but it struggles with many others. We only started implementing HTML forms in the last few months in order to log into Gmail.

It’s not yet available for download as I think we need to address the usability of it first. It currently needs a configuration file tailored to your computer, and has no toolbar. You don't want a toolbar for TV interfaces, so we never implemented one.

For which platforms is Flow currently available?

For Mac, Linux, and Android. Plus, of course, for the set-top boxes that are our main market, most of which run Linux. As to Windows, none of us run Windows so its development is untested and lags behind a bit, but I’ve just compiled a version and it seems to work.

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.

Which JavaScript engine do you use?

We chose Spidermonkey in 2006, and as far as I recall it was because of both licensing and a documented embedding API. It was around the time that TiVo were having arguments over the GPL. The paranoia over that also ruled out use of LGPL licensed libraries for a few years.

The core browser code is abstracted away from any Spidermonkey APIs, largely so we could handle upgrades over the years - we can still handle its legacy garbage collection model quite happily.

What are your long-term goals with Flow?

The primary goal is stability, followed by getting more websites rendering perfectly in Flow. They generally fail because of either layout bugs or missing JavaScript APIs in Flow, so we have to solve those. Even for the embedded market, getting as many websites working as possible improves our confidence that a new HTML user interface will function correctly, first time.

Our roadmap is very flexible, usually because of commercial needs, but also we prioritise what’s interesting to a developer at that given time.

You said Flow is multi-threaded. Which tasks exactly are divided among the multiple threads?

HTML and CSS parsing is single-threaded, as is JavaScript (if you ignore WebWorkers). It’s the layout, primarily word wrap of text, that is done in parallel. Several caveats apply, but in general, two paragraphs can be laid out in parallel since they don’t impact each other apart from their vertical position.

We wrote some technical papers on this process.

Is the word wrap of paragraphs the computationally most expensive part of laying out an HTML page?

Yes. Each letter is a separate rectangle, plus you have word wrap rules for groups of letters. It’s also probably the hardest to achieve, so it's a good place to start. Desktop browsers haven’t touched layout, and have instead concentrated on making whole components run in separate threads.

Is Flexbox one of the caveats you mentioned?

There are multiple passes across the tree, all in parallel. We first calculate, in parallel, essentially the min-content and max-content widths of each paragraph, flexbox or table cell. Once we have those constraints, a relatively quick pass (not in parallel for that one flex box) works out the final widths of each box.

But we can handle multiple flexboxes in parallel, or one flex box and a paragraph outside the flexbox, and so on.

How integral is multi-threading to Flow and its architecture? Could you remove it? Would other browsers be able to copy Flow's multi-threading?

Multithreading can be turned off with a config setting. I suspect it’s always going to be easier to rewrite the layout code with multithreading in mind than rework existing layout algorithms - Mozilla took that approach that with Servo, rather than rework Gecko. The new layout engine could then, in theory, be combined with the rest of an existing browser.

Can you give an example of tricky problems you encountered while creating this browser?

Many sites, Gmail being a good example, were very frustrating as the JavaScript can be so large and obfuscated. It’s almost impossible to tell what they are doing, and much of the debugging was educated guesses as to what it was trying to do. Thankfully, the web platform tests help us make sure we are compatible with other browsers once we figured out the blocking bug or missing feature.

We can’t realistically pass these tests 100% as they test such a huge set of APIs - it would take us years to catch up with other browsers so we can only focus on what is used by priority websites.

And something that was much easier to implement than you thought?

The HTML parser. I first wrote an HTML parser back in 2002, and back then there was no detailed specification of how to handle badly-nested elements. We spent so much time writing test cases to figure out what desktop browsers did in each situation, and trying to behave the same. Ten years later, the detail in the WHAT-WG specification was amazing, and it was perfectly possible to write an HTML parser that is completely compatible with all other browsers.

And a feature you decided not to implement for now?

HTML forms. A TV user interface doesn’t use most, if any, of the features of HTML forms so it was a very low priority. We started adding them because they are needed for general web browsing, but they are not complete.

We haven’t yet implemented WebGL or IndexedDB because they are not used on most of the websites we’ve tried. Obviously Google Maps uses WebGL and Google Docs uses IndexedDB but both have fallbacks. Implementing more features to allow a larger number of websites to work is a priority.

What is Flow's UA string?

For the Mac version, it's the following:

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_0) EkiohFlow/5.7.4.30559 
Flow/5.7.4 (like Gecko Firefox/53.0 rv:53.0)

The strings vary depending on the device, but the "EkiohFlow" and "Flow" strings should always occur.

Why do you emulate Firefox? I assumed it'd be Chrome.

We’ve spent ages on that UA string… I could probably write a blog post about it. Essentially, I copied Chrome. Things mostly worked. Then I hit the Instagram site, which decided to use ES6 features based on the UA string. I changed it to FireFox’s, using the version of SpiderMonkey that we were using (53 in the build you have), and the site worked. Then I added more afterwards (the rc:53) to get us to the more modern Google login box.

The UA string isn’t final at all but its choice is full of compromises.

Ekioh creates browsers for set-top boxes. What is Flow’s main purpose on set-top boxes?

It is used to render the UIs created by the box’s vendors, and not for actually surfing the web. But we don’t always get to see the UIs the vendors create, so being able to render all HTML flawlessly is the goal. That way, UI developers can do as they please.

Does the average set-top box have a browser meant for surfing the web?

Sort-of, but not really. I have a 2012 Sony TV with that functionality, but it was useless then and is useless now. IR has a significant lag, and that makes TV remotes far too painful to control a TV browser with. I don’t recall any modern TV/STBs that let you have open internet, but they probably exist. I can’t imagine anyone seriously using them.

Flow also runs on TVs and embedded devices. Could you give a few examples of embedded browsers? And TV browsers?

Back before we started our SVG engine, there were many HTML 4 browser engines for the TV market, such as ANT Fresco and Galio (which I also worked on), Access’s NetFront, Oregan, Espial and Opera. For the non-TV market, we have replaced Internet Explorer Mobile on a line of Windows CE devices. These days, almost all embedded browsers are based on Blink or WebKit.

What are your main competitors in the TV and embedded browser markets?

The main competitors to Flow are Blink and WebKit. Most STB providers often do their own port of one of these browsers. WebKit can be optimised for these low-powered devices, but Flow is usually able to out perform other browsers, and in the areas it’s not as fast, we can usually optimise it.

In a strange way, we also compete with ourselves - we offer our own embedded WebKit-based browser that is more feature-complete than Flow. The same developers work on maintaining and improving that.

Thanks for this interview!

You’re welcome.

Fitbit on Thursday launched its Fitbit Heart Study, a large-scale, virtual study to validate the use of its wearable technology to identify heart acti

Gevorkian, Peter, author

Online Resource

Online Resource

Dewey Library - QA483.H39 2019

Online Resource

Online Resource

Online Resource

Rotch Library - QA300.L43 2019

Online Resource

Online Resource

Dewey Library - QA63.P67 2020

Elon Musk's SpaceX, Jeff Bezos' Blue Origin selected by NASA to b...

Astronomers discover closest black hole to earth, can be seen with naked ey...

US President Donald Trump slams Lincoln Project Republicans for COVID-19 ad...

World Thalassemia Day: Hrithik Roshan, Farah Khan create awareness about bl...

Non-bailable warrant against AAP MLA Prakash Jarwal in connection with doct...

A COVID-19 wedding! Specially abled couple ties knot in Jodhpur

People violate social distancing norm in Noida vegetable market

WATCH: MS Dhoni, Ziva play fetch with pet dog in adorable father-daugh...

Religion in Public Schools: Discerning the Needed Balance of Religion in Public Schools Khrais, Reema The recent approach of public educators eliminating any mention of religion in school curricula may prove to be detrimental to the developing education of students. Over the years, United States federal government, as well as many state and local governments, have attempted to interpret the appropriate relationship between religion and public schools. The highly debated issue has been the question of what role, if any, religion should have in America's public schools. Wary of violating any legal constraints, many public schools nowadays have tackled the issue of religion by steering clear of it, or merely neglecting to adequately cover topics concerning it. Debate over the issue of religion in school curricula have fallen under two camps. Some scholars argue that religion should be utterly eliminated in public schools whereas other scholars argue that religion should be a vital component in the school curricula of public schools. In this article, I argue that though endorsement of religion violates the legal principles of the United States, this does not insinuate that religion in school curricula should be excluded altogether. In order to prove such assertion, I will first examine the legal standards of the U.S. under the First amendment as they pertain to religion. I will next analyze the case of Everson v. Board of Education of Ewing Township (1947) and how it aided in establishing the concrete guidelines and interpretation of the Establishment Clause and how such interpretation disallows the promotion of religion in public schools. In the last portion of my article, I maintain my argument by detailing the necessity of discussing and referencing religion in a well-rounded education and how such was effectively carried out recently by a school district in California. As teachers have more than ever avoided the mention of religion, scholars may find that further research on the integration of religion in school curricula must be implemented in order to assess the adequate balance of religious assimilation needed in school curricula.

Hayden Library - TN672.I527 2012

Dewey Library - TN623.C87 2013

The North Eastern States of Assam and Tripura have been under a boil in recent days ever since the Citizenship Amendment Act (originally the Citizenship Amendment Bill or CAB) was passed in both houses of the Indian parliament. The issue is extremely sensitive to the people of Assam, as their state’s GDP was once higher […]

The post BBC reporting blatant lies to mislead World about ‘CAB’ protests appeared first on TIMES OF ASSAM by David Hoffman.

And an unprecedented pandemic of Covid-19 continues to rise! The toll has been ascending every single hour at a much faster rate showing no sign of descent in its trajectory, sweeping off the entire world with fear, anxiety, infections, and deaths. For the first time in history, next to 2009’s H1N1 swine flu virus outbreak, […]

The post COVID-19 – Current bottlenecks and its probable repercussions appeared first on TIMES OF ASSAM by Anmona Handique Mahanta.

Let us pray that organization expert Marie Kondo never comes within spitting distance of A Boy’s Room, part of the Studio Ghibli museum’s Where a Film is Born installation. It’s not likely that every single item in the massive (and no doubt well dusted) collection of books, postcards, hand tools, pictures, figurines, and other assorted tchotchkes pictured above […]

A Virtual Tour Inside the Hayao Miyazaki’s Studio Ghibli Museum is a post from: Open Culture. Follow us on Facebook, Twitter, and Google Plus, or get our Daily Email. And don't miss our big collections of Free Online Courses, Free Online Movies, Free eBooks, Free Audio Books, Free Foreign Language Lessons, and MOOCs.

1 online resource (xix, 727 pages) : illustrations, portraits

It's not just my own kids' well-being that matters anymore.