Browsers (1)

Hi folks,

After 3 articles on DocuVieware (this one, this one and this one) you probably know by now that one (and clearly not the only) cool thing about it is that client-side has just one single requirement to provide users with state-of-the-art image/documents viewing, processing and managing:  a browser.
So we thought maybe it’s a good idea to tell you a thing or two about browsers.
During researches made for this article, we found many insipid or inaccurate articles enjoying however lots of views, comments and ‘FB likes’ while a few others, not only interesting but also really funny (like this biblical one) having, helas!, apparently less popularity.
And knowing our readers are smarter, we did our best in putting together some interesting facts in a more distilled approach.

So what’s a browser, anyways? Well, basically it’s the computer program that turns the web’s Matrix of binary data into livable experiences so we can read, hear or watch information.

It’s a rabbit hole of sorts: we hop-in our current informational wish and it pops-out to us whatever we’ve asked for (and also what we didn’t ask for, actually, but that’s another story to tell).

The word “browser” comes from the verb “to browse” of course, which has multiple senses. The sense reserved for humans is “surveying goods for sale in a casual way” while the sense dedicated to animals is the action of “feeding on leaves, twigs or other high-growing vegetation” (quoted texts are taken from the authoritative Oxford Dictionary).
Nevermind, both original senses serve very well the internet-related sense which, although the most recent, it is probably one of the most used terms on Earth for the time being.

The origins of browsers as computer programs can be traced way back and the complete history of their evolution along time is as complicated as counterproductive. So let’s just follow a most simple and logical thread and start by marking 1990 as the first important milestone to mention.