Modern Programming Trends in context of 1984


Revamp your clocks thirty-three years back:

Computer science has come by far from the initial phase of first generation computers. This development is something which we have seen in front of our naked eyes. But, does actually computer science has changed totally? Where are all the earlier developments replaced with new ones? Well, this is a very vital question to consider after almost 33 years of computer science revolution. That’s why we are taking 1984 as a base year for our comparison.

There weren’t much present in technology sector before 1984. But, this valuable era has swamped technology in a new light. We have some important hardware inventions of that period with us till date. BASIC was impactful than sequencing seven instructions to perform the astounding task of summing two 16-bit numbers. Scheme, ML, and Prolog were all gifted to us by this auspicious year. And moreover, Hughes’s Why Functional Programming Matters was written in 1984.

Some say we have come very far from 1984, but some say we still revolve around that period. So, that’s why need to understand our position after three long decades. To make the comparison let’s pay some attention to these bolded points.  

#Now seems to be the right time to reconsider all those high-level languages. The high-level languages which were set aside due to limits of expensive minicomputers with four megabytes of memory. Which was not able to run 8-bit computer games. But, now memory problem has almost been resolved as we got 125 GB memory in our smartphones nowadays. So, it seems a good time to use these high-level languages again.
#Speed is virtue nowadays. Well, if your program isn’t responding immediately, then we have a big problem. The little line command should take less than two seconds to load and print the version number. There must be some serious efforts required to make them that slow.
#Applications should be designed as small executables. To design application everything is set as multi-core processors, lots of memory, native support for pipes and sockets. Which provides multi-core without support the help of threads. It also considered as a most bulletproof way to separate components.
#Never write temporary files on the disk, ever. There’s only so much RAM, that’s why the fear of files getting lost always roams over your head. Still, after three decades it isn’t possible to create and execute a script without saving to a file first. We still can’t tweak to a learning-the-language test program result in a two-megabyte executable that shortly gets overwritten. That’s the real pain in the ass.
#C still lacks modules. We can’t deny that C is a versatile and dynamic language. But, yet no one tried to add modules to it. Right from the beginning C works without the modules and this isn’t likely to change anytime soon. So, cheers to that!
#Intangled documentation of any program. Before, start learning new program you have to go through the hefty mess of documentation. Some of the documents are so confusing that beginners can’t process them. So, we are still waiting for the program which self-capable to lead the path. As these lengthy documentations makes impossible to distinguish between libraries and APIs.

About the author

Arpit Agarwal

I am a freelancer content writer, web developer and Video editor who loves to write technical stuff and on the other hand makes awesome videos as well. I like to make people happy with my writing and also try to make sure, you come back to read more.

By Arpit Agarwal

Most common tags

%d bloggers like this: