Julia is my favorite programming language. More than that actually, perhaps I’m a bit of a fanboy. Sometimes, though, the ceaseless celebration of Julia by fans like me can be a bit too much. It papers over legitimate problems in the language, hindering progress. And from an outsider perspective, it’s not only insufferable (I would guess), but also obfuscates the true pros and cons of the language. Learning why you may not want to choose to use a tool is just as important as learning why you may.
This post is about all the major disadvantages of Julia. Some of it will just be rants about things I particularly don’t like - hopefully they will be informative, too. A post like this is necessarily subjective. For example, some people believe Julia’s lack of a Java-esque OOP is a design mistake. I don’t, so the post won’t go into that.
Table of contents
- Table of contents
- Compile time latency
- Large memory consumption
- Julia can’t easily integrate into other languages
- Weak static analysis
- The core language is unstable
- The ecosystem is immature
- The type system works poorly
- You can’t extend existing types with data
- Abstract interfaces are unenforced and undiscoverable
- Subtyping is an all-or-nothing thing
- The iterator protocol is weird and too hard to use
- The protocol
- The problem
- Functional programming primitives are not well designed
Read in full here:
https://viralinstruction.com/posts/badjulia/
This thread was posted by one of our members via one of our news source trackers.