Let’s say you decide to learn programming. You have two options. Either use the education system (college or courses) or become self-taught. In the first case, you will learn the programming languages that are imposed on you. The education system (universities, colleges, courses) uses the “modern” development stack. Because what matters to them is what can later bring income to companies and you in life, and taxes to the state. They are part of the system and that’s how it works. Or because they want to get certificates from industry giants and use everything in their implementation - from development tools to ideology. Only a very few colleges and courses specializing in a very narrow field, such as embedded devices, can teach you the C language.
If you choose to learn programming on your own, the first thing you will do is go to the Internet to determine where to start and what you need to learn today. Naturally, you will find there a lot of articles and posts on the topic of “what programming language to learn in X year”. And they will contain a detailed or not very detailed comparison of “modern” languages. But you are unlikely to find the C language among them. Moreover, almost all of these languages will have the intention of being “C replacements”. Naturally, you will choose a new, powerful, and promising language that will replace the “dying C”, while you “look to the future”. You will never find phrases like “Rust is a replacement for Zig” or vice versa, they will all be “replacements for C”. And by doing this they are trying to hide the C language. We have seen why the C programming language is hidden.
But suddenly one wonderful day you came across a post with the words “give C language a try”, or, if you are over 40, you remembered where you started learning programming as a child before you started writing all this “SaaS garbage”. And you thought “well, okay, what if there is something, here is nothing to lose anyway”. And you started learning C, simultaneously integrating into the C community. And then you discover, to your surprise, that the C language is simple and effective, applicable everywhere, and continues to develop. And the community is kind, not pompous, without hype, and buzzing with interesting projects. You realized that the C language is not dying and is not going to die, as the “gurus” on youtube taught you and representatives of the “modern” language communities argued with foam at the mouth. And that it is unlikely that C will be able to replace anything in the near future. It’s as if you have found “your home” again, something you have been looking for a long time, but could not express in words. You have returned to the roots. And this is why the C language is gold.
Look for your “gold”, never give up. When you find it, you will know for sure that this is it. Thanks for reading!
Old enough to have learnt BASIC and assembly in the 80s as well as Turbo Pascal (in CP/M) and C, all self-taught. I still code in C as of today.
My first programming language book I read was about C in early 2000s, the Kernighan and Ritchie one in fact. But never programmed anything else than some exercises. I begun way tooo late to learn and do something with real languages unfortunately, as focused on scripting and some other languages for temporary usage.
I know old scripting (bash, awk) but nothing about python :-/
Back then I was using AutoHotkey for most stuff (before it was the hot shit it is now, before gamers knew about it). With the switch to Linux I needed something and that’s when I learned about Python 2 in 2008. I do lot of stuff in Bash too nowadays.
Python is really not hard to learn or use. The only awkward thing it has to me is, the logic and grouping of code is indentation based… Python even comes by default with Linux, and similar to Bash you just need the
#!/usr/bin/env python3and can use the entire language and its features like Bash is using the commandline tools. I highly recommend to learn some basics of Python, because this will be useful for the rest of your life. Even if you don’t end up writing yourself much, you can read and confirm others code are not doing stupid stuff or make changes as you wish.#!/usr/bin/env python3 print("hello world")