5 ms·
You must also take account that people not always look at a language per by their MOST perfect domain fit. For me, and probably many I look in the rust sphere(
by mamcx 7y ago
You must also take account that people not always look at a language per by their MOST perfect domain fit.
For me, and probably many I look in the rust sphere(and go and swift and F# where I also have worked), this langs are not picked because "I need bare-metal baby!" but "I need something a bit faster/easier to deploy/less resource/less crazy intensive than obj-c/python/ruby/js/php".
I have picked all 4 (rust, f#, go and swift) because that, because all (except go) have AGDTs and pattern matching (and go only because I need some utilities easier to cross compile FAST) and that is all.
ALSO
because are langs FRIENDLY to solo(me!)/small teams of developers. Even If i must pick a "system language" I will NEVER pick C++, too much complexity. That is why I pick F# vs C# (F# is more economic in lines of code, more expressive and overall simpler), Swift as fast I as could (vs obj-c) and Pascal over C/C++ in the old days.
Looking this way, them intersect much more than most imagine.
- niclo 7y agoMay I ask how you experience with F# was and how you used it ? I'm slowly learning it but I'm not 100% sure to keep going, maybe switch to other similar languages with bigger communities/bigger market demand
- mamcx 7y agoI use C# a lot before and think F# is a good alternative. I use for ERP-like app development with web backend, CLIs, mobile all done on OSX. I move now to Rust (for long term bets I made) but think F#/.NET Core is a great toolset in itself.