Quote from: rlh on January 20, 2016, 04:06:17 PM

Quote from: nexern on January 20, 2016, 04:00:48 PM

Quote from: Come-from-Beyond on January 20, 2016, 02:41:30 PM

Quote from: l8orre on January 20, 2016, 02:26:00 PM

seriously?
many people (myself included) consider C# a cheap M$- java knockoff.
Not that I would badmouth such a thing, but it seems a bit redundant...
Getting a native c version looks much more effective.

Disclaimer: Personally, I only dabble in c occasionally, but seeing the raw power and compactness of jl777's SuperNET c codebase made me say that! Grin

The world has changed. http://www.mono-project.com/

into what exactly?

vanilla C is and will be unbeatable in terms of portability and extensibility compard to C#.
sure, adding additional layers (and therefore complexity) to run on nix for instance is
doable but this is not what i am talking about. a lean dependency free 33.3 kb C lib
which compiles from source on all major OS without bloat, ready to use is what i mean.

however, don't want to start a language war here but if your requirements are those
like portability, usability, extensibility etc. to unlock many other devs and projects
you have to go good-old-plain-ansi-C.

I'm hoping to convert it to C# because I want to convert it to C#. This is part hobby and part useful tool for the business Windows developer world. I understand that portability is important and I agree that writing a C API or client is of immense importance. However, a lot of business logic is written in .Net and a capable dev can right something that's very extensible and fast.

Anyway, that's my intent. I'm not looking to go into troll-mode (coz that's not my style:D) but that's not to say that a .Net option[\i] isn't without it's benefits.

absolutely agree rlh!

don't take me wrong here, it is great what you are doing but my suggestion points
to enable as much other devs as possible to overcome the lang gulag.
the requirements are different if IOTA see/confirms the potential in doing so.