Why C Programming Is Awesome




Sponsors:
Dev Mountain Coding Bootcamp

Other Links:
Check out my tutorials, blogs and more at my website
-~-~~-~~~-~~-~-

In this video I give a quick nod to C and why learning C is never going to be a bad thing.

source

31 thoughts on “Why C Programming Is Awesome”

  1. 2:25 its not c code that run. its machine code. why they would put c code to mars rover that will compile it and run it. that will usee too much power lol. it's allready compiled its not c code. it can be any language that have been compiled. binary code would be exacly same when its do same thing(not true) it can be build many ways and other language could even do smaller and faster code lol

  2. Program in C, they said. It will be fun, they said.
    -A seasoned programmer that has audited so many spaghetti code in C.

  3. European space agency is invested in micropython. It works great for my microcontrollers, I cant see why not for curiosity ;). time critical code should be c functions exposed to the python interpreter.

  4. I like C / C++ because I always know how it will be translated to machine code, I know when objects get destroyed or created. I can manage my own memory and do a lot of stuff that is mot possible or requires worl arounds on higher level

  5. Radiation from space is not going to hurt C# any more than it would hurt C code. C is great because it's fast and lean. But I disagree with some of your other points.

  6. My story: First, I learned Java, then z80 assembly (wrote a little minesweeper game for the TI-83+), now C++, let's see if/when I come to C.

  7. I love C and also hate C. Two words: Segmentation Fault. Yeesh. What programmer hasn't had the experience of spending hours trying to figure out what went wrong only to realize it was a simple fix all along. Just goes to show how stack traces are crucial to development.

  8. C is a good language for things it is good for, but I wouldn't want to for instance code a website with it. There are better tools for that, like to many other things.

  9. lol, nowadays people write high level apps on super mainframes treating tons of data with .NET, python, java, you name it
    even if you were coming with something like c+ I would still tell you that you're a fucking looser
    it's 2017 dude, get the memo

  10. The problem with people is described in C. It goes like this: Bill bought a car, after few cycles passed, he decided to buy a brand new one and throw old one away without recycling it. Bill bought many products and threw them away without much thought. Now we have dumping grounds everywhere, climate warming heating the plain and people ignore it by throwing segfaults and restarting the badly written program they designed. Peace, research Flat Earth (Eric Dubay). C knows its flat!

  11. When I need speed and/or simplicity I use ASM. Interrupt handlers work, work reliably and are very simple in ASM. At least mine are. I use an ASM Framework that's a series of macros and preprocessors to enforce type and scope rules. When I want portability and maintainability across platforms, I use C.

  12. C is a beautiful language, dont forget GTK framework, and the KDE environments built based on C. 🙂 and of course so much more….

  13. Our development team came from c backgrounds and we were tasked to develop this simulation program in Java. It had to use the CPU as efficiently as possible and also run for weeks under high stress conditions. Long story short, we had multiple years of growing pains learning you DID have to actively worry about Java's memory management.

    We would constantly fight the introduction of memory leaks. Some small seemingly innocuous fix in one part of the code would cause a slow memory leak only noticeable after running for several days. This ended up with everyone having to learn memory profiling tools. Often, the root cause was difficult to locate and you could easily spend multiple days attempting to figure it out.

  14. Our development team came from c backgrounds and we were tasked to develop this simulation program in Java. It had to use the CPU as efficiently as possible and also run for weeks under high stress conditions. Long story short, we had multiple years of growing pains learning you DID have to actively worry about Java's memory management.

    We would constantly fight the introduction of memory leaks. Some small seemingly innocuous fix in one part of the code would cause a slow memory leak only noticeable after running for several days. This ended up with everyone having to learn memory profiling tools. Often, the root cause was difficult to locate and you could easily spend multiple days attempting to figure it out.

  15. Perl is based on C too.
    Apart from their source code, C is to almost all modern languages what Latin is to European languages.

  16. Goddamit I hate how many times C and Assembly are overestimated. I mean overestimated in being hard (not useful!). They are easy. I had a background in Basic and moved to C pretty easy at 11 and Assembly at 13. Entire generation of young programmers was built upon Assembly in 80s.

  17. 3:24 *Many kernels are also responsible for ensuring that faulty programs do not interfere with the operation of others, by denying access to memory that has not been allocated to them*

    https://msdn.microsoft.com/en-us/library/windows/desktop/ff818516(v=vs.85).aspx

    #include <Windows.h>
    FindWindow();
    GetWindowThreadProcessId();
    OpenProcess();
    ReadProcessMemory();
    WriteProcessMemory();

    https://msdn.microsoft.com/en-us/library/windows/desktop/ms679303(v=vs.85).aspx

Leave a Reply