General > General Technical Chat

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

<< < (19/99) > >>

IanB:

--- Quote from: nctnico on May 06, 2020, 09:03:29 pm ---C# is MS only. People seem to use Python for that kind of applications nowadays. Personally I don't know anyone who is writing software using C#.

--- End quote ---

C# is gaining cross-platform support and much of it is now open.

As for writing software in C# -- over here! ::waves hand::  ;D

engrguy42:

--- Quote from: nctnico on May 06, 2020, 09:03:29 pm ---
--- Quote from: engrguy42 on May 06, 2020, 08:43:45 pm ---I'm kinda surprised in an engineering forum nobody is talking about C#. For general engineering stuff like simulations and setting up UI's and graphs and data acquisition stuff it is, for me at least, incredibly fast and efficient to get stuff up and running. Just drag-n-drop some UI components (windows, buttons, graphs,

--- End quote ---
C# is MS only. People seem to use Python for that kind of applications nowadays. Personally I don't know anyone who is writing software using C#.

--- End quote ---

No offense, but one guy not knowing a C# user doesn't say much. I just checked and it's said there are over 6 million users.

Maybe you need to get out more  :D

bd139:

--- Quote from: engrguy42 on May 06, 2020, 08:43:45 pm ---I'm kinda surprised in an engineering forum nobody is talking about C#. For general engineering stuff like simulations and setting up UI's and graphs and data acquisition stuff it is, for me at least, incredibly fast and efficient to get stuff up and running. Just drag-n-drop some UI components (windows, buttons, graphs, etc.), grab a free math library like MathNet, write your code and you're all set. And personally, like I say, if you're simulating real world equipment the OO design makes things so intuitive.

Is it because many folks here are more involved with hardware/embedded systems?

--- End quote ---

I have written a fair bit of C# over the years. In fact there are a few programs attached to my posts on here. You're right for rapid development purposes it's good. It also scales really well vertically and across teams. The main products I worked on over the last 15 years or so were C#.

But that's where the love ends I'm afraid. The language is fine but the mismanagement by microsoft of all the frameworks over the years has put a hell of a lot of us off. On top of that we have the shit show which is .Net Core that appeared on the scene. Really the issue stems from the closed nature of the ecosystem initially where you'd get pulled through microsoft "patterns and practices" which gave you terrible architectural advice and frameworks and then left you high and dry when their direction changed. Then along came the SOA era where they kicked out stuff like WCF, WWF and AppFabric. Within 3 years they pulled most of that and migrated to the whole Web API ecosystem, abandoning swathes of enterprise customers. Then there was the Silverlight debacle and the Windows Phone "throw everything away and start again" transition between WP7 and WP8. People were starting to get pissed. Then the Compact Framework and Windows Embedded were abandoned which left hoardes of mid-tier enterprises up shit creek. As if that wasn't enough of a kick in the teeth, about that time the ecosystem license costs got cranked up and other platforms started getting a lot of interest. Their result was to recycle the original Rotor CLR as .Net core and make it cross platform, an easy enough job apart from all the shitty bits of cruft that were win32 specific. Some effort was made at compatibility (.Net standard) but it means a rewrite for a lot of people. Even large components like NHibernate have non-portable forward changes.  In the background all the open source projects were being abandoned out of disinterest because the ecosystem is relatively small compared to others. Literally by the time everyone had ported to .Net Core 2.0, the world was on .Net core 3.1 and there was more heavy lifting and cost to throw at the problem. At the same time there was massive API consolidation and growth leading to a simpleish console application with logging pulling in a metric shit ton of dependencies. The last desperate breath is "we're going to get it right with .Net 5 and oh by the way can you bend over some more because your legacy SQL cluster is going to be buggered for a cool £1 million this year". Deep breath and look at the universe...

The C guys are raising one eyebrow because nothing changed in the last 15 years.

The Go guys are raising one eyebrow because the last major version upgrades they did in the last 10 years were trivial and automated.

The Python guys waited until all their libraries were ported, ran 2to3 and carried on in the last 10 years.

The postgres guys are sitting there laughing at this.

Everyone in the .Net ecosystem saw the guys above and said they want some of that. All the remains is a few scarred corpses like myself propping up what is left and whining on github and being silenced every time we even try and deal with MSFT who are really shitting out the marketing hard and shutting down negative sentiment and anything which questions their totalitarian control of the "open source" projects they run. Which is why C# is dying on it's arse at the moment. Even the company I work for which is a stallwart MS partner for many years is a Linux shop now. The legacy shit runs on .Net Core. The new stuff is going out in python and Go on Linux on AWS. It's dying. Run away quick.

Microsoft's development ecosystem is shiny as fuck but it's not something I would consider building a business on at this time. It's expanding out of desparation, nothing more. What exists past trivial stuff is a money sink.

radioactive:

--- Quote from: engrguy42 on May 06, 2020, 09:08:40 pm ---
--- Quote from: Wolfgang on May 06, 2020, 08:52:16 pm ---IMHO, the reason for the preference of Python is because:
- cross-platform
- much more scientific/engineering libs than other languages
- free, and open source.
Hard to beat, I would say. When you look at TIOBE what is happening to MATLAB at the moment that tells something.
Python is on the way to a firm number one in scientific computing, also for AI, ...

--- End quote ---

Hey, wait a minute...what's happening to MATLAB???

Am I gonna have to learn Python??  :D

--- End quote ---

No,  it is just another C library that someone created bindings to in Python.  Don't worry.

Wolfgang:

--- Quote from: engrguy42 on May 06, 2020, 09:08:40 pm ---
--- Quote from: Wolfgang on May 06, 2020, 08:52:16 pm ---IMHO, the reason for the preference of Python is because:
- cross-platform
- much more scientific/engineering libs than other languages
- free, and open source.
Hard to beat, I would say. When you look at TIOBE what is happening to MATLAB at the moment that tells something.
Python is on the way to a firm number one in scientific computing, also for AI, ...

--- End quote ---

Hey, wait a minute...what's happening to MATLAB???

Am I gonna have to learn Python??  :D

--- End quote ---

yeah, maybe not the worst idea. The point is that in Python most of engineering and math you need works similarly or sometimes even better than MATLAB, and Python is free. MATLAB not at all.
TIOBE shows that MATLAB use is declining steeply, Python is growing at record speed.

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