On: Python Is Eating the World

[Ensorceled]

No, not at all, I'm saying if you had been a C programmer in the 90's you would have some perspective on some of the complaints and comments about python in 2019.

[Sean1708 → Ensorceled]

Why are you complaining about C in the 90s? If you'd been using punchcards in the 50s you'd have some perspective on some of the complaints and comments about C in 1990.

[Ensorceled → Sean1708]

I'm actually not complaining about C in the '90s, it was amazing compared to Fortran in the '80s.

Funny story, my first co-op job (Fortran IV), my boss made me fix a bug using punch cards so I'd appreciate why the codebase wasn't as nice as it might be. THAT was prespective.

[Koshkin → Ensorceled]

Fortran was designed for punch cards - sometimes you could even "write" new code by picking old cards from your desk drawer.

[C1sc0cat → Ensorceled]

For what use case? for math and tech programming in the 90's I would have gone with Fortran.

[Ensorceled → C1sc0cat]

Fortran IV? But yeah, Fortran was the goto tool for mathematics, simulations, etc. for the same reason Python often is today: libraries and existing code. I had to convert a simulated annealing algorithm from Fortran to C in the '90s

[C1sc0cat → Ensorceled]

In the 90's it would should been F77 or later if they where stuck on Fortran IV in the 90's I am not surprised Python was invented.

Why did you convert the algorithm from Fortran to c seems a waste of time to me, unless it was a training exercise.

[dboreham → Sean1708]

Abacus in the 0000's...