Need advice about which tool to choose?Ask the StackShare community!

Julia

379
500
+ 1
117
Scala

7.6K
5.7K
+ 1
1.5K
Add tool

Julia vs Scala: What are the differences?

What is Julia? A high-level, high-performance dynamic programming language for technical computing. Julia is a high-level, high-performance dynamic programming language for technical computing, with syntax that is familiar to users of other technical computing environments. It provides a sophisticated compiler, distributed parallel execution, numerical accuracy, and an extensive mathematical function library.

What is Scala? A pure-bred object-oriented language that runs on the JVM. Scala is an acronym for “Scalable Language”. This means that Scala grows with you. You can play with it by typing one-line expressions and observing the results. But you can also rely on it for large mission critical systems, as many companies, including Twitter, LinkedIn, or Intel do. To some, Scala feels like a scripting language. Its syntax is concise and low ceremony; its types get out of the way because the compiler can infer them.

Julia and Scala can be primarily classified as "Languages" tools.

"Lisp-like Macros" is the primary reason why developers consider Julia over the competitors, whereas "Static typing" was stated as the key factor in picking Scala.

Julia and Scala are both open source tools. Julia with 22.7K GitHub stars and 3.43K forks on GitHub appears to be more popular than Scala with 11.8K GitHub stars and 2.75K GitHub forks.

Twitter, Coursera, and 9GAG are some of the popular companies that use Scala, whereas Julia is used by inFeedo, Platform Project, and N26. Scala has a broader approval, being mentioned in 437 company stacks & 324 developers stacks; compared to Julia, which is listed in 5 company stacks and 5 developer stacks.

Advice on Julia and Scala
Needs advice
on
ScalaScalaNode.jsNode.js
and
GoGo

Finding the best server-side tool for building a personal information organizer that focuses on performance, simplicity, and scalability.

performance and scalability get a prototype going fast by keeping codebase simple find hosting that is affordable and scales well (Java/Scala-based ones might not be affordable)

See more
Replies (1)
David Annez
Head of Engineering at loveholidays · | 4 upvotes · 126.1K views

