HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dmolina
DaemonMode.jl
Julia2020–2023
dmolina / DaemonMode.jl

DaemonMode.jl

Client-Daemon workflow to run faster scripts in Julia

12Distinct people
22Mentions
0Explicit recommenders
305GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Client-Daemon workflow to run faster scripts in Julia

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year22 dated mentions

Observed mentions: 2020-08-03 18:32:29 UTC to 2023-12-04 17:26:11 UTC.

0369122020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC11011
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC808

What Hacker News says

22 sources
Thats for an entry point, you can search `Base.@main` to see a little summary of it. Later it will be able to be callable with `juliax` and `juliac` i.e. `~juliax test.jl` in shell. DynamicalSystems looks like a heavy project. I don't think you can do much more on your own. There have been recent features in 1.10 that lets you just use the portion you need (just a weak dependency), and there is precompiletools.jl but these are on your side. You can also look into https://github.com/dmolina/DaemonMode.jl for running a Julia process in the background and do your stuff in the shell without startup time until the standalone binaries are there.
In Potential of the Julia programming language for high energy physics computing
I'll preface by saying by far my biggest gripe with Julia is the inability to deploy binaries easily. The only hope on easy deployment I suppose is to hope it becomes commonly installed enough that you can rely on it being on systems. But some of your complaints are a bit off (in my own opinion): >and you can't quickly run a script What is wrong with the following to run a script? $ julia myscript.jl If you have specific needs that demand, after hitting return, the few seconds of delay for the vast majority of scripts is an issue, you can pre-compile it ahead of time or simply use something like https://github.com/dmolina/DaemonMode.jl Julia has issues as with all languages but "not being able to quickly run a script" is by far one of the easiest to work around. > and you can't quickly run a script or REPL for development. REPL- I disagr
Read the rest
ee. Of course you can - that's how many of use Julia. > And now Julia has competition from Mojo. ...maybe. The code-samples we've seen from Mojo look very similar to Python, obviously. And that is specifically why a lot of poeple love Julia. The problems people are more and more interested in (machine learning, etc) are at their base mathematical problems. These languages are all tools to translate mathematics into computer instructions. The code should then ideally look as close to that math as possible. Spamming np.linalg, sp.sparse, and so forth over and over again is just ugly, and the entire Python workflow overly encourages object oriented design for concepts that are mathematically functions. And, well, should be functions. If you're working in these or related fields at all and write any code with Julia, it's hard to not fall in love. Mojo may make Python faster. But it will still be, roughly, Python. And considering that the Python 2 -> Python 3 transition has still not completed, I think it's premature to conclude Mojo's python upgrades will get anywhere.
In Julia 1.9.0 lives up to its promise
> Making a "busybox" style executable that replaces all coreutils I wonder if DaemonMode (https://github.com/dmolina/DaemonMode.jl) is the right approach for this, having each of those tools' functionality loaded in the server process, and calling out to them from a client when a tool is invoked. > a complete base package for sparse matrices, including kronecker products etc. SparseArrays is a standard library package for sparse matrices and arrays. kron is in the LinearAlgebra standard library. So you can just do using LinearAlgebra using SparseArrays and then do any kron product you want, whether sparse matrices with other sparse matrices, or dense ones, or any other array type.
In Julia 1.9.0 lives up to its promise
> CLI Well, not nicely certainly, but: https://github.com/dmolina/DaemonMode.jl > portable Neither is python - it just relies on universal availability. Over time… > Multiple dispatch, it's system of abstract inheritance and lack of static analysis and tooling makes it very difficult to write correct code. It's even hard to read Julia code due to dispatch labyrinths, macros that obfuscate IDEs, and lack of good IDE tooling. There is support for solving some of this but it’s obscure and needs more attention. Overall I think the growth will continue, specific fields having best of any language software packages (DifferentialEquations.jl,…) written in Julia starts to create somewhat of a network effect. And imo the packages being written in Julia are quite specialized, unlike much of the famed “Python ecosystem”, half of which is wrapper to
Read the rest
C++ functions and another big chunk being HTTP calls to external APIs..
In Ask HN: Why is Julia so underrated?
The startup times have improved a lot in version 1.6, the latest release, and are I Proving again in the next upcoming release candidate. Are you hitting the startup time very often? If so, you might want to try some things to keep one julia session open and sending code to it like a daemon instead of constantly closing and opening sessions. This package makes that workflow really easy: https://github.com/dmolina/DaemonMode.jl
In Julia: Faster than Fortran, cleaner than Numpy
Plenty of people use the REPL in terminal and sublime text or vim or whatever. I also dislike browser-based tooling and think Julia has done a good job avoiding Rstudio-style dependencies. But if your point is the inability to do `julia script.jl` , yeah thats a pain point. Fortunately there has been some tooling to make running many jobs in a row easier: https://github.com/dmolina/DaemonMode.jl
In Introduction to Pluto.jl

Showing the 15 most recent of 22 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.