Inko compared to other languages
Inko shares similarities with a variety of other languages. This can lead one to wonder, what are the differences? This guide provides an unbiased overview of the differences between Inko and several other programming languages.
Comparing with Go
Go is a compiled language, whereas Inko is an interpreted language. In practise this means Go executables are easier to distribute, as you do not need to distribute both your code and a virtual machine.
Go is a multi-paradigm language, while Inko is an object-oriented programming language.
Go uses lightweight tasks called "goroutines", which are basically green threads. Inko uses lightweight processes, which are closer to OS processes, as each lightweight processes is fully isolated.
Goroutines use shared memory, whereas Inko processes have their own heaps.
Go's garbage collector is a concurrent mark & sweep garbage collector, prioritising low pause timings over application throughput. To the best of our knowledge, the Go garbage collector may still suspend all goroutines in certain cases (known as a "stop-the-world" phase).
Inko's garbage collector is a parallel generational garbage collector, based on Immix. The Inko garbage collector only suspends the process that is being garbage collected, but it's suspended for the entire duration of the garbage collection cycle. Inko's garbage collector doesn't focus on one specific area (e.g. low pause timings), instead it tries to provide a healthy balance between low pause timings and application throughput.
Go's scheduler is partially preemptive. This means that Go can suspend goroutines and have others run in their place, but only when meeting certain conditions. Inko's scheduler is fully preemptive, meaning every process is guaranteed a certain amount of execution time, no matter what code it's running.
Comparing with Erlang and Elixir
Erlang, Elixir, and Inko are all interpreted languages. All three compile source code into bytecode, which is then executed. Inko draws a lot of inspiration from Erlang and Elixir.
Erlang and Elixir are functional programming languages, while Inko is object-oriented.
Erlang, Elixir, and Inko all use a similar multitasking model: lightweight processes.
Erlang and Elixir use a combination of process-local memory, and reference counted memory. Reference counting is typically used for larger objects, making it cheaper to send them to other processes, at the cost of having to perform reference counting.
Inko uses tracing garbage collection, although some internal data structures use reference counting on top of tracing garbage collection. For example, strings are reference counted to make it cheaper to send them to processes. The garbage collector manages these reference counts, and typically are only modified when copying such an object or when it's garbage collected.
All three use a similar scheduling setup: multiple threads perform work using work stealing, and processes can be suspended whenever the scheduler decides this is necessary. This is not surprising, as Inko's scheduling mechanism is inspired by Erlang and Elixir.
Comparing with Ruby
Ruby is an interpreted object-oriented programming language, typically used for building web services such as Basecamp and GitLab, although you can also use it for a wide variety of other tasks.
Both Ruby and Inko use a bytecode interpreter. Ruby does not persist the bytecode after compilation, instead it's directly executed. This means that every time your program runs, the bytecode has to be compiled from scratch.
Inko's compiler is a separate program, and bytecode is saved to disk. Incremental compilation is not supported, but will be added in the future.
Both Ruby and Inko are object-oriented languages. Inko takes things a few steps
further by using methods for almost everything, including statements such as
In Ruby you can use OS threads, fibers (coroutines), and OS processes. There are no high level structures such as thread pools, or work stealing schedulers.
In Inko you can only use lightweight processes, and the virtual machine takes care of scheduling and running these in the best way possible.
The main Ruby implementation (MRI, also known as CRuby) uses a "Global Interpreter Lock" (GIL), preventing Ruby threads from running in parallel, except for a few cases. Inko has no such lock, allowing you to run processes in parallel.
Ruby uses shared memory, whereas in Inko all processes have their own isolated heap.
Ruby uses a generational, incremental, mark & sweep garbage collector that will suspend all threads when running. The garbage collector is not parallel, meaning only a single thread is used to perform garbage collection.
Inko uses a parallel generational garbage collector, and only suspends the process that is being garbage collected.
As Ruby uses OS threads for multitasking, it relies on the OS thread scheduler. This means an OS thread will typically run until it's garbage collected or terminates. This means it's possible for a few OS threads to consume all CPU time, preventing other threads from performing their work.
Inko uses its own preemptive scheduler, and guarantees that every process is given a fair share of execution time.
Comparing with Pony
Pony is an object-oriented programming language built on the actor model. Pony uses "capabilities" to make certain operations secure. The definition of a "capability" described in "Chapter 4: Capabilities" of the Pony tutorial.
Pony is a compiled language using LLVM, whereas Inko is an interpreted language. Both Inko and Pony use a separate program for compilation, inkoc and ponyc respectively.
Both Pony and Inko are object-oriented programming languages.
Pony uses actors, which you define similar to objects in Inko. To the best of our knowledge, Pony requires you to define your actor before you can use it, whereas in Inko you can spawn a process whenever you like.
To the best of our knowledge, Pony uses separate heaps for actors, although we haven't been able to confirm this. Memory is managed using a garbage collector, although garbage collection does not run while an actor is performing a "behaviour". A behaviour is basically an asynchronous method call. While this may result in higher application throughput, it can also lead to an actor exhausting memory.
Pony's advice for dealing with this appears to come down to "Just don't do it". For example, from the Garbage collection guide:
Long loops in behaviors are a good way to exhaust memory. Don't do it. If you want to execute something in such a fashion, use a Timer.
Inko uses a separate heap for every process, and garbage collection can occur while the process is performing work. The impact of this on application throughput should be minimal, as most (large) processes won't be suspended for more than a few milliseconds per garbage collection cycle.
Pony's scheduler is not preemptive, meaning an actor will continue to run until it yields control back to the scheduler. This means an infinite loop will prevent the thread running the actor from doing any other work.
Inko's scheduler is preemptive, meaning every process is given a fair share of execution time. As a result, long running code such as infinite loops will never prevent a thread from doing other work indefinitely.