I've picked Node.js here but honestly it's a toss up between that and Go around this. It really depends on your background and skillset around "get something going fast" for one of these languages. Based on not knowing that I've suggested Node because it can be easier to prototype quickly and built right is performant enough. The scaffolding provided around Node.js services (Koa, Restify, NestJS) means you can get up and running pretty easily. It's important to note that the tooling surrounding this is good also, such as tracing, metrics et al (important when you're building production ready services).

You'll get more scalability and perf from go, but balancing them out I would say that you'll get pretty far with a well built Node.JS service (our entire site with over 1.5k requests/m scales easily and holds it's own with 4 pods in production.

Without knowing the scale you are building for and the systems you are using around it it's hard to say for certain this is the right route.

See more
Decisions about Julia and Scala
Chose
PythonPython
over
ScalaScala

I am working in the domain of big data and machine learning. I am helping companies with bringing their machine learning models to the production. In many projects there is a tendency to port Python, PySpark code to Scala and Scala Spark.

This yields to longer time to market and a lot of mistakes due to necessity to understand and re-write the code. Also many libraries/apis that data scientists/machine learning practitioners use are not available in jvm ecosystem.

Simply, refactoring (if necessary) and organising the code of the data scientists by following best practices of software development is less error prone and faster comparing to re-write in Scala.

Pipeline orchestration tools such as Luigi/Airflow is python native and fits well to this picture.

I have heard some arguments against Python such as, it is slow, or it is hard to maintain due to its dynamically typed language. However cost/benefit of time consumed porting python code to java/scala alone would be enough as a counter-argument. ML pipelines rarerly contains a lot of code (if that is not the case, such as complex domain and significant amount of code, then scala would be a better fit).

In terms of performance, I did not see any issues with Python. It is not the fastest runtime around but ML applications are rarely time-critical (majority of them is batch based).

I still prefer Scala for developing APIs and for applications where the domain contains complex logic.

See more
Alexander Nozik
Senior researcher at MIPT · | 3 upvotes · 72.7K views
Migrated
from
JuliaJulia
to
KotlinKotlin

After writing a project in Julia we decided to stick with Kotlin. Julia is a nice language and has superb REPL support, but poor tooling and the lack of reproducibility of the program runs makes it too expensive to work with. Kotlin on the other hand now has nice Jupyter support, which mostly covers REPL requirements.

See more

We needed to incorporate Big Data Framework for data stream analysis, specifically Apache Spark / Apache Storm. The three options of languages were most suitable for the job - Python, Java, Scala.

The winner was Python for the top of the class, high-performance data analysis libraries (NumPy, Pandas) written in C, quick learning curve, quick prototyping allowance, and a great connection with other future tools for machine learning as Tensorflow.

The whole code was shorter & more readable which made it easier to develop and maintain.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Julia
Pros of Scala
  • 18
    Designed for parallelism and distributed computation
  • 17
    Fast Performance and Easy Experimentation
  • 14
    Free and Open Source
  • 13
    Multiple Dispatch
  • 12
    Calling C functions directly
  • 12
    Lisp-like Macros
  • 11
    Dynamic Type System
  • 8
    Powerful Shell-like Capabilities
  • 4
    REPL
  • 4
    Jupyter notebook integration
  • 2
    String handling
  • 2
    Emojis as variable names
  • 188
    Static typing
  • 179
    Pattern-matching
  • 177
    Jvm
  • 172
    Scala is fun
  • 138
    Types
  • 95
    Concurrency
  • 88
    Actor library
  • 86
    Solve functional problems
  • 83
    Open source
  • 80
    Solve concurrency in a safer way
  • 44
    Functional
  • 23
    Generics
  • 23
    Fast
  • 18
    It makes me a better engineer
  • 17
    Syntactic sugar
  • 13
    Scalable
  • 10
    First-class functions
  • 10
    Type safety
  • 9
    Interactive REPL
  • 8
    Expressive
  • 7
    SBT
  • 6
    Implicit parameters
  • 6
    Case classes
  • 4
    Used by Twitter
  • 4
    JVM, OOP and Functional programming, and static typing
  • 4
    Rapid and Safe Development using Functional Programming
  • 4
    Object-oriented
  • 3
    Functional Proframming
  • 2
    Spark
  • 2
    Beautiful Code
  • 2
    Safety
  • 2
    Growing Community
  • 1
    DSL
  • 1
    Rich Static Types System and great Concurrency support
  • 1
    Naturally enforce high code quality
  • 1
    Akka Streams
  • 1
    Akka
  • 1
    Reactive Streams
  • 1
    Easy embedded DSLs
  • 1
    Mill build tool
  • 0
    Freedom to choose the right tools for a job

Sign up to add or upvote prosMake informed product decisions

Cons of Julia
Cons of Scala
  • 5
    Immature library management system
  • 3
    Slow program start
  • 3
    Poor backwards compatibility
  • 2
    JIT compiler is very slow
  • 2
    Bad tooling
  • 2
    No static compilation
  • 11
    Slow compilation time
  • 6
    Multiple ropes and styles to hang your self
  • 4
    Too few developers available
  • 3
    Complicated subtyping
  • 2
    My coworkers using scala are racist against other stuff

Sign up to add or upvote consMake informed product decisions

What companies use Julia?
What companies use Scala?
See which teams inside your own company are using Julia or Scala.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Julia?
What tools integrate with Scala?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Julia and Scala?
Python
Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best.
R Language
R provides a wide variety of statistical (linear and nonlinear modelling, classical statistical tests, time-series analysis, classification, clustering, ...) and graphical techniques, and is highly extensible.
MATLAB
Using MATLAB, you can analyze data, develop algorithms, and create models and applications. The language, tools, and built-in math functions enable you to explore multiple approaches and reach a solution faster than with spreadsheets or traditional programming languages, such as C/C++ or Java.
Rust
Rust is a systems programming language that combines strong compile-time correctness guarantees with fast performance. It improves upon the ideas of other systems languages like C++ by providing guaranteed memory safety (no crashes, no data races) and complete control over the lifecycle of memory.
Go
Go is expressive, concise, clean, and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language.
See all alternatives