3 ms·
> And they are amenable to the abstraction of C. That's kind of the whole point of that comment. Well, that's sort of the problem, right? C was made so portab
by kbenson 10y ago
> And they are amenable to the abstraction of C. That's kind of the whole point of that comment.
Well, that's sort of the problem, right? C was made so portable (because, admittedly at the time of development hardware was less uniform) that a lot of assumptions we take for granted are actually undefined, because you can't make those assumptions about the underlying hardware. What makes C usable and useful on these architectures is the same thing that causes problems for the other 99.9% of people programming in it.
Should a language with obvious shortcomings in the name of portability be one of the de-facto standard languages for all types of library development? Do i even trust a crypto or XML parser library written in C on a platform with a non "standard" word or byte sizes that wasn't developed specifically for that architecture, or those constraints?
> The world of computing is far larger than PCs and smartphones. One could make a convincing argument that those are a small minority, in fact.
As a question of where to optimize, I would say it pays to get a much safer language on these devices, both because it would prevent crashes, bugs and security problems, and because (I think?) far less people are responsible for writing the code, so a little extra work on their part pays of more overall).
I think C is as prominent as it is today because of how history played out, not necessarily because of its inherent merits.