General > General Technical Chat

How many people code in C these days, and if so, why?

<< < (40/99) > >>

engrguy42:
For some reason people are compelled to label stuff either GOOD or BAD. And it's never the case.

C is wonderful, it's served millions well for many years. It has pro's, and it has con's.

C++ is wonderful, it's served millions well for many years. It has pro's, and it has con's.

Python is wonderful, it's served millions well for many years. It has pro's, it has con's.

C# is wonderful, it's served millions well for many years. It has pro's, it has con's.

And so on.

Nothing in this universe has ever been perfect. 

And the fact that every tool you've ever used has pro's and con's means that anyone can always point to a con if they want to discredit the tool. But for those who have used the tool successfully for many years, those cons are likely irrelevant.

coppice:

--- Quote from: bd139 on May 09, 2020, 11:39:47 pm ---
--- Quote from: coppice on May 09, 2020, 11:26:24 pm ---
--- Quote from: bd139 on May 09, 2020, 10:56:48 pm ---See my earlier rant. It’s dying on its arse. Even the stalwart C# guys are disenchanted. Not because of the platform but the complete mismanagement of it for 20 years.  Honestly wish I hadn’t wasted a chunk of my brain on it.

--- End quote ---
I haven't touched C# for some time. It wouldn't surprise me to find its being mismanaged. It was mostly created for political purposes, so its continued funding would depend on the success of that political ploy. What kind of mismanagement has there been? Poor compiler? Poor libraries?

--- End quote ---

Best bet is hit my previous rant on it https://www.eevblog.com/forum/chat/how-many-people-code-in-c-these-days-and-if-so-why/msg3053124/#msg3053124

--- End quote ---
So your main issues are with .net? That has been a disaster for everyone using MS products, not just C# developers. The original versions were a complete joke.

maginnovision:
My first experience with .net was porting a game written in visual basic 6.0 over to C#. They had a tool to sort of auto port the thing. After it did that it only took 8 hours to fix everything that was broken and double the size of the executable. I haven't really touched it since but I know devs who have and don't have any problems with it. It's all about what you're used to.

IDEngineer:

--- Quote from: floobydust on May 09, 2020, 11:23:33 pm ---C is just a high-level assembly language
--- End quote ---
...which is both its strength and its weakness, like all good and powerful tools. An idiot can do stupid things and hurt themselves with any tool, and the "less safe" the tool the more likely this becomes. But in the hands of someone competent, few language tools are more powerful or flexible and truly competent craftsmen do not want a bunch of protective features getting in the way.

The better the craftsman, the fewer restrictions he wants (and needs) on his tools. A screwdriver with PlastiDip on its tip may seem "safer", but its usefulness is severely hampered. A soldering iron that "doesn't get too hot" might seem "safer" but might also have very few applications. Both of these might be suitable for neophytes, but not for most people on this site.

Before someone says "But look at all the bugs in [your favorite example] from [your least favorite large software company]" as a supposed example of how C can have bugs even when written by "the best", remember that sheer company size does not guarantee that they hire only competent software people. I've met some surprisingly ignorant software folk who sported business cards with names like "Microsoft" and "Adobe".

As noted herein by others, this is another example of "The right tool for the job". To which I would add, "...while also considering the person DOING the job". C is an excellent choice when the author is competent. The less competent the user, the more hand-holding and safety nets and babysitting they need. Thankfully, there are languages which provide such things when the author is someone who needs such protection.

rsjsouza:
Another one that does almost exclusively assembly and C due to small memory footprint on the platforms I work. A tiny fraction is done with what I call an alkost naked C++. Right tool for the job.

I do a lot of batch and shell scripting, as well as javascript and some python on the bigger systems.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod