(23-08-2015, 09:41 PM)Houseoftea Wrote: First: I've been Reading a lot and people keep saying c is impractical for modern projects. Useful only on embedded systems or for kernels. Is this because its a low level language or its lack of objects or are they wrong?

I know some Java and Python programmers who work on "modern" projects. Those people think on a completely different level. It's a bit hard to explain... They're more like "software architects" instead of "programmers". They don't build rooms nor houses, they build entire cities and countries. Some of them even try to build an entire planet. From their point of view, using C is like using scissors to cut a tree.

It's also important to note that those people are often professional programmers (as in: they get paid for writing code). With very tight schedules and huge piles of TODO lists, they simply can't afford taking the time to write good C code.

They are very pragmatic people. They want libraries and frameworks that do most of the job. Why? Because it's less time consuming, it's much easier and it's less error prone.

Thus, they rightfully argue that C is impractial -- at least for what they do.

At the other end of the spectrum, there's us. I guess that most of us "work" in our spare time. We're enthusiasts. It's not even "work", we're doing this for fun. There's no nagging customer. There's no manager. We care about clean code and simplicity. We care about the little details. And we're not forced to comply to weird specifications (most of the time).

For us, it's a lot easier to use C. It is indeed practical.

However, I don't know any professional C programmer in person. I'd be interested to know: How does the work of professional C programmers differ from the work of Java and Python programmers? What kind of software do they write? Why do they use C? Did they even choose C or is it a requirement?