r/programming • • Mar 16 '20

How is computer programming different today than 20 years ago?

https://medium.com/swlh/how-is-computer-programming-different-today-than-20-years-ago-9d0154d1b6ce
5 Upvotes

18 comments sorted by

7

u/[deleted] Mar 16 '20

The tools available, particularly free ones, are lightyears ahead.

Also, trawling through old school internet forums for tutorials and paying obscene prices for physical copies of books.

6

u/[deleted] Mar 16 '20

Creating a new programming language or even creating a new hardware is a common hobby.

I'm not so sure about this one. The other day I was checking some CD/DVD to throw away and found a list of programming languages with a short description/history of them. According to this document from the university of Kansas, as of 1995, there were some 2350 programming languages!

11

u/yeahnoworriesmate Mar 16 '20

We didn't have stackoverflow

5

u/Objective_Mine Mar 16 '20

Nitpick:

Since we have much faster CPUs now, numerical calculations are done in Python which is much slower than Fortran. So numerical calculations basically take the same amount of time as they did 20 years ago.

The code that implements the numerical calculations has generally been written in C. You just call that code from Python through a Python API. So no, it's not slow. I have no idea why people still think e.g. data analysis from Python is somehow slow because it's Python.

I don't know if it's as fast as something implemented in Fortran but it sure as hell has little to do with the speed of pure Python code.

Otherwise a nice article, the kind that's both occasionally funny and has a few points here and there.

1

u/anengineerandacat Mar 16 '20

Python generally speaking is slow, and whats worse is that it's also one of the slowest languages in it's class (interpreted). It's likely a bit more of a "productive" language though due to it's features.

https://greenlab.di.uminho.pt/wp-content/uploads/2017/10/sleFinal.pdf

Do be mindful this study is about 3 years old though; the gap may of closed a bit since then.

As for floating-point performance; I found this https://www.fourmilab.ch/fbench/fbench.html#results

In short, if one actually cared about runtime performance they should stay quite a bit away from Python; though the above does highlight that using PyPy you do get some significant gains putting it at about 100% overhead from Java.

NOTE: If you know of even more credible sources please comment back and I'll edit this comment to include it.

4

u/Objective_Mine Mar 16 '20

Did you even read my comment?

2

u/unfoxable Mar 16 '20

I was at an interview and the guy mentioned that 20 years ago you didn’t have great hardware so you had to optimise your code very well but nowadays people dont optimise shit because we have the hardware and its less work

4

u/quentech Mar 17 '20

the guy mentioned that 20 years ago you didn’t have great hardware so you had to optimise your code very well

No. 40 years ago sure.

20 years ago we were blowing through 1GHz when we were under 100Mhz not 5 years prior. Hardware was amazing back then and you could barely even get your code shipped before a new twice-as-fast processor along with twice as roomy drives and ram were already mainstream.

Nothing like this largely stagnant, boring incremental increases we've seen for nearly the past decade now. At least Zen2 brought a little bit of that old school generational improvements leap back.

6

u/[deleted] Mar 16 '20

It's less work, yes, and also far more productive to not have to work at that level. There was a noticeable shift away from "performance at all costs" to "increased productivity and delivering are far better measures of success" in terms of the languages used for development for most general cases.

6

u/glacialthinker Mar 16 '20

"More productive"... so now we can have 2000 shitty "apps" instead of two good programs to choose from.

2

u/jasonlhy Mar 16 '20

More and more abstraction

2

u/weevyl Mar 16 '20

The tooling: IDEs with integrated debuggers and refactoring support made coding a different experience. Before you needed to spend a lot of time thinking and fleshing out the structure of your code because changes were hard, even something as simple as moving code from one package to another.

2

u/decian_falx Mar 17 '20

The most noticeable difference for me is that package managers and third party code have become a more central part of the process (maybe this is just my career trajectory, hard to say). Twenty years ago I had what the compiler came with and a much smaller selection of online libraries. Finding those online libraries often required some digging because there were only a few very specialized package managers and everything else was just strewn around on random websites. Perl had a package manager, but I feel like it wasn't as big a part of the environment at large.

Package managers and "patch it later" culture have in turn facilitated an explosion in the number of different 'dialects' for various languages. Perl was always criticized for it's loose "there's more than one way to do it" slogan that lead to each developer's code being unreadable to virtually everyone else and now I feel many languages have followed the same path. Things like React for example can be borderline unintelligible for someone only familiar with other Javascript dialects. You can learn 50 different dialects, but 20 years ago the most common case was that there was only one to know and having more than one was frowned upon.

2

u/rainotenk Mar 16 '20

20? 30 years ago you had 64 kb memory and storage was a floppy, imagine

1

u/quentech Mar 17 '20

30 years ago you had 64 kb memory and storage was a floppy

30 years ago we had 486's @66Mhz with probably 4 or 8 MB of RAM and something around a 40GB hard drive.

0

u/[deleted] Mar 16 '20

[deleted]

1

u/rainotenk Mar 16 '20

Oh You caught me, didnt realize I am that old :-) so I meant 40, tsss, shakin head

0

u/[deleted] Mar 16 '20

[deleted]

1

u/rainotenk Mar 16 '20

yep, and prost, fly safe

1

u/flatfinger Mar 17 '20

Twenty years ago, writers of C compilers understood and honored the principles described in the published Rationale for the C Programming Standard (C89 version at http://www.lysator.liu.se/c/rat/title.html), and the myth that the Standard was intended to deprecate reliance upon anything described therein had not yet taken hold.