Navigation
Companies
JULIA DIRECTORY
Write a resistor in ordinary code and you have to pick a direction before you write a single line. Is voltage the input and current the output, or the other way around? You commit, you write the function, and the function only ever runs that one way.
Write the same resistor in Dyad and you do not pick a direction at all.
component Resistor parameter R::Resistance relations v = i * R end That is the whole model: a parameter and one equation.
If you’ve followed the Flexible Julia posts, this one is a close neighbor: Flexible Sim.
Building and checking a simulation model is hard without proper IDE support. Much of the work still happens outside the IDE, in a separate tool - especially when your codebase mixes Dyad, Julia, Modelica and Python.
Most language servers read your file and make an educated guess about what the compiler would say. JETLS.jl skips the guessing and asks the compiler directly.
That distinction sounds small until you have watched a language server get something wrong that the real compiler would never get wrong, because the language server never ran your code through inference in the first place. It parsed the syntax tree, matched some patterns, and did its best.
I spent fifteen years tuning JVMs for banks, retailers and insurers, and it took building a Julia plugin to notice how much of that tuning HotSpot does for you before you ever touch a flag.
The problem HotSpot solves is the one every JIT has: interpreted code starts instantly and runs slow, compiled native code starts slow and runs fast. You cannot have both from the first line. HotSpot’s answer, tiered compilation, has been the default since Java 7, and it works by never picking just one option.
The debugger locked up the first time I inspected a DataFrame mid-session, and it took me a while to believe that the box-drawing characters in a pretty-printed table were the reason. │ ─ ⋯ …, the kind of Unicode a DataFrame uses to draw its own borders, sent over the wire as part of a debug response. The connection did not crash. It just quietly went out of sync and stopped answering, which is worse, because nothing tells you why.
A regex can highlight a language for about as long as nobody nests anything. The moment a string contains a comment marker, or a comment contains something that looks like a string, or a block comment nests inside another block comment the way Julia’s #= ... =# is allowed to, the pattern either lights up the wrong span or gives up entirely. A regex is the cheap first instinct for a language plugin, and it means you will rewrite the highlighter twice.
Joovy is out - Apache 2.0, on GitHub.
The name is Julia + Groovy. Groovy gave Java a dynamic layer without leaving the JVM. Joovy does the same for Julia.
A quick one, but I’ve just released Flexible Julia - a Julia language plugin for JetBrains IDEs.
You can get it on the JetBrains Marketplace.
Works with IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains products. So… yay :)
Background
| Education | EBS Business School, SFSU, HSG |
| Experience | 20 Years Enterprise Systems |
| Built | Scipio ERP - ERP & Ecommerce System |
| Author | "Start/Up - Set the net on fire" |
| JetBrains | 5x Plugins Published |
Tech Stack
| Languages | Java, Python, JS, TS, Rust, Go, Swift, PHP |
| Frontend | React, Vue, Angular, HTML/CSS |
| Databases | PostgreSQL, MySQL, MongoDB |
| Caching | Redis, Memcached |
Key Clients
| Enterprise | L'Oréal, Amadeus, Konica Minolta, Orange |
| Digital | 1&1 Internet, Sedo.com, Creditsafe |
| Public | DRK, Kanton Basel, Aktion Mensch, Börsenverein |