4 ms·

Are we conflating .NET with C# and ecosystem? My perception is lots of libraries that does serious work are just written in C and C++, in the future I imagine

by a1o 3y ago

Are we conflating .NET with C# and ecosystem? My perception is lots of libraries that does serious work are just written in C and C++, in the future I imagine they will be in Rust and not C# - I am talking libraries you get from NuGet, lots of well maintained ones have a C# API that is a shell around something from elsewhere. Be it ImageMagick, lots of media decoding stuff or even proprietary things, like Flir. It's usually hard to find a library to do some work for you in C#, in NuGet, that is also maintained - you will have an easier time grabbing the sources and adding directly in your project so you can maintain it yourself as bug appears and debug it more easily. A lot of times the bug is the developer assumed everyone uses Windows. Most of time when using C# I am reinventing the wheel in it because of this. I also never had a C# project that used it exclusively.

Hawxy 3y ago
> Be it ImageMagick, lots of media decoding stuff or even proprietary things, like Flir. For ImageMagick specifically, there's a purist C# replacement (ImageSharp) that avoids the dependency on System.Drawing. > A lot of times the bug is the developer assumed everyone uses Windows. I can't say I've encountered this in years, most libraries are cross-platform out of the box with support for the major .NET 6+ targets (Windows, Mac, Linux).
coldtea 3y ago
>Are we conflating .NET with C# and ecosystem? .NET is C# and ecosystem, so we're rightly equating, but not conflating them.
- lupire 3y ago
  (cries in VB.NET)
  - coldtea 3y ago
    Wasn't VB.NET basically a rework of VB to be a thin facade over the C#-oriented and tailored .NET semantics and libs?
Dr4kn 3y ago
Pretty much what made python so popular. The language made it a necessity that everything that had to be fast needed to be written in another language, but it made it easy to do. Having an easy to use (scripting) language that can do serious work was and still is awesome
- a1o 3y ago
  Well yes, I do agree in parts, python is awesome for this and if I am working on the lower level I would much prefer it as scripting language - it's very easy to glue. On C# and .NET we still don't have a portable C++/CLI, it's still something that is only for Windows and only MSVC. Maybe if they ever port that. But for now I will stick to python.

by a1o 3y ago

Hawxy 3y ago

> Be it ImageMagick, lots of media decoding stuff or even proprietary things, like Flir. For ImageMagick specifically, there's a purist C# replacement (ImageSharp) that avoids the dependency on System.Drawing. > A lot of times the bug is the developer assumed everyone uses Windows. I can't say I've encountered this in years, most libraries are cross-platform out of the box with support for the major .NET 6+ targets (Windows, Mac, Linux).

coldtea 3y ago

>Are we conflating .NET with C# and ecosystem? .NET is C# and ecosystem, so we're rightly equating, but not conflating them.

lupire 3y ago
(cries in VB.NET)
- coldtea 3y ago
  Wasn't VB.NET basically a rework of VB to be a thin facade over the C#-oriented and tailored .NET semantics and libs?

Dr4kn 3y ago

Pretty much what made python so popular. The language made it a necessity that everything that had to be fast needed to be written in another language, but it made it easy to do. Having an easy to use (scripting) language that can do serious work was and still is awesome

a1o 3y ago
Well yes, I do agree in parts, python is awesome for this and if I am working on the lower level I would much prefer it as scripting language - it's very easy to glue. On C# and .NET we still don't have a portable C++/CLI, it's still something that is only for Windows and only MSVC. Maybe if they ever port that. But for now I will stick to python.