Why not make this the default everywhere? Well, there are a lot of scientific use cases where it's convenient to have Python-style dynamic typing and interactivity. A cool thing about Julia is that it allows that, while _also_ allowing to achieve high-performance, all within a single language.
For the record, I do also love the static type system and overall design of Rust. But for my day job (research in numerical methods and computational physics), I find Julia to be the most efficient way to get the job done -- rapid algorithm prototyping, data analysis, plot generation, etc.
We're looking for two frontend software engineers! (Interviews are starting this week, we're very ready.)
Our team works on all the (non-ad) screens in the subway, as well as two apps (TrainTime and the MTA app) and our website. We're a team of 20, mostly engineers, a few PMs and a designer. We operate like a startup within the MTA and are responsible for all customer-facing digital endpoints.
See one of our products here: https://apps.apple.com/us/app/mta-traintime/id1104885987 as well as some new screen designs here: https://www.reddit.com/r/nycrail/comments/1h2rqr6/new_countd...
Job description and application details: https://www.mta.info/document/163661
you can (and people already) model steps in any arbitrarily large workflow and have those results be processed in a modular fashion and have whatever process that begins this workflow check the state of the necessary preconditions prior to taking any action and thus go to the currently needed step, or retry ones that failed, and so forth.
- Checking the status of a task (queued, pending, failed, cancelled, completed) - Cancelling a queued task (or pending task if the execution environment supports it) - Re-prioritizing queued tasks - Searching for tasks based off an attribute (e.g. tag)
You really do need a database for this.