3 ms·
This is huge. A few months ago, we decided to write a big new software component at $work, basically a service layer that is going to accumulate lots of busine
by perlgeek 12y ago
This is huge.
A few months ago, we decided to write a big new software component at $work, basically a service layer that is going to accumulate lots of business logic. We discussed several programming languages, and thought that a statically typed language might be a good fit (we mostly did perl and python so far). C# was dismissed pretty quickly, because .Net was closed source, and Mono had the reputation of being a bit second rate (possibly not well-founded, but also hard to debunk for somebody not in the community).
I mentioned that Roslyn was also open source, but it was hard to convince anybody when the "main" implementation was still closed source (and we're very much an open + linux shop).
If this had come a year earlier, we might have picked C#. Maybe there'll be another project here in a few years...
- katbyte 12y agoWhat did you end up picking?
- jaked89 12y agoWhat ever you were designing, it's almost certain that a more expensive, and mission critical system than yours was already built with C#. Objecting to a major language as C# because it's "closed-source" seems irrational to me. Why does it matter if it's open or closed-source? It's not like you can realistically invest time to dig in the source code and modify it, in the rare case that you found a problem. C# had huge amounts of money invested on it, probably more than your entire project you were planning.
- perlgeek 12y ago> Why does it matter if it's open or closed-source? It's not like you can realistically invest time to dig in the source code and modify it, in the rare case that you found a problem. Except that exactly this has happened with lots of libraries that we use, and sometimes also language implementations. Compilers and interpreters aren't any more scary than other projects, really.