Re:Std::visit is everything wrong with modern C++ (2017)
by sideeffffect on Sunday December 06, 2020 @06:25AM
(#25322789)
Why not F#? :)
Re:Std::visit is everything wrong with modern C++ (2017)
by v-yadli on Sunday December 06, 2020 @07:13AM
(#25323010)
I love to write F# (I built FVim), but there's still gap towards high performance game programming. In C# you get a lot of low-level unsafe constructs with zero allocation overhead that integrates very well with the external libraries. In F#, you either get a clumsy library special form (without proper syntax support), or the idea itself is considered "only for C# interop uses" and thus not prioritized.
F# has been in this position: a smaller team that tries to align with C#, without a language implementation team backing them (unlike Roslyn-C#), yet constantly feeding innovations back into the dotnet ecosystem. You can see a lot of example where F# piloted the idea, and later C# adopted and extended it in its own way, and F# struggling to catch up in that OO-centric world
(Disclaimer: MS employee, but not on the language teams)
Re:Std::visit is everything wrong with modern C++ (2017)
by matkoniecz on Tuesday December 08, 2020 @05:37AM
(#25343719)
Why F#?
I need a good reason to use one more programming language and one more dependency.
Also, how many Unity examples and tutorials and knowledgeable people are using C# and how many F#?
It could be C++, if I would go with Unreal Engine.
I used Squirrel in past, solely because for some reason it was modding language of OpenTTD.
I am not fan of any of them, I am not an expert in any of them. But it was more effective that writing from scratch 3D engine or AI backend to use something else.