@@MrWendijohanes I hate web dev, I'd rather make a website in C than with those kiddy scripting languages, even then I wouldn't even make a website in the first place
C is really awesome! The creators of C (Ken Thompson and Dennis Ritchie) deserve so much respect, they literally built the foundation of modern programming. Thanks Chris Hawkes!
Although Ken Thompson was around and undoubtably had some input, he is not considered one of the creators of C, and *certainly* not listed first. C really was Denis Ritchie's baby.
I've used C for going on 40 years now... I still like how it works. One advantage is that it's small. I don't think there are even 100 keywords to the whole thing. I like that simplicity. The standard libraries are well tested and robust. C has proved to be a most useful tool.
I’ve been studying compsci for a while now (since middle school) and one of the biggest game changers for me was reading “The C Programming Language” written by the creators themselves. Absolutely legendary book.
I honestly think that pulling up embedded systems / microcontrollers, kernel development and the age of the language as the main strong points of C does the language a disservice, because these are the things perhaps most commonly associated with C and the usual reasons why C is shunted to the side and disregarded when it comes to discussing or choosing programming languages. The need to have "an intimate knowledge of how a computer is actually operating" is also not a reason for C's awesomeness, and neitehr is the need to manage the program's memory. Saying that C is great because other languages or their implementations are built on C also, in my opinion, serves little purpose - if we, as humanity, have taken tool X and our knowledge of it, and with it we've built tools Y and Z that make our jobs easier and help us achieve what we want with less effort, why would we go back to using tool X for those same jobs? I think you've missed a good deal of why C is actually awesome to the programmer. It's well-designed - simple, consistent and with a high degree of semantic coherence. It does a good job of telling the programmer what the code does, without making it overly complicated. It doesn't make the programmer work hard for that information, at least definitely not as hard as with some other languages (_cough_ c++ _cough_ sorry, I have a cold); it doesn't obscure its low-level workings, but it also doesn't prematurely force implementation details on the programmer. It's flexible - you can do both operating system kernel implementation, and high-level application programming, all in the same language, without much effort at all. It's so old and still used today for all sorts of tasks because of how well it has stood the test of time and how strong its design has turned out to be. It's easy to pick up, learn, and do stuff with, even without the "intimate knowledge" about CPUs and memory, because nearly every high school kid is smart enough to write a C program that asks for 2 integers, adds them together, and spits out the result, during their very first class about the language. And probably some other neat things about C that I've forgotten about. Cool video idea, but I think a lot of people in the industry really miss out on the true elegance of C. The bland powerpoint slides with a mouse pointer racing across them didn't help the video, either :P
Oh and i have a very simple project if someone wants to help transition from screenspace only to calculations off the screens borders at a very slight loss in FOV for resolving cleanness purposes. Example: 1936x1089 internal borders cut off 1920x1080 actual pixel density Not supersampling... Any help?
I have to say, although C can be a pain to deal with and it is certainly not my first choice to use for anything, I am really glad that it was my first language. You learn all about building your own data structures from scratch, manually managing memory, etc. and then you feel like a master when you go into languages like ruby and python and realize that you don't need to do any of that stuff :)
Please cite your source of information? Which microcontrollers, specifically? Because BASIC was the only language those MCUs supported? I am really curious to learn more about this.
If you're into embedded systems design C is probably the language you should start with because most microcontrollers use it, for example your Arduino uses what's essentially C programming.
C is a big pain compared to something like Python though. Granted C is great and lower level when compared to Python but how easy would it be to make a quick script like what I produce in this video with Python using C? ua-cam.com/video/g8b4Ex81bWw/v-deo.html
Just discovered this and going to have to respectfully disagree with you here Chris (Hawkes). I would love to give every developer in the world basic exposure to C; especially those who primarily work in interpreted or typeless languages. C teaches and enforces good programming habits. I've been in a rotational engineering/development role at a fortune 500 company for a couple years, and the number of questionable production systems I've already found is crazy. The issue is always something like no regard for data type, poor memory management, rushed overall data structure, or straying to far from the underlying computer science. These are all things that you cannot get away with easily in C. C really forces you to evaluate your programming design and refine it to be what you need. So yes, while I agree that I certainly wouldn't use C for every application, I strongly believe it's important to understand and respect how to build everything you develop at the C-programming level. There are also definitely some developers out there that would benefit from gaining an appreciation of C before they put yet another loosely-constructed, over-complicated java(script) app into production. Sorry for the long response; I get really passionate about this.
I'm definitely biased, because I got my upbringing in C and have literally replaced the Linux system memory allocator with C code before, but I still feel like lack of understanding of the things C brings to the table is a huge issue in the modern development world.
C has the perfect level of abstraction from the hardware. It's high-enough to be 100% portable, and human-readable, but it's low-enough to be efficient for performance- and memory use sensitive applications. And, it's much easier to understand other people's code than in something like C++, where you can even overwrite operators (what I call an encryption / obfuscation scheme, rather than a helpful language feature). With C99 and later, you can also create an excellent object-oriented runtime, way better than C++.
You can overwrite operators, feel free to use this feature carefully and relevantly. I personally find the C not abstracting enough for me, I don't want to have memory management concerns when I'm dealing with high levels works, as long as you have to manage strings and collections, C will force you to handle memory manually whatever the level of abstraction you are coding into. C++ allows you to forget about it, doing exactly what you would do manually, maybe even better.
Why did Stroustrup call the C language to be obsolete then? I honestly don't get it. Can somebody please elaborate? I wasted my time learning JavaScript (for millennials) when what I really wanted is to learn a logic language that gave me control over real machines, real hardware.
brian lucore C is a powerful language with a lot of flexibility, but it doesn't protect you from yourself. If you don't program defensively and comment your code thoroughly, it can be a real pain to debug later. The more a high-level language takes care of for you, the more it can limit you options. So C gives you a lot of freedom, but at the price of your having to take responsibility for more things.
C is easier to learn and faster to compile compared to C++. You have forgotten to mention one of the most important benefits of C that is a proper stable ABI.
C is not easier to learn than C++. C++ comes with some features that lower the minimum-learning-barrier to entry. References for example. If you want to write a function that changes its arguments outside its scope, you have to use pointers. Which is one more thing you have to learn. That and streams, stuff in STL, function (and operator) overloading, templates to name a few other features. Also, being able to define functions inside structs without having to know what function pointers are once again makes it easier to pick up.
@@SArthur221 I disagree. "C is not easier to learn than C++. C++ comes with some features that lower the minimum-learning-barrier to entry. References for example. If you want to write a function that changes its arguments outside its scope, you have to use pointers. Which is one more thing you have to learn." First off you have to learn pointers in C++ too so that makes no sense, and second, it's not that hard to do. You can either pass by reference, or return the data you want to edit. Ex: //First way int weridfunction(int a); int main(void){ int outofscope = weridfunction(1); //gives outofscope a value of 2 } int weridfunction(int a){ return ++a; } //Second way void weridfunction(int* a); int main(void){ int outofscope = 1; weridfunction(outofscope); //gives outofscope a value of 2 } void weridfunction(int* a){ ++a; } Im pretty sure this will compile properly, but Im a little tired right now so eh. "That and streams, stuff in STL, function (and operator) overloading, templates to name a few other features. Also, being able to define functions inside structs without having to know what function pointers are once again makes it easier to pick up." All of that is more complex things to learn, you complained about learning pointers (Not that hard of a topic to pick up imo) but learning templates overloading and such is easier?
@@lightskinche You forgot to dereference A in the 2nd weridfunction. It should be ++(*a) not ++a; But what you're saying is true. It literally took me a week to basically master Pointers. They're only hard if you can't imagine the boxes in your head.
Faster to compile if you use templates in C++, but if you don't use template you will rewrite a lot of code. What you gain in compilation time, you lose it in sustainability.
import static java.lang.System.out; public class Hello { public static void main(String[] args) { out.println("Hello World of C - Greetings from Mx. :) " + "C,C++,Java, C# etc... they all are awesome languages "+ " Learn them all and have fun :)
I have worked in c, java and a host of other languages. but I still prefer c. you can do just about anything in c, and you can do it efficiently and clean. it's very efficient once you know it.
No. Not really. I mostly spend my time in Java nowadays (as it is the language of choice in many larger business oriented systems) but I rarely do actul object orientation even here. OOP has it's uses, but IMHO it often complicates things rather than simplifies them. Abstractions are useful, but when they get in the way of seeing the actual problem at hand, they are simply put just in the way of the solution.
I learned C as my first programming language and it's so efficient that I have no idea why anyone would even bother with OOP. And with the right text editor like Vim you can type C reeeeaally fast.
OOP keeps your code and data together in one place. Allows more complex abstractions (e.g. Tensors, Atoms). Procedural programming is all about how to compute - you give the computer all the steps, functional programming is all about what to compute - you state the problem and make the computer figure himself how to solve it, OOP is somewhere in between. Also no paradigm is perfect. Different problems ask for different solutions. I personally don't understand pure OOP, but it must be working for the majority, given the popularity of C# and Java.
I started coding in BASIC. It originally had no subroutines and long programs were sometimes referred to as "spaghetti code". Subroutines were an improvement as they allowed you to organize code into logical functions. However, sometimes you have several logical functions that work with a couple of shared variables. C offered no way to organize those. Enter C++. I loved C, but C++ is the next progression of being able to organize your program making it easier to organize, understand and use.
***** The question is what is the definition of _quality code_. To the extent that organization and readability is key, you just can't do as well in raw C (for the reasons I outlined above). That isn't to say you can't write quality code in C--I did for many years. But I can give my code a higher level of organization and many operations are much easier to read using classes.
Flash Man I have never programmed in a non OOP language. I am learning C++ now, and I have a friend who told me if I know C++, then I know C. Is this true? And also, what is wrong with OOP? I am just curious lol.
Kyle Stankovich Yes, that is true for the most part as C++ is basically C with a number of extensions to the language. And there is absolutely nothing wrong with OOP. OOP is a better way to organize your application code. Is it slower? It can be only because it makes it easier to do more complex things. And sometimes you need to be fairly proficient to know everything that is happening within the compiler. But I'm a guy who held on to assembly programming because I loved the hand optimizations. As software gets more complex and hardware gets faster, you'll need to move on if you want your skills to be marketable.
I started doing a little bit of Python. Then, after going to college (still studying) and learning how to create algorithms in pseudocode and to program in C, has made me a much better overall programmer. I still have a lot to learn, but I can't wait to keep going and keep getting better.
C also just says, “Screw type safety, I want to do this myself!” giving you the freedom to do things far more efficiently, but at the risk of shooting yourself in the foot if you don’t know what you’re doing.
I'm a huge type nerd and proponent of Rust and Typescript. But absolutely, there is time and a place! I love Rust's approach of putting unsafe{} around such code. I love safety by default with an easy escape hatch for when you need to do the fiddly bits.
A great C Programming book is C Programming Language 2nd ed. By Kernighan, W. B. & Ritche, M. D. 256 Pages The C Answer Book 2nd ed. By Tondo, L. C. & Gimpel, E. S. This the answer guide for the above 201 Pages. Also your correct you need to know something about computers. A good book for that is The Architecture of Computer Hardware, Systems Software & Networking By Englander, I. Great video.
I agree with the majority of this presentation regarding C. I don't think the primary reason for choosing C for the Curiosity Rover is for reducing overhead. NASA has many of their own higher level languages for their own use. C is chosen because none of the other languages can easily do I/O with computer chips, robotic devices, and device drivers. There are exceptions since you do have chips such as Arduino will allow higher level support. I suspect there are hundreds of device vendors that NASA contracts with that requires programmatic communication across low-level ports which cannot be done with other higher level languages. I've personally worked with Satellite contract jobs that were similar to what I described. Regardless, this was a good and informative presentation. One last thing too add, another good reason to learn C is that all of the higher level languages you mentioned are based on C/C++.
when i was studying computer engineering in 2003/2004 first grade they taught us C and C++, those days i loved C programming language and the logic of the language. After that year one of the teachers pushed us to learn C# and i dont know why but i couldnt easily adapt it and like it as much as i liked C/C++. later on in the masters degree we focused on Java and i became a Java developer. Now after all those years I'm teaching myself C programming language and i confess it's really amazing.
Yeah but you lose the sense of how it works. Like Java creating pointers without even letting the programmer know that you just created a pointer. Don't worry about garbage collector or the dreaded pointers. Here's an example that I got from Github it says----- The following code shows some Java object references. Notice that there are no *'s or &'s in the code to create pointers. The code intrinsically uses pointers. Also, the garbage collector (Section 4), takes care of the deallocation automatically at the end of the function. public void JavaShallow() { Foo a = new Foo(); // Create a Foo object (no * in the declaration) Foo b = new Foo(); // Create another Foo object b=a; // This is automatically a shallow assignment -- // a and b now refer to the same object. a.Bar(); // This could just as well be written b.Bar(); // There is no memory leak here -- the garbage collector // will automatically recycle the memory for the two objects. } Slower. Because the language takes responsibility for implementing so much pointer machinery at runtime, Java code runs slower than the equivalent C code
I think if you are serious about programming you should take an assembly language class. Even if you never touch it again, it gives you a much better understanding of what is going on at the CPU level.
shouting back. When 32-bit first became readily accessible (in the form of the 386-DX), and GUIs were in their infancy, C programmers wrote code that made such (limited) devices useful. Speed was paramount. Disk-thrash was death. Keep it lean. I rode that wave (and I miss it pretty badly.)
C is to modern programming languages what Latin is to almost all European languages today. It's the basis, and everything shows its influence, including Perl.
@@brainletexplains8271 yeah, in the UK you can take a GCSE course in Latin (this is a high school level qualification not sure what the American equivalent will be)
@@BlazertronGames I can't do much in pure JavaScript but that doesn't mean I just can't use it. I can still program in JavaScript using frameworks. Just try a framework and see the magic happen.
At 6:39, what causes those spikes in job demand? Is it simply big layoffs in companies or is it just by chance that hundreds (if not thousands) of C jobs become in demand at one time?
When personal computers ran off of floppy disks, program efficiency was much more important. I liked C programming because it was easy to see how each statement would be translated into machine language. I could write a C program, compile it, pick at the assembly code, and end up with a small and fast program. I actually had a C program produce a standalone distributable binary that was 453 bytes long (of course it used stdio from a console library, and a system library). A program that was only 453 bytes to download was nice when our modems maxed out at 1200 baud.
I totally agree with you as an ex C developer of a great many years standing. After a 10 year+ "break" from coding/development I have recently come back to it after my wifes death to take advantage of the Arduino revolution. Sadly, I cannot find a "RAW COMPILER" any more. The last one I used commercially was VC 4 or 5, and then it all moved on to C++, and now of course C#, but both of these rely as you righty pointed out on endless different libraries and frameworks, all of which you need to be pretty familair with if you are to be able to code in these environments. I think the introduction of the MS Intellisense is the best indicaton of this need, qas without it I suspect that few programmers would ever really get anything done without understanding all of these arcane library canyons.
2:06 C is radiation hardened??? Are there special libraries that have redundancy or error checking built-in that could detect a radiation induced hardware fault? One of C's biggest strength (and potential pitfalls) is it's use of pointers and pointer arithmetic. Conditional pre-processor directives can give your c-code tremendous flexibility, but can also make tracking down some bugs a lot more difficult. Managing memory can get a little tedious. No exception handling though. "C is for cookie, that's good enough for me." Cookie Monster
I think what he meant was that a spacecraft has to endure conditions which make a large onboard library, which would have to substitute for an internet based set of system call procedures, inadvisable. Smaller means lighter and easier to shield from radiation, and being compiled directly to optimized machine code makes the program smaller. In the Apollo project, when the effects of solar and cosmic radiation on memory and logic circuits were less understood, they played it safe with “macrame” memory for the onboard invitational computer. Each bit of this “read only” memory was a donut shaped magnetic core, penetrated by driving wires for each address containing a 1 in a given bit position of a word, and by a sense wire for that bit position. These wires were hand knotted for each copy of the computer. Radiation couldn’t move a wire from one core to another!
If you want to program anything low level in C you ALWAYS need to read a hardware's (MCPUs, sensors, interfaces...) user manuals (UM) first. This is how you learn hardware and it is a lot of fun if you like to read. I learned basic C while cross compiling ARM programs on Linux. To me it was easy to (a) learn ARM by reading MCPU's UM, to (b) interact with sensors integrated alongside MCPU on the same MCU, by reading MCU's UM or to (c) program external sensors only connected to the same embedded system that MCU is on by studying UM for that sensors... So I was able to learn on how to do basic stuff with embedded boards, but... On the other hand it was very hard to (a) find any study material on how to actually show anything on LCD and to create a graphical library, or to (b) write C drivers for Linux in order for Linux to be able to recognize the embedded system or in other words firmware that is ran on that same embedded system. This is where you see flaws of Linux, and you feel how Linux knowledge is intentionally hidden in order to sell it through seminars, certification...
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.
What is awesome about C, is the fact that your "framework" is not a runtime, perhaps you are powered by means of an Library, in general, most of the time, your framework is the very same machine you are programming to. IMHO.
C, unlike ISO C++ plus STL, has a very thin compile-time and run-time. I'm assuming that's partly why NASA picked C. After all if it's an embedded thing that you're debugging you need to fully understand what the relevant parts of the hardware and your code are doing and how they're interacting and that gets harder the more layers, abstractions and complexity you have in between. Was it C.A.R. Hoare who in one of his old papers posed the rhetorical question of what point there is in using a tool that is more complicated than the problem you're trying to solve. The language isn't supposed to be there to add accidental complexity to the situation.
C isn't the language to do your day to day drive, but when a task is too complicated to do with other higher level languages C is the one you will jump to and thank the gods of programming for making it exist and not having to deal with assembly.
Languages are converted to LLVM IR anyway. IR is optimized and the result is dumped to binary. Does it really make that big difference what Lang was used?
Chris I have a question, I am very confused with C? Because the C version which is being taught for my cs50 intro course the syntax which is written during the class course wont be accepted by the Apple x-code IDE, it gets rejected. I noticed when I wrote "get_int" on the variable line it is flagged red and is rejected by the compiler. I am not sure but I think the version the x-code uses is c99? I don't know anything about the different versions of C I am now hearing about this. Chris, which is the standard version of C everyone is using which is best recommended because this is so complicated to learn now. I don't know the version of C the Harvard CS50 intro course is using I am trying to find out. But how can I pick the right version of C? Any help would be most appreciated, thank you.
I do all things in C. Once you learn how to wield your '.dll' and '.so' files you don't even need scripting languages for any reason, you can make small configuration/high level adjustments in one compilation to the dynamic/shared library and just compile that from C too. It's not sexy, but eventually I got bored with sexy and realized pure and simple is the only way to go... I do use the '.cpp' extension and compile as C++ though, so that I can use C++ style struct declarations and very occasional operator overloading. The biggest shortcoming of C is lack of good introspection. Can't easily turn an enum value into a string, or list the members of a struct by index, etc, but once you're willing to write your own metaprogram to generate a few .h files, that can pretty much be solved as well.
3:34 For more than 30 years? C was developed at Bell Laboratories in 1972 by Dennis Ritchie. He also worked with Ken Thompson to develop UNIX. This video was released in 2016, and that was 44 years after it was created. It's already 46 years old.
TinyC ompiler is reasonable for begineers. I have a general math ebook with most of the practical math functions found on scientific calculators written in the basic ansi C language.
I started working on a video game with my friends, and sometimes wish that I used C, but I used C++ because there was supposed to be other people helping me with the programming and they only knew C++, so I used C++, but it turned out they didn’t understand the code well enough and it was too complicated, so I’m doing it alone. Although I am using it as half C and half C++ (like using classes and cout, but using a lot of struct based stuff and little C++ only stuff as well).
NASA would build their own very efficient robust runtime libraries for their robots in a manner where code execution is deterministic. Also, applications would not use malloc -- not directly anyway. Everything must be controllable. Garbage collection would bea BIG NO NO on the Mars Rover.
If I want to build a watch I use a magnifying glass and tiny tools, screws and cogs. If I want to build a bridge I use large steel beams, bolts and steel cables. Nobody would use watchmaker tools to build a bridge or vice versa. So it´s all about the purpose which tools (or programming language) I use. I agree that C is a beautiful language. But I wouldn´t want to use C to build a large website or a major Enterprise Data Application.
@@realchrishawkesWhat is the point of this statement. No one disputes the power or beauty of the C language. It is just that you wouldn´t choose C to build a big data-driven application or a large website like you wouldn´t choose a tiny brush that would be well suited for painting tiny details in a portrait to paint the walls of your house.
I don’t know how to code in C yet, but hearing all these testimony makes me want to start programming class immediately. Can someone please recommend a good book?
43 keywords to make up the world. the problem with C is not that it is complicated. the problem with c is that it is too simple. and many people have a hard time wrapping their brains around simple. :)
The problem is that you need to drill a hole but are given a stick, a string, a woodplate and a stone. Nothing more simple than the things you are given and one can certainly do it with the things you are given, but you can also just use a prebuild drill, it may not be optimal for your use case, but chances are it is the same with your selfmade one, if your not experienced enough.
The first point doesn't make much sense, because we would all be using assembly because C was built with it. C is NOT portable, you need to make a lot of code changes to make a code run in all systems and, you could see java running in the Mars thing (you just need to implement the jvm in it) but you would never see it because java has too much of a overhead for it, it has nothing to do with portability. I still think that C is a good programming language and it's between assembly (really low level) and higher level languages. Best language for machine programming
It depends on what you’re doing. If you’re into embedded design C is probably the only language worth knowing. I do a lot of embedded design at least 95% of the code I have written in the last 20 years was in C. As a matter of fact, a lot of small processors in eight and 16 bit bus with, and millions of those things are used in everyday products , have no compilers in any other language available. If you’re interested in that kind of work it is 100% C.
1. turn off distractions,
2. plug into computer ibm model m keyboard
3. write some C and feel like a real programmer again.
This is exactly what I need to do after experience severe burnout with web dev bullsh*t
@@MrWendijohanes I hate web dev, I'd rather make a website in C than with those kiddy scripting languages, even then I wouldn't even make a website in the first place
@@MrWendijohanes had this same problem, really helped me to recover actually
@@freedomgoddess Would Web Assembly be a part of the solution?
Install FreeBSD never install a DM or DE/TWM buys C a modern approach. The path to god hood
C is really awesome!
The creators of C (Ken Thompson and Dennis Ritchie) deserve so much respect, they literally built the foundation of modern programming.
Thanks Chris Hawkes!
Although Ken Thompson was around and undoubtably had some input, he is not considered one of the creators of C, and *certainly* not listed first. C really was Denis Ritchie's baby.
I've used C for going on 40 years now... I still like how it works. One advantage is that it's small. I don't think there are even 100 keywords to the whole thing. I like that simplicity. The standard libraries are well tested and robust. C has proved to be a most useful tool.
That's awesome.
Sir, why don't you make videos about C?
@@dzvsow2643 not everyone wants to do UA-cam...
I’ve been studying compsci for a while now (since middle school) and one of the biggest game changers for me was reading “The C Programming Language” written by the creators themselves. Absolutely legendary book.
32 keywords
Perl is based on C too.
Apart from their source code, C is to almost all modern languages what Latin is to European languages.
Great example.
What about Lisp and Delphi/Pascal?
yeah but the API to extend perl modules in C is a huge macro world mess
This comment
you know about germanic languages?
"Why using default powerpoint templates is also awesome."
Ease of use.
I used to fly hang gliders. Now I program in C and use lots and lots of pointers. Dangerous fun and nobody gets hurt.
I C that you really like this language.
Even though he is not a "deep C" guy..
I like this language because it's like a C of things to do with it.
I C what you did there
I dunno what u mean I can't C#
I didnt c that 1 coming
The reason why I like C the best is simple.
What you "C" is what you get!
When you get into C, you get into the Hell of debugging...
I like C anyway...
I dunno... I don't know of any programming language that doesn't need debugging...
Depends a lot of your style of writing code. I program C very defensively, so it's very rare for me to encounter a nightmare bug.
@@baruchben-david4196 GCC points to the location of the error and just go fixit, if not rethink.
@@amalirfan Yeah, I've found GCC's error messages to be very helpful.
Those are the nice errors. The worst are the subtle ones that seems to work for a while, like UB or memory corruption.
I honestly think that pulling up embedded systems / microcontrollers, kernel development and the age of the language as the main strong points of C does the language a disservice, because these are the things perhaps most commonly associated with C and the usual reasons why C is shunted to the side and disregarded when it comes to discussing or choosing programming languages. The need to have "an intimate knowledge of how a computer is actually operating" is also not a reason for C's awesomeness, and neitehr is the need to manage the program's memory. Saying that C is great because other languages or their implementations are built on C also, in my opinion, serves little purpose - if we, as humanity, have taken tool X and our knowledge of it, and with it we've built tools Y and Z that make our jobs easier and help us achieve what we want with less effort, why would we go back to using tool X for those same jobs?
I think you've missed a good deal of why C is actually awesome to the programmer. It's well-designed - simple, consistent and with a high degree of semantic coherence. It does a good job of telling the programmer what the code does, without making it overly complicated. It doesn't make the programmer work hard for that information, at least definitely not as hard as with some other languages (_cough_ c++ _cough_ sorry, I have a cold); it doesn't obscure its low-level workings, but it also doesn't prematurely force implementation details on the programmer. It's flexible - you can do both operating system kernel implementation, and high-level application programming, all in the same language, without much effort at all. It's so old and still used today for all sorts of tasks because of how well it has stood the test of time and how strong its design has turned out to be. It's easy to pick up, learn, and do stuff with, even without the "intimate knowledge" about CPUs and memory, because nearly every high school kid is smart enough to write a C program that asks for 2 integers, adds them together, and spits out the result, during their very first class about the language. And probably some other neat things about C that I've forgotten about.
Cool video idea, but I think a lot of people in the industry really miss out on the true elegance of C. The bland powerpoint slides with a mouse pointer racing across them didn't help the video, either :P
thank you for sharing this.
DX12 has entered the chat.
Hardware abstraction tho..
A.I. is coming.
Oh and i have a very simple project if someone wants to help transition from screenspace only to calculations off the screens borders at a very slight loss in FOV for resolving cleanness purposes.
Example:
1936x1089 internal borders cut off
1920x1080 actual pixel density
Not supersampling...
Any help?
@@realchrishawkes
Gabe Newell is watching.
Completely agree
I have to say, although C can be a pain to deal with and it is certainly not my first choice to use for anything, I am really glad that it was my first language. You learn all about building your own data structures from scratch, manually managing memory, etc. and then you feel like a master when you go into languages like ruby and python and realize that you don't need to do any of that stuff :)
fun fact about the mars curiosity rover: there are microcontrollers on it that were programmed in BASIC
Please cite your source of information? Which microcontrollers, specifically? Because BASIC was the only language those MCUs supported? I am really curious to learn more about this.
If you're into embedded systems design C is probably the language you should start with because most microcontrollers use it, for example your Arduino uses what's essentially C programming.
C is a big pain compared to something like Python though. Granted C is great and lower level when compared to Python but how easy would it be to make a quick script like what I produce in this video with Python using C? ua-cam.com/video/g8b4Ex81bWw/v-deo.html
The main language for Arduino is C++
www.arduino.cc/en/Reference/HomePage
only found out about c and love having this much control, btw im a java developer
Just discovered this and going to have to respectfully disagree with you here Chris (Hawkes). I would love to give every developer in the world basic exposure to C; especially those who primarily work in interpreted or typeless languages. C teaches and enforces good programming habits. I've been in a rotational engineering/development role at a fortune 500 company for a couple years, and the number of questionable production systems I've already found is crazy. The issue is always something like no regard for data type, poor memory management, rushed overall data structure, or straying to far from the underlying computer science. These are all things that you cannot get away with easily in C. C really forces you to evaluate your programming design and refine it to be what you need. So yes, while I agree that I certainly wouldn't use C for every application, I strongly believe it's important to understand and respect how to build everything you develop at the C-programming level. There are also definitely some developers out there that would benefit from gaining an appreciation of C before they put yet another loosely-constructed, over-complicated java(script) app into production. Sorry for the long response; I get really passionate about this.
I'm definitely biased, because I got my upbringing in C and have literally replaced the Linux system memory allocator with C code before, but I still feel like lack of understanding of the things C brings to the table is a huge issue in the modern development world.
Back in the 80s, even user applications were written in C. You can use C for low level development to high level development.
C has the perfect level of abstraction from the hardware. It's high-enough to be 100% portable, and human-readable, but it's low-enough to be efficient for performance- and memory use sensitive applications.
And, it's much easier to understand other people's code than in something like C++, where you can even overwrite operators (what I call an encryption / obfuscation scheme, rather than a helpful language feature). With C99 and later, you can also create an excellent object-oriented runtime, way better than C++.
You can overwrite operators, feel free to use this feature carefully and relevantly. I personally find the C not abstracting enough for me, I don't want to have memory management concerns when I'm dealing with high levels works, as long as you have to manage strings and collections, C will force you to handle memory manually whatever the level of abstraction you are coding into. C++ allows you to forget about it, doing exactly what you would do manually, maybe even better.
Why did Stroustrup call the C language to be obsolete then? I honestly don't get it. Can somebody please elaborate?
I wasted my time learning JavaScript (for millennials) when what I really wanted is to learn a logic language that gave me control over real machines, real hardware.
screw object orientation though
"I'm not a deep C guy." #punny
I did ~ C that coming
brian lucore C is a powerful language with a lot of flexibility, but it doesn't protect you from yourself. If you don't program defensively and comment your code thoroughly, it can be a real pain to debug later. The more a high-level language takes care of for you, the more it can limit you options. So C gives you a lot of freedom, but at the price of your having to take responsibility for more things.
C is easier to learn and faster to compile compared to C++. You have forgotten to mention one of the most important benefits of C that is a proper stable ABI.
nope. you'll update glibc and everything will breaks :)
C is not easier to learn than C++. C++ comes with some features that lower the minimum-learning-barrier to entry.
References for example. If you want to write a function that changes its arguments outside its scope, you have to use pointers. Which is one more thing you have to learn.
That and streams, stuff in STL, function (and operator) overloading, templates to name a few other features. Also, being able to define functions inside structs without having to know what function pointers are once again makes it easier to pick up.
@@SArthur221 I disagree.
"C is not easier to learn than C++. C++ comes with some features that lower the minimum-learning-barrier to entry.
References for example. If you want to write a function that changes its arguments outside its scope, you have to use pointers. Which is one more thing you have to learn."
First off you have to learn pointers in C++ too so that makes no sense, and second, it's not that hard to do. You can either pass by reference, or return the data you want to edit.
Ex:
//First way
int weridfunction(int a);
int main(void){
int outofscope = weridfunction(1); //gives outofscope a value of 2
}
int weridfunction(int a){
return ++a;
}
//Second way
void weridfunction(int* a);
int main(void){
int outofscope = 1;
weridfunction(outofscope);
//gives outofscope a value of 2
}
void weridfunction(int* a){
++a;
}
Im pretty sure this will compile properly, but Im a little tired right now so eh.
"That and streams, stuff in STL, function (and operator) overloading, templates to name a few other features. Also, being able to define functions inside structs without having to know what function pointers are once again makes it easier to pick up."
All of that is more complex things to learn, you complained about learning pointers (Not that hard of a topic to pick up imo) but learning templates overloading and such is easier?
@@lightskinche You forgot to dereference A in the 2nd weridfunction. It should be ++(*a) not ++a; But what you're saying is true. It literally took me a week to basically master Pointers. They're only hard if you can't imagine the boxes in your head.
Faster to compile if you use templates in C++, but if you don't use template you will rewrite a lot of code. What you gain in compilation time, you lose it in sustainability.
#include
int main() {
printf("Hello Everyone!");
return 0;
}
#include
int main()
{
puts("hello");
return 0;
}
import static java.lang.System.out;
public class Hello {
public static void main(String[] args) {
out.println("Hello World of C - Greetings from Mx. :)
" +
"C,C++,Java, C# etc... they all are awesome languages
"+
" Learn them all and have fun :)
");
} // end main
} // end class.
i hate optimizations so use O0 in gcc
static inline void __write_this_for_lolz(const char *s)
{
asm volatile(
"xorl %eax, %eax;
"
"mov $1, %edi;
"
"mov $1, %eax;
"
"mov $5, %edx;
"
"mov %eax, %ebx;
" );
register const char __attribute__((unused)) *p asm("esi") = s;
asm("syscall");
}
int main(void)
{
__write_this_for_lolz("hello");
return 0;
}
#include
void main()
{
int ans;
printf("
\t Is the user saying hi to me?");
printf("
1>Yes 2>No");
printf ("
Answer:") ;
scanf("%d", &ans);
if (ans==1)
{
printf("
\t\tHeelooooooo!! ) ;
}
else if (ans==2)
{
printf("aww,sad noises");
}
else
{
printf("Please enter between 1 and 2 only") ;
main() ;
}
}
10 PRINT "Basic beats y'all"
20 GOTO 10
I have worked in c, java and a host of other languages. but I still prefer c. you can do just about anything in c, and you can do it efficiently and clean. it's very efficient once you know it.
You don't find yourself missing OOP? Some people say that it's hard to organize big projects without OOP features.
+sakalava47 DOP
No. Not really. I mostly spend my time in Java nowadays (as it is the language of choice in many larger business oriented systems) but I rarely do actul object orientation even here. OOP has it's uses, but IMHO it often complicates things rather than simplifies them. Abstractions are useful, but when they get in the way of seeing the actual problem at hand, they are simply put just in the way of the solution.
Interesting. Thanks for explaining.
I learned C as my first programming language and it's so efficient that I have no idea why anyone would even bother with OOP. And with the right text editor like Vim you can type C reeeeaally fast.
OOP keeps your code and data together in one place. Allows more complex abstractions (e.g. Tensors, Atoms). Procedural programming is all about how to compute - you give the computer all the steps, functional programming is all about what to compute - you state the problem and make the computer figure himself how to solve it, OOP is somewhere in between.
Also no paradigm is perfect. Different problems ask for different solutions. I personally don't understand pure OOP, but it must be working for the majority, given the popularity of C# and Java.
I started coding in BASIC. It originally had no subroutines and long programs were sometimes referred to as "spaghetti code". Subroutines were an improvement as they allowed you to organize code into logical functions. However, sometimes you have several logical functions that work with a couple of shared variables. C offered no way to organize those. Enter C++. I loved C, but C++ is the next progression of being able to organize your program making it easier to organize, understand and use.
***** The question is what is the definition of _quality code_. To the extent that organization and readability is key, you just can't do as well in raw C (for the reasons I outlined above). That isn't to say you can't write quality code in C--I did for many years. But I can give my code a higher level of organization and many operations are much easier to read using classes.
Flash Man I have never programmed in a non OOP language. I am learning C++ now, and I have a friend who told me if I know C++, then I know C. Is this true? And also, what is wrong with OOP? I am just curious lol.
Kyle Stankovich Yes, that is true for the most part as C++ is basically C with a number of extensions to the language. And there is absolutely nothing wrong with OOP. OOP is a better way to organize your application code. Is it slower? It can be only because it makes it easier to do more complex things. And sometimes you need to be fairly proficient to know everything that is happening within the compiler. But I'm a guy who held on to assembly programming because I loved the hand optimizations. As software gets more complex and hardware gets faster, you'll need to move on if you want your skills to be marketable.
I started doing a little bit of Python. Then, after going to college (still studying) and learning how to create algorithms in pseudocode and to program in C, has made me a much better overall programmer. I still have a lot to learn, but I can't wait to keep going and keep getting better.
C also just says, “Screw type safety, I want to do this myself!” giving you the freedom to do things far more efficiently, but at the risk of shooting yourself in the foot if you don’t know what you’re doing.
Kind of... C still imposes big restrictions on your typecasting with strict aliasing, etc.
I'm a huge type nerd and proponent of Rust and Typescript. But absolutely, there is time and a place! I love Rust's approach of putting unsafe{} around such code. I love safety by default with an easy escape hatch for when you need to do the fiddly bits.
for Embedded systems C remains the language of choice
A great C Programming book is C Programming Language 2nd ed. By Kernighan, W. B. & Ritche, M. D. 256 Pages
The C Answer Book 2nd ed. By Tondo, L. C. & Gimpel, E. S. This the answer guide for the above 201 Pages.
Also your correct you need to know something about computers. A good book for that is The Architecture of Computer Hardware, Systems Software & Networking By Englander, I.
Great video.
But ANSI C is more modern than K&R C.
The 2nd edition is ANSI C.
2nd edition is ansi c though.
I'm at a intermediate level coding in C and mostly doing it as a hobby and it's awesome. One of teachers on YT I really appreciate is Kris Jordan.
Thanks for sharing
@@realchrishawkes And Eskils Steenberg more than two hours master class C video.
I agree with the majority of this presentation regarding C. I don't think the primary reason for choosing C for the Curiosity Rover is for reducing overhead. NASA has many of their own higher level languages for their own use. C is chosen because none of the other languages can easily do I/O with computer chips, robotic devices, and device drivers. There are exceptions since you do have chips such as Arduino will allow higher level support. I suspect there are hundreds of device vendors that NASA contracts with that requires programmatic communication across low-level ports which cannot be done with other higher level languages. I've personally worked with Satellite contract jobs that were similar to what I described. Regardless, this was a good and informative presentation. One last thing too add, another good reason to learn C is that all of the higher level languages you mentioned are based on C/C++.
when i was studying computer engineering in 2003/2004 first grade they taught us C and C++, those days i loved C programming language and the logic of the language. After that year one of the teachers pushed us to learn C# and i dont know why but i couldnt easily adapt it and like it as much as i liked C/C++. later on in the masters degree we focused on Java and i became a Java developer. Now after all those years I'm teaching myself C programming language and i confess it's really amazing.
Taught*
@@Defaulttemporaryusername yeah fixed it. hope you are happy now. (for your concern, english is not my native language)
What did Ms. Java say to Mr. C?
....
"Stop objectifying me!"
Damn, Mr.C has no class!
Caio A. i get this joke.
Ba dum... C.
C++ objectifies C in my opinion. C++ is C with Classes. What do you think ?
Yeah but you lose the sense of how it works. Like Java creating pointers without even letting the programmer know that you just created a pointer. Don't worry about garbage collector or the dreaded pointers. Here's an example that I got from Github it says-----
The following code shows some Java object references. Notice that there
are no *'s or &'s in the code to create pointers. The code intrinsically uses pointers. Also,
the garbage collector (Section 4), takes care of the deallocation automatically at the end
of the function.
public void JavaShallow() {
Foo a = new Foo(); // Create a Foo object (no * in the declaration)
Foo b = new Foo(); // Create another Foo object
b=a; // This is automatically a shallow assignment --
// a and b now refer to the same object.
a.Bar(); // This could just as well be written b.Bar();
// There is no memory leak here -- the garbage collector
// will automatically recycle the memory for the two objects.
}
Slower. Because the language takes responsibility for implementing so
much pointer machinery at runtime, Java code runs slower than the
equivalent C code
A shout out to assembly language. .. the most fun and the most interesting language.
writing code in assambly will tech you how computer really work
Yes!!!!
In Addition your gonna learn how to cry real good
I think if you are serious about programming you should take an assembly language class. Even if you never touch it again, it gives you a much better understanding of what is going on at the CPU level.
@@burnttoast111 true, it will make you be more grateful
All you have to do was follow the damn train, Cj
shouting back. When 32-bit first became readily accessible (in the form of the 386-DX), and GUIs were in their infancy, C programmers wrote code that made such (limited) devices useful. Speed was paramount. Disk-thrash was death. Keep it lean. I rode that wave (and I miss it pretty badly.)
C is to modern programming languages what Latin is to almost all European languages today. It's the basis, and everything shows its influence, including Perl.
Except we still use C :P
What modern programming language do you use in embedded systems?
@@Myvoetisseer I still use Perl.
many people still use latin.
@@brainletexplains8271 yeah, in the UK you can take a GCSE course in Latin (this is a high school level qualification not sure what the American equivalent will be)
I love C. It's the first language that I am familiar with.
C is nice, I can't do anything in it, but it influenced a lot of syntax for other languages. So I like the syntax.
@@BlazertronGames I can't do much in pure JavaScript but that doesn't mean I just can't use it. I can still program in JavaScript using frameworks. Just try a framework and see the magic happen.
Behold!
2[(char[]){'a','b','c'}] = '9';
for (int i = 0; i < 3; i++) printf( "%c
", (i - i)[&((&(i[!(i & 1) ? (char[]){'a', 'b', 'c'} : "efg"]))[i - i])]);
At 6:39, what causes those spikes in job demand? Is it simply big layoffs in companies or is it just by chance that hundreds (if not thousands) of C jobs become in demand at one time?
Just an innocent Java user passing by, please don't kill me xD
Takes shotgun out pumps it System.println.out this (pow!)
HHHHHHHHHHHHH
We’re going to garbage collect the garbage collectors!
@Steven Tsakiris Based and Christpilled. Holy C is God's programming language.
Printf("die die!");
No reason you can't program in c-style, and just reach for c++ features when they're convenient.
Compile times though! C compiles way faster.
+cbbuntz
Since when?
Once you start including lots of libraries with templates and stuff, C++ compilation times get *slow*.
this is why you use namespaces and don't bother with boost.
Those facts about C, like how many employees require knowledge of C, inspired me with awe!
i feel like a true programmer when using c and assembley
ALX brought me here.
"segmentation fault"
The only people who fear that are the lazy bums who can't be bothered to do debug properly.
Use GDB. Problem solved.
oh shit, here we go again HAHAHA
"Exception in thread "main" in Java.lang...
"
core dumped, illegal seek, fgets succes ... some of the other legends that streets wont forget
I wrote my first script over 40 lines in C yesterday.
I'm learning it as a hobby but knowing the syntax
of C makes Python incredibly easy to navigate.
When personal computers ran off of floppy disks, program efficiency was much more important. I liked C programming because it was easy to see how each statement would be translated into machine language. I could write a C program, compile it, pick at the assembly code, and end up with a small and fast program. I actually had a C program produce a standalone distributable binary that was 453 bytes long (of course it used stdio from a console library, and a system library). A program that was only 453 bytes to download was nice when our modems maxed out at 1200 baud.
Thanks for sharing that!
C is the Mother of all programming Languages.
All hail C!
*Stares in Assembly*
@Aurora Paisley, opcode and instructions (x86 or arm) is a programming language too. Assembly looks almost the same like that.
Hey.
You forgot to mention DOOM
fck yeah
Quake
I totally agree with you as an ex C developer of a great many years standing. After a 10 year+ "break" from coding/development I have recently come back to it after my wifes death to take advantage of the Arduino revolution.
Sadly, I cannot find a "RAW COMPILER" any more. The last one I used commercially was VC 4 or 5, and then it all moved on to C++, and now of course C#, but both of these rely as you righty pointed out on endless different libraries and frameworks, all of which you need to be pretty familair with if you are to be able to code in these environments. I think the introduction of the MS Intellisense is the best indicaton of this need, qas without it I suspect that few programmers would ever really get anything done without understanding all of these arcane library canyons.
I needed as an old school C programmer coming back to programming
I miss the dependency bit. Java and .net are dependent on external libs that gets updated which can be cumbersome and risky.
2:06 C is radiation hardened??? Are there special libraries that have redundancy or error checking built-in that could detect a radiation induced hardware fault?
One of C's biggest strength (and potential pitfalls) is it's use of pointers and pointer arithmetic. Conditional pre-processor directives can give your c-code tremendous flexibility, but can also make tracking down some bugs a lot more difficult. Managing memory can get a little tedious. No exception handling though.
"C is for cookie, that's good enough for me." Cookie Monster
I think what he meant was that a spacecraft has to endure conditions which make a large onboard library, which would have to substitute for an internet based set of system call procedures, inadvisable. Smaller means lighter and easier to shield from radiation, and being compiled directly to optimized machine code makes the program smaller.
In the Apollo project, when the effects of solar and cosmic radiation on memory and logic circuits were less understood, they played it safe with “macrame” memory for the onboard invitational computer. Each bit of this “read only” memory was a donut shaped magnetic core, penetrated by driving wires for each address containing a 1 in a given bit position of a word, and by a sense wire for that bit position. These wires were hand knotted for each copy of the computer. Radiation couldn’t move a wire from one core to another!
I’m so new to C language, this is cool!
mother of all languages
you mean FORTRAN?
FORTRAN is the shitty father who left when you were 2.
Well, I use it daily.It is still used by a lot of scientists. Those fellows in CERN .... C is a derivative of the ideas in FORTRAN.
So C is the son of the shitty father that left?
Today even C is considered obsolete.
assembly, not c teaches you how your computer works.
Could you allow community contributions so your videos can be captioned?
Thank you for your contribution, I updated the video to allow it.
What did Mr. C say to the tourist asking for directions?
Let me give you some pointers
Lol
If you want to program anything low level in C you ALWAYS need to read a hardware's (MCPUs, sensors, interfaces...) user manuals (UM) first. This is how you learn hardware and it is a lot of fun if you like to read. I learned basic C while cross compiling ARM programs on Linux. To me it was easy to (a) learn ARM by reading MCPU's UM, to (b) interact with sensors integrated alongside MCPU on the same MCU, by reading MCU's UM or to (c) program external sensors only connected to the same embedded system that MCU is on by studying UM for that sensors...
So I was able to learn on how to do basic stuff with embedded boards, but... On the other hand it was very hard to (a) find any study material on how to actually show anything on LCD and to create a graphical library, or to (b) write C drivers for Linux in order for Linux to be able to recognize the embedded system or in other words firmware that is ran on that same embedded system.
This is where you see flaws of Linux, and you feel how Linux knowledge is intentionally hidden in order to sell it through seminars, certification...
Sounds like fun
@@realchrishawkes Call me weird, but when not gaming, or hanging out with friends, it's one of m favorite ways to kill an evening. 😂
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.
Wow, a positive video about a programming language, where most people agree with the presenter in the comments.
What is awesome about C, is the fact that your "framework" is not a runtime, perhaps you are powered by means of an Library, in general, most of the time, your framework is the very same machine you are programming to. IMHO.
C is awesome. If there would be only language for all tasks. People would pick C.
5:51 What about assembly? It's better if you want to know how the computer really works.
Program in C, they said. It will be fun, they said.
-A seasoned programmer that has audited so many spaghetti code in C.
C really needs to add namespaces. It will save SOOO many headaches
@@flutterwind7686 Definitely a feature from C++ that I wish they'd incorporate into C. **sad sigh** maybe one day.... I hope...
C, unlike ISO C++ plus STL, has a very thin compile-time and run-time. I'm assuming that's partly why NASA picked C. After all if it's an embedded thing that you're debugging you need to fully understand what the relevant parts of the hardware and your code are doing and how they're interacting and that gets harder the more layers, abstractions and complexity you have in between. Was it C.A.R. Hoare who in one of his old papers posed the rhetorical question of what point there is in using a tool that is more complicated than the problem you're trying to solve. The language isn't supposed to be there to add accidental complexity to the situation.
1:25!!! More reason for me to stay pumped and glad to have taken the first steps in learning C as my first language! That's freaking awesome.
C isn't the language to do your day to day drive, but when a task is too complicated to do with other higher level languages C is the one you will jump to and thank the gods of programming for making it exist and not having to deal with assembly.
C is a beautiful language, dont forget GTK framework, and the KDE environments built based on C. :) and of course so much more....
metaldownm Slight disagree: Gtk is horrible and kde is most likely c++ because it uses the c++ library qt
Some really superficial reasoning here. Grade: C.
I think learning c is very important because all libraries that other languages provide it would make it easier to use API well.
🔥 If you're learning to code, check out my website 👉 codehawke.com/all_access.html 🔥
Learn more 👉 ua-cam.com/video/fpp215OSRV0/v-deo.html
I'm actually not, just C++ for now
very good
which vs code them is that in the thumbnail?
I use C whenever I can
Debugging in C is hard that’s what makes you a better programmer in other languages
It is
Languages are converted to LLVM IR anyway. IR is optimized and the result is dumped to binary. Does it really make that big difference what Lang was used?
Clr and jvm languages? Not much.
Wich books are the best to learn the basics of C programming nowadays in 2020?
I do som bat-file scripts, are there any language that works without any compiler and that IT-department cant block.
Chris I have a question, I am very confused with C? Because the C version which is being taught for my cs50 intro course the syntax which is written during the class course wont be accepted by the Apple x-code IDE, it gets rejected. I noticed when I wrote "get_int" on the variable line it is flagged red and is rejected by the compiler. I am not sure but I think the version the x-code uses is c99? I don't know anything about the different versions of C I am now hearing about this. Chris, which is the standard version of C everyone is using which is best recommended because this is so complicated to learn now. I don't know the version of C the Harvard CS50 intro course is using I am trying to find out. But how can I pick the right version of C? Any help would be most appreciated, thank you.
C is for cookie, that's good enough for me!
Please don't flame me, I just couldn't resist that joke....
I do all things in C. Once you learn how to wield your '.dll' and '.so' files you don't even need scripting languages for any reason, you can make small configuration/high level adjustments in one compilation to the dynamic/shared library and just compile that from C too. It's not sexy, but eventually I got bored with sexy and realized pure and simple is the only way to go...
I do use the '.cpp' extension and compile as C++ though, so that I can use C++ style struct declarations and very occasional operator overloading.
The biggest shortcoming of C is lack of good introspection. Can't easily turn an enum value into a string, or list the members of a struct by index, etc, but once you're willing to write your own metaprogram to generate a few .h files, that can pretty much be solved as well.
3:34 For more than 30 years? C was developed at Bell Laboratories in 1972 by Dennis Ritchie. He also worked with Ken Thompson to develop UNIX. This video was released in 2016, and that was 44 years after it was created. It's already 46 years old.
TinyC ompiler is reasonable for begineers. I have a general math ebook with most of the practical math functions found on scientific calculators written in the basic ansi C language.
which is better c++ or c. And could you tell me why? i want to begin learning one of these and i want to get a better understanding of computers.
I started working on a video game with my friends, and sometimes wish that I used C, but I used C++ because there was supposed to be other people helping me with the programming and they only knew C++, so I used C++, but it turned out they didn’t understand the code well enough and it was too complicated, so I’m doing it alone.
Although I am using it as half C and half C++ (like using classes and cout, but using a lot of struct based stuff and little C++ only stuff as well).
cool, i want to learn C for same reason, i'm trying to build an algorithm for playing Snake and python has time issues.
So you're using C++, you should never mix C code with C++ code its considered bad practice
@@126644 why is it bad? I literally see C++ as C just with OOP and i use it as that, I program it pretty much like C. Never had any issues with it.
NASA would build their own very efficient robust runtime libraries for their robots in a manner where code execution is deterministic. Also, applications would not use malloc -- not directly anyway. Everything must be controllable. Garbage collection would bea BIG NO NO on the Mars Rover.
If I want to build a watch I use a magnifying glass and tiny tools, screws and cogs. If I want to build a bridge I use large steel beams, bolts and steel cables. Nobody would use watchmaker tools to build a bridge or vice versa. So it´s all about the purpose which tools (or programming language) I use. I agree that C is a beautiful language. But I wouldn´t want to use C to build a large website or a major Enterprise Data Application.
But the lower parts are all because of C
@@realchrishawkesWhat is the point of this statement. No one disputes the power or beauty of the C language. It is just that you wouldn´t choose C to build a big data-driven application or a large website like you wouldn´t choose a tiny brush that would be well suited for painting tiny details in a portrait to paint the walls of your house.
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.
I don’t know how to code in C yet, but hearing all these testimony makes me want to start programming class immediately.
Can someone please recommend a good book?
43 keywords to make up the world.
the problem with C is not that it is complicated. the problem with c is that it is too simple. and many people have a hard time wrapping their brains around simple. :)
The problem is that you need to drill a hole but are given a stick, a string, a woodplate and a stone.
Nothing more simple than the things you are given and one can certainly do it with the things you are given, but you can also just use a prebuild drill, it may not be optimal for your use case, but chances are it is the same with your selfmade one, if your not experienced enough.
For myself I find the simplest concepts are often the hardest to grasp.
I love it too. "Till this day"!!!!
The first point doesn't make much sense, because we would all be using assembly because C was built with it.
C is NOT portable, you need to make a lot of code changes to make a code run in all systems and, you could see java running in the Mars thing (you just need to implement the jvm in it) but you would never see it because java has too much of a overhead for it, it has nothing to do with portability.
I still think that C is a good programming language and it's between assembly (really low level) and higher level languages.
Best language for machine programming
It depends on what you’re doing. If you’re into embedded design C is probably the only language worth knowing. I do a lot of embedded design at least 95% of the code I have written in the last 20 years was in C. As a matter of fact, a lot of small processors in eight and 16 bit bus with, and millions of those things are used in everyday products , have no compilers in any other language available. If you’re interested in that kind of work it is 100% C.
I don't know why i like C but i absolutely love it. Maybe the pointer stuff or maybe the memory managing powers.
Am I the only one who thinks that the Dispose-pattern used by most managed languages is *literally* manual resource management?
I recently just started learning C language. It is really awesome. Thanks for the video 🤗
It's a small language that allows you to do low level and high level stuff.....what more do you need?
Cool reflections, thank you for the video.
what are c-users views on c plus plus?
God of all programming languages
The father of them all
To C .... or not to C? That is the question.
Oh well, I guess I will try it with the help of the book of C Primer Plus sixth edition.
Your Legendary
I C where you got that PP presentation template from lol
Thanks for watching!
>C isn't going anywhere
Prepare yourself...
Jai is coming
Thank you for sharing!
Who is Jai?
Is he a person or a language?
is it marketable to get a job to learn system programming and with the c language?