4 ms·
I’ve been writing C code for 30 years. What I like about it is code from back then is pretty much similar to what you’d right today so there’s limited need to c
by sys_64738 6y ago
I’ve been writing C code for 30 years. What I like about it is code from back then is pretty much similar to what you’d right today so there’s limited need to chase the train. Sure it has security issues but if you don things ‘right’ it’s still untouchable, imo. Most other languages are heavy and slow compared to C. A lot are not even backwardly compatible (python) or suffer from being kitchen sinks (C++). My own opinion is that python is the only other ‘must know’ language as you can do RAD. For speed you resort to C. There are so many toy languages in between with some nice features (coroutines, native JSOn support, etc). But lots are just meh. All personal opinions.
- monetus 6y agoHave you ever tried nim?
- andi999 6y agoDoes nim have numpy/scipy/matplotliv equivalents?
- dnautics 6y agoI think the stack for the next 30 years is going to be zig for low level code, something on the erlang vm for networks and distributed systems, and Julia for numerical computation. It's just too hard to "do things right" in C. Even people who have been "doing things right" for decades make mistakes.