News for hackers. Stuff that matters.
Re:Why Go and Not Rust? by mamcx on Monday September 16, 2019 @11:13AM (#20984865)
I agree. .NET is not bad at all. I work with F# and like the results

BUT

Is easier to make faster/memory-efficient app in Rust or Go than in .NET.

The "defaults" of a language matter a lot. And what it give for "free" impacts a lot. Specially for the code made by less skilled OR skilled-but-tired developers.

Re:Why Go and Not Rust? by floatboth on Monday September 16, 2019 @12:57PM (#20986072)
Go is garbage-collected just like .NET.

Rust indeed always pushes you towards efficiency :)

Re:Why Go and Not Rust? by thelazydogsback on Monday September 16, 2019 @02:17PM (#20986990)
Not necessarily. I've moved C++ code to C#, and it got much faster. The reason is because of copy (and other flavors of) c'tors that needlessly copied data because it was either happening unbeknownst to the author, or it was easier than dealing with the consequences of proper aliasing semantics. I have a feeling that this is not uncommon. So IOW, bad manual memory management is going to perform worse than modern GC systems. Pretty much the same as an automatic transmission on a high-end sports sedan -- unless you really know what you're doing, the AT is going to do a better job of shifting than you are.
Re:Why Go and Not Rust? by mamcx on Monday September 16, 2019 @02:33PM (#20987136)
> Go is garbage-collected just like .NET.

And I bet the .NET GC is much better than Go.

But what I was trying to say is that is very common in .NET to build layers of layers of abstraction. .NET is still largely used by a lot of "enterprisey" developers with bad or non-existence training.

With Go you get a much simpler deal: You have structs (like POCOS in C#) and you pass them. Sometimes, you put traits.

Is alike what is preached for good F#/C# code, but .NET still carry the inertia.

However, if you get into .NET with modern runtime (aka: around 4.5+) and idioms then I think the results will be very good.