3 ms·
> Please say why C is wrong. I think it's obvious, or should be: manual memory management and poor types. There's no problem domain for which I'd ever want to
by zeveb 10y ago
> Please say why C is wrong.
I think it's obvious, or should be: manual memory management and poor types.
There's no problem domain for which I'd ever want to write C again: not for OSes, not for word processors, not for shell utilities, not for mathematics, not for graphics.
C's strong point is that Unix assumes it.
> No language is "wrong" or "right"
Counterpoints: JavaScript; PHP. Quod erat demonstrandum.
- jly 10y agoHave you ever written a program for a 50 MHz microcontroller with 128 KB of RAM? This is a problem domain in which C is well-suited, where manual memory management is quite important. In fact, there are not many alternatives. It turns out there are a lot of these out there in the world. The world of software development is a lot bigger than PCs running high-level operating systems.
- zeveb 10y ago> Have you ever written a program for a 50 MHz microcontroller with 128 KB of RAM? This is a problem domain in which C is well-suited, where manual memory management is quite important. I think that Forth would be a far better solution in that situation. C would be a mistake IMHO.
- pjmlp 10y agoYes, using Pascal dialects.
- RossBencina 10y ago>> Please say why C is wrong > manual memory management This is arguable. There are cases where automatic memory management is not a viable option, and other cases where it is a poor choice. Just one example: consider all the trouble people go to with off-heap allocation in Java in order to get reliable low-latency operation.