Skip to main content

Week 2: Pre-web technologies vs the web

Fax

Fax or facsimile or telecopying is the telephonic transmission of scanned-in printed material, which used to be a popular way of sending printed pictures and documents wirelessly to others. It was in 1843 when a Scottish inventor and mechanic named Alexander Bain received a British patent for his invention - “improvements in producing and regulating electric currents and improvements in timepieces and in electric printing and signal telegraphs.” But later on an English physicist, Frederick Bakewell improved Bain's invention, which was much more similar to the fax machines that we have today. 

Although the concept of fax comes from the 1800s, fax machines and faxing didn't become widespread until the 1980s, when it became more inexpensive. But as technology has evolved, fax has become obsolete as it has become outdated and ineffective compared to the digital alternatives that we have now. As fax has built-in security flaws and excessively wastes resources like paper it really has no place in the everyday home and work environment.

C

An example of pre-web technology that survived the web and actually became even more popular since then is the programming language C. It was developed between 1972 and 1973 by Dennis Ritchie in Bell Labs, initially to be used in UNIX operating system. It was derived from previous languages like B and BCPL, so it has lot of the same features.

Despite being published decades ago, C is still widely used today, especially the variations of C like C# and C++. C is still the most used programming language throughout time, and as of January 2021, C was even ranked first in the TIOBE index which is a programming community index that measures the popularity of programming languages. If you compare C to other languages evolved from it, it isn't nearly as bloated as the others, it's fairly straightforward, it has great performance and most importantly it was developed to work with the hardware of a system so you have a lot of control over what is going on. 



Sources: 
https://www.javatpoint.com/history-of-c-language
https://www.infoworld.com/article/3402023/why-the-c-programming-language-still-rules.html

https://faxauthority.com/fax-history/
https://www.efax.co.uk/blog/is-fax-obsolete
https://www.britannica.com/technology/fax

Comments

Popular posts from this blog

Week 9: Examples of bad and good HCI

With technology developing rapidly, we find all sorts of new ways to improve our lives and how we interact with technology. With technological innovation, we might witness the creation of something life-changing and spectacular or something that just no one even asked for. I'll try to bring examples of both worlds. Firstly I'd like to bring a good example of HCI - eye-tracking. I recently watched either a video on YouTube or a documentary on Netflix (can't really member which) that showed how eye-tracking technologies have changed the lives of people suffering from illnesses like locked-in syndrome. Locked-in syndrome is a condition where people have full cognitive ability but they are unable to move or speak due to paralysis of voluntary muscles. So usually they can only move their eyes, and that's about it, although some can't even do that. They are literally locked in their bodies unable to move and communicate with others. But thanks to eye-tracking, people that

Wiki Review: The Chinese Social Credit System

For my Wiki review I chose a paper by Bálint Adám, Dominik Kovács, Benedek Matveev, Luca Mizzi and Carlos Rodriguez on The Chinese Social Credit System. I think the topic chosen is really interesting, hence why I chose this article to review, and important at the same time. As the Chinese government is really invading people's privacy, at least in my opinion, by tracking its citizens and companies. It's important to know about the problem so we could avoid this also happening in the western world. All in all, I think the most important aspects of the topic got covered, at least what I was hoping to learn from it while reading the article, and it was presented in a good manner so it was interesting to read. The structure of the article was good, it was organized in a logical way and was divided into subcategories, although they could have been tied a bit better. The viewpoint or angle of the article was for the most part pretty neutral as it should be. Maybe it was a bit to the

Week 6: Copyleft

Continuing on the topic of copyright issues, this week's post will be about Copyleft and what impact it has on choosing a software license for one's project.  So first of all, what even is Copyleft? Some of you might have heard of this term before in association with open-source software. Well, it's a license for free content/software that determines whether or not the derived works are influenced by the license or not. In contrast to copyright, copyleft ensures that the code/content is freely available for use and modification, whereas copyright more restricts uses.  There are three different grades of copyleft: Strong copyleft - one of the most famous examples is definitely GNU GPL, which was also the first copyleft license. This basically means that the license applies to all derived works and you are obligated to publish the source code if you distribute code that was derived from theirs. Weak copyleft - an example of this would be GNU Lesser General Public License. T