F# vs JRuby: What are the differences?
What is F#? Strongly-typed, functional-first programming language for writing simple code to solve complex problems. F# is a mature, open source, cross-platform, functional-first programming language. It empowers users and organizations to tackle complex computing problems with simple, maintainable and robust code.
What is JRuby? A high performance, stable, fully threaded Java implementation of the Ruby programming language. JRuby is the effort to recreate the Ruby (http://www.ruby-lang.org) interpreter in Java. The Java version is tightly integrated with Java to allow both to script any Java class and to embed the interpreter into any Java application. See the docs directory for more information.
F# and JRuby can be primarily classified as "Languages" tools.
"Pattern-matching" is the top reason why over 40 developers like F#, while over 7 developers mention "Java" as the leading cause for choosing JRuby.
F# and JRuby are both open source tools. JRuby with 3.32K GitHub stars and 830 forks on GitHub appears to be more popular than F# with 2.09K GitHub stars and 341 GitHub forks.
Olo, Huddle, and Property With Potential are some of the popular companies that use F#, whereas JRuby is used by Groupon, Soundcloud, and Lookout. F# has a broader approval, being mentioned in 19 company stacks & 16 developers stacks; compared to JRuby, which is listed in 13 company stacks and 4 developer stacks.
What is F#?
What is JRuby?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using F#?
What are the cons of using JRuby?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.
After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...
I've used .NET for many years, but only in recent years, after Microsoft introduced .NET Core, I've found a new love and excitement for the technology again. The main driver for us using .NET Core is not that it is cross platform compatible, open source or blazingly fast (which it is!), but the fact that we can use (what we consider) the best programming languages (mainly F# and C#) to carry out our jobs without sacrificing the other benefits.
Today we run most of our web infrastructure on .NET Core in Docker containers, deployed into a Kubernetes cluster which spans across multiple time zones in the Google Cloud and we couldn't be happier. Due to the portability of the .NET Core platform we are even able to develop many new services as serverless functions with F# which has become an absolute game changer.