Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
What I find fascinating about this trilogy is that C, C++, and C# didn't simply replace one another. Each made a different trade-off between control, performance, safety, and developer productivity.
But here's a question:
If you were starting a completely new project today, would you choose C for maximum control, C++ for zero-cost abstractions, or C# for developer productivity?
And more importantly, what would make you choose one over the other?
I'd love to hear some real-world reasoning, not just language preferences! 🚀
(Also: this is my first post under DEVengers, hope it resonates with you all!)
A good reminder of C, C# and C++. New information for me surprisingly, so it's good to see the history behind it.
I think it's also leave noting about the security aspects of it such as various attacks if you didn't write "correctly". For example, the most common is overflow attack if you written "C" in an un-optimized way.
Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
Really enjoyed this, Dhruv. I don’t code in C, C++ or C#, so I never knew the history behind them until today. I didn’t know C# came about because Microsoft walked away from Java after the Sun lawsuit, or that C++ started as “C with Classes” at the same Bell Labs where C was made. Such an educative post, thanks for sharing!
Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
Backend engineer exploring distributed systems, AI, developer tools, and security. I build things to test ideas and write about what worked, what failed, and what I learned.
Great read! I think Ken Thompson and Unix deserve a mention here too. Rewriting Unix in C was a huge step in making operating systems portable. Maurice J. Bach's The Design of the UNIX Operating System is also worth mentioning. It goes pretty deep into System V and shows how many of those early design ideas around processes, memory and file systems are still relevant today.
The lineage is a useful reminder that languages carry trade-offs forward, not just syntax. It would be interesting to map one recurring boundary—memory ownership, abstraction cost, or interoperability—across all three ecosystems. That makes the historical connection actionable for someone choosing where safety or control should live in a new system.
Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
The control-vs-safety framing ties the three generations together nicely — C trusts the programmer with raw pointers, C++ layers abstractions on that model, and C# pushes the safety boundary into a managed runtime. That same trade-off keeps showing up in Electron: the main process gets near-Node power and native access, while renderers are deliberately sandboxed so a compromised web layer cannot touch the file system. Really each generation is arguing over who pays the cost — runtime safety overhead versus programmer discipline — and it never disappears, it just moves up the stack.
Solo developer building practical CLI tools for Linux auditing and B2B data extraction. Creator of Vaultcheck and NPILift. I write about silent failures, false green lights, and infrastructure reliabi
The Electron case is the cleanest modern instance of that trade: since Electron 12 contextIsolation defaults on and since Electron 20 renderers are sandboxed by default, so the C#-style managed boundary stopped being opt-in and became the default.
The bill just moves to IPC — everything across the bridge is structured-cloned, so bulk data has to cross in one message instead of streaming through calls, which is C++'s zero-cost-abstraction argument reappearing at a process boundary.
None of the three generations made the cost disappear. They only chose who signs for it.
Fascinating walk through computing history. Seeing how C, C++, and C# evolved to balance low-level control with developer ergonomics really shows how architectural decisions made decades ago still anchor our modern infrastructure.
For a service that mostly talks to a database, I’d pick C#. For a small tool where I want predictable cleanup at scope exit, I’d lean C++. The vector example makes RAII easy to see, but a file handle would make the difference even clearer. If the parser returns early after a bad row, I want to be able to point to the exact object that closes the file.
The framing of each language as a different trade-off rather than a ranking is what makes this work. If I had to pick one for a brand-new project tomorrow, I would take C#: the managed runtime and garbage collector remove the whole class of memory bugs that C leaves on the developer, and for most web or app work that safety is worth more than the raw control C offers. The RAII section was the clearest explanation of why C++ still earns its place in game engines and browsers, though — that part alone made the history worth reading.
I measure AI coding claims in public. LGTM — Let's Get the Measurements: real runs, real numbers, receipts. Every article is an experiment I actually ran. Books & packs: aheadkit.gumroad.com
Genuinely enjoyed the three-act structure, but I have to ask — the "Jeremiah Johnson Nod" heading with absolutely nothing under it is the most C thing in the entire piece. No safety net, no explanation, just a heading and the void. My pick is C#, by the way, and only because I'm too soft for manual memory management and too impatient for template error messages.
Interesting read, and a nice framing. I’ll answer your question from a slightly odd seat, though, because I don’t write any of the three. I run things written in them.
From that side, the decision isn’t about memory safety at all. It’s about what the build produces. A C or C++ binary drops into a scratch or distroless image with almost nothing around it, so the only patch surface is my own code. A C# service ships a runtime, and that runtime is its own patch surface, its own cold start and its own memory floor before my application has done a thing.
So my pick would be C#, for the reason your post doesn’t quite reach: I’d rather carry the runtime and take the productivity, because the operational cost of a runtime is predictable and the cost of a memory bug in production isn’t.
Solo developer building practical CLI tools for Linux auditing and B2B data extraction. Creator of Vaultcheck and NPILift. I write about silent failures, false green lights, and infrastructure reliabi
The three still meet at one seam worth testing: P/Invoke. C#'s bool marshals as a 4-byte Win32 BOOL by default, so a callee declared as C _Bool reads the low byte and the rest is whatever the register held -- declare the parameter byte or [MarshalAs(UnmanagedType.U1)] before you lose an afternoon to it. Same reason a std::string cannot cross: neither C++ nor .NET ships a standard ABI, so the portable seam is extern "C" with char* plus an explicit length on one side and IntPtr + Marshal.PtrToStringUTF8 on the other. First move on any such bug is sizeof the struct on both sides and compare, not step through a debugger.
This is great, I know how we started from C in 1st year to C# in 3rd year. But still since I'm using java for competitive programming I got used to it and never returned to C family!
Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
Cool, nothing wrong in it! I've always seen C# completing all needs that Java has and Cpp didn't. And somehow you know I got my 1st internship and some months later a job in .NET. So, I'm used to this family!😄
Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
After over 8 years of Quality Assurance in the Video Game Industry, I have decided to start my own Dev Journey and start creating my own games instead of testing or playing them.
Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
A Natural storyteller, developed IT professional , travelled the road of ERP,CRM now exploring the pathways of AI-capturing the technical world from an artistic lense,making digital footprints
Full-Stack Developer (Flutter / Laravel) & UI/UX Designer. Passionate about building robust, offline-first applications and bridging the gap between clean code and beautiful design. Always exploring n
Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
JavaScript enthusiast with a growing passion for Python. I love exploring the world of programming, experimenting with code, and discovering new ways to turn ideas into reality.
Upcoming Trainee Engineer @ Simform 🚀
Building, experimenting, and writing my way through tech.
AI • Web • Open Source • Challenges
If I find something interesting, I'll probably write about it. 😄
Location
Vadodara, Gujarat, India
Education
B.Tech in Computer Engineering @ Dharmsinh Desai University
Go and Rust are relatively young wrt to C/C++.
The comparison in terms of market penetration is unfair.
In fact, only last year 2025, Rust has been chosen as an experiment for Linux Kernel.
The problem with Go and Rust is sometimes the exotic syntax...
We're a place where coders share, stay up-to-date and grow their careers.
💬 Let's make this interesting!
What I find fascinating about this trilogy is that C, C++, and C# didn't simply replace one another. Each made a different trade-off between control, performance, safety, and developer productivity.
But here's a question:
If you were starting a completely new project today, would you choose C for maximum control, C++ for zero-cost abstractions, or C# for developer productivity?
And more importantly, what would make you choose one over the other?
I'd love to hear some real-world reasoning, not just language preferences! 🚀
(Also: this is my first post under DEVengers, hope it resonates with you all!)
This is awesome Dhruv! First DEVenger post!
A good reminder of C, C# and C++. New information for me surprisingly, so it's good to see the history behind it.
I think it's also leave noting about the security aspects of it such as various attacks if you didn't write "correctly". For example, the most common is overflow attack if you written "C" in an un-optimized way.
Otherwise, a good introduction! Good work :)
That's the thing with C that Denis Ritchhie trusted devs that they'll do their job properly!😂
One of my experiment is back to the C vibeing instead of rust
Sir, we'd like to hear more about your experiment!
Will be soon around Nov 25. A vim like linux markdown first CLI editor.
Looking forward to it Sir!
Have A Great Day!
Really enjoyed this, Dhruv. I don’t code in C, C++ or C#, so I never knew the history behind them until today. I didn’t know C# came about because Microsoft walked away from Java after the Sun lawsuit, or that C++ started as “C with Classes” at the same Bell Labs where C was made. Such an educative post, thanks for sharing!
Thanks for the read!
Have A Great Day!
Loved the way it's explained through storytelling how the C family of languages has shaped the software world.
Great read! I think Ken Thompson and Unix deserve a mention here too. Rewriting Unix in C was a huge step in making operating systems portable. Maurice J. Bach's The Design of the UNIX Operating System is also worth mentioning. It goes pretty deep into System V and shows how many of those early design ideas around processes, memory and file systems are still relevant today.
The lineage is a useful reminder that languages carry trade-offs forward, not just syntax. It would be interesting to map one recurring boundary—memory ownership, abstraction cost, or interoperability—across all three ecosystems. That makes the historical connection actionable for someone choosing where safety or control should live in a new system.
Sure Sir, that'd make it more helpful and interesting but I wrote this with my knowledge as a student!😅
The control-vs-safety framing ties the three generations together nicely — C trusts the programmer with raw pointers, C++ layers abstractions on that model, and C# pushes the safety boundary into a managed runtime. That same trade-off keeps showing up in Electron: the main process gets near-Node power and native access, while renderers are deliberately sandboxed so a compromised web layer cannot touch the file system. Really each generation is arguing over who pays the cost — runtime safety overhead versus programmer discipline — and it never disappears, it just moves up the stack.
The Electron case is the cleanest modern instance of that trade: since Electron 12
contextIsolationdefaults on and since Electron 20 renderers are sandboxed by default, so the C#-style managed boundary stopped being opt-in and became the default.The bill just moves to IPC — everything across the bridge is structured-cloned, so bulk data has to cross in one message instead of streaming through calls, which is C++'s zero-cost-abstraction argument reappearing at a process boundary.
None of the three generations made the cost disappear. They only chose who signs for it.
Fascinating walk through computing history. Seeing how C, C++, and C# evolved to balance low-level control with developer ergonomics really shows how architectural decisions made decades ago still anchor our modern infrastructure.
For a service that mostly talks to a database, I’d pick C#. For a small tool where I want predictable cleanup at scope exit, I’d lean C++. The vector example makes RAII easy to see, but a file handle would make the difference even clearer. If the parser returns early after a bad row, I want to be able to point to the exact object that closes the file.
The framing of each language as a different trade-off rather than a ranking is what makes this work. If I had to pick one for a brand-new project tomorrow, I would take C#: the managed runtime and garbage collector remove the whole class of memory bugs that C leaves on the developer, and for most web or app work that safety is worth more than the raw control C offers. The RAII section was the clearest explanation of why C++ still earns its place in game engines and browsers, though — that part alone made the history worth reading.
Genuinely enjoyed the three-act structure, but I have to ask — the "Jeremiah Johnson Nod" heading with absolutely nothing under it is the most C thing in the entire piece. No safety net, no explanation, just a heading and the void. My pick is C#, by the way, and only because I'm too soft for manual memory management and too impatient for template error messages.
Interesting read, and a nice framing. I’ll answer your question from a slightly odd seat, though, because I don’t write any of the three. I run things written in them.
From that side, the decision isn’t about memory safety at all. It’s about what the build produces. A C or C++ binary drops into a scratch or distroless image with almost nothing around it, so the only patch surface is my own code. A C# service ships a runtime, and that runtime is its own patch surface, its own cold start and its own memory floor before my application has done a thing.
So my pick would be C#, for the reason your post doesn’t quite reach: I’d rather carry the runtime and take the productivity, because the operational cost of a runtime is predictable and the cost of a memory bug in production isn’t.
The three still meet at one seam worth testing: P/Invoke. C#'s bool marshals as a 4-byte Win32 BOOL by default, so a callee declared as C _Bool reads the low byte and the rest is whatever the register held -- declare the parameter byte or [MarshalAs(UnmanagedType.U1)] before you lose an afternoon to it. Same reason a std::string cannot cross: neither C++ nor .NET ships a standard ABI, so the portable seam is extern "C" with char* plus an explicit length on one side and IntPtr + Marshal.PtrToStringUTF8 on the other. First move on any such bug is sizeof the struct on both sides and compare, not step through a debugger.
Clean architecture is easy to maintain in a slide deck; the real test is how gracefully the system degrades under cascading production failures.
Minimizing abstraction layers and owning your critical runtime path will always outperform adding more third-party glue.
三幕式的结构写得很清楚,把三位前辈的工作和各自的取舍串起来读很有意思,“信任程序员”和“零成本抽象”这两条规则的对比也很到位。
This is great, I know how we started from C in 1st year to C# in 3rd year. But still since I'm using java for competitive programming I got used to it and never returned to C family!
Cool, nothing wrong in it! I've always seen C# completing all needs that Java has and Cpp didn't. And somehow you know I got my 1st internship and some months later a job in .NET. So, I'm used to this family!😄
Also, bro good for you joining DEVengers!
Thanks bro!
knowing c# from unity made it easier to learn c++ for unreal engine.
Great, I have huge respect for those who are in game dev cause I've tried it before and its very hard that I chose SDE domain!😅
Have A Great Day!
Thanks for the time travel experience .
Reading about C and manual memory reminds me of auditing old machine scripts at The Printing World. One wrong byte and the whole packaging run halts.
This is amazing, I really appreciate it. ❤️❤️❤️❤️
Given the popularity of www, developed on NeXT, and Apple's OSX, Objective C deserves discussion in this story.
It does sir, but I wrote this one with my knowledge as a student on these 3. And I haven't tried objective C yet!
Have A Great Day!
C++
Pretty cool! Reminds me of my college days :) Currently using C++ for game dev!
Great Di, Actually as I said earlier game dev sounds very tempting to me but I went through some tutorials on codecademy and realized its not for me😅.
But hats off to you! I'd love to try out your work!😄
Nice overview, an entertaining read!
Good! Now I am learning C
Am new here
Welcome!🎉
C
Go and Rust are relatively young wrt to C/C++.
The comparison in terms of market penetration is unfair.
In fact, only last year 2025, Rust has been chosen as an experiment for Linux Kernel.
The problem with Go and Rust is sometimes the exotic syntax...