Remix.run Logo
▲ bjoli 3 hours ago

Go isn't as much fun. And is usually slower for my work until I bump up the GC and then it uses roughly the same amount of memory.

I have also found c# async to be lighter than go's concurrency story, and dotnet11 is going to make that much more clear.

Now: I write software for fun, not for money.

▲SurajMishra 3 hours ago | parent [-]

So for a requirement where both golang and .net would suffice, would you choose .Net over golang?

▲bjoli 2 hours ago | parent [-]

Yes. Unless I really need CSP, but then I would much rather use f#+hopac because CML is the bee's knees.

For general concurrency where async doesn't suffice, go is nicer than C#, but hopac is nicer than go.

If go had proper concurrentML I am pretty sure I would use go a lot more. Again: this is for hobby projects where I get to choose freely.