Certainly parsing large text files into structured data is easy in F# (with libraries like FParsec). And tail-recursion is a blessing for this. But my money would be on well-written C++ to be faster - it's simply a lower level language. But it depends how "well written" it is. As a whole I also find .Net Core faster than .Net Framework.
But if milliseconds count I'd be looking at languages like Go or Rust (which are new enough to work well with modern standards). On Fri, 18 Jan 2019 at 14:43, Greg Keogh <gfke...@gmail.com> wrote: > > >> https://stackoverflow.com/questions/1324919/what-language-is-net-framework-written-in >> > > That's interesting, but it's a separate issue. My colleague claims that > you would always chose to write an app in C++ for better performance in > computationally intensive work. I counter-claim this is no longer generally > true. I suspect that JIT'd managed code would have acceptably close > performance to the native equivalent. > > I saw a YouTube video a few months ago (I can' find it now) where a lady > spruiking F# told of a developer boffin she knew who took a massive > financial application written with millions of lines of C++ and rewrote it > in F# with a fraction of the lines of code, and it was easier to maintain > and it performed much better. I feel she was indirectly pointing out that > the game has changed regarding our old biases about languages, platforms > and performance. > > *GK* > >>
