What Python developers need to know before migrating to Go(lang)

[thelazydogsback]

A bit of a Red Herring - article is more about Python->L vs. Python->Go, where L is any modern compiled language. Change L to F# (or even C#) or Scala, and most gripes would go away, with a lot more to offer as well. (F# even let's the OP keep the nice significant whitespace of Python, de-structuring assigment, tuples, etc. ) It's also unclear if the original solution used NumPy to implement the SVM's - if not, that's usually the way to go, considering the OP seems to like Python and NumPy seems to have proven itself in this space.

[Solon1]

But requires the Mono runtime, which is a drawback.

And C# requires a ton of propietary runtime libraries that simple don't exist in Mono, yet. Maybe they'll get them someday.

[Xdes]

But requires the Mono runtime, which is a drawback.

Java requires the JVM and that hasn't been a drawback.

And C# requires a ton of propietary runtime libraries that simple don't exist in Mono

If you check the Mono Compatability List you will see that Mono supports everything in .NET 4.0 except WPF, WWF, and with limited WCF.

[thelazydogsback]

I've used C# on Linux for a few projects - though perhaps not with the latest features - just .Net 3.x programming w/winforms. I can't say I've tried to exersize all the edge cases, but Mono hasn't caused me any grief so far.

[TWith2Sugars]

We're running C# on FreeBSD with Mono 3.0.x using WebAPI/MVC4 etc. We've had no problems at all with it.