3 ms·
You might be able to use F#. There is no technical reason you can't use F# with C#, but I've seen political barriers to even using C# with VB.Net.
by tl 16y ago
You might be able to use F#. There is no technical reason you can't use F# with C#, but I've seen political barriers to even using C# with VB.Net.
- mapleoin 16y agoThere's always the issue of who will maintain the code once you're gone?.
- tl 16y agoThat gets trotted out as the counter argument (even with vb .net vs c# where the 2 languages are very similar), but it's moot. Code reuse doesn't happen without clean interfaces (which reduces the problem of different languages) because few programmers will read your code even if it's in the language they want.
- trezor 16y agoThat code reuse doesn't happen is really a myth and where I work, things gets reused a lot. That said, what language to use boils down more to code-maintenance than code-reuse since on .NET code reuse can (and will) happen transparently across CLR languages. I work for a software vendor and having high quality, maintainable code which others can work with is a requirement for everything you do. Using some "exotic" language would not be fully compliant with that requirement.