Dear all, I wrote a new blog post on Julia. This time, a review of the use of trimming for Advent of Code so far. It also contains a bunch of opinions / speculation / rambling about Julia and Julia development in general. Enjoy. Review: Julia trimming for Advent of Code 2025 …

I think the near future of the language will have formal interfaces and a strict sublanguage. This is just what it has been building towards: write the simple code to get things work, but for core packages, then take the time to refactor towards a static sublanguage with more guarantees, lock it dow…

[image] ChrisRackauckas: Solving the two language problem … a gradual process to get a very fast and statically inferable program Won’t this create a two-language problem, though? In Python, you can gradually switch to JAX. It’s still Python, but not really, because some of the semantics ar…

That’s already kind of what happens with large codebases: we end up rewriting things with loops from the start, preallocating stuff, using views instead of slices, etc. I agree that the idea of strict mode possibly being applied at a project level is a bit scary, but maybe there are ways to activate…

Good post, the only thing I would add is that GPU compilation goes through an entirely separate path. In that sense, Julia is “3 languages in a trench coat”: static, dynamic, and GPU.

[image] ForceBru: Won’t this create a two-language problem, though? Technically no because it’s still one language with the same philosophy and semantics. Someone has called this the “1.5-language problem” before, but I never really bought into that idea. Every language has its contextual sub…

GPU is not in Base so I don’t think it works :slight_smile: otherwise every symbolic package is its own language

[image] yolhan_mannes: Would you say there are “two” Rusts just because you can go fully unsafe or fully safe Not sure, I don’t really use Rust. [image] yolhan_mannes: “two” V because you can compile to c code or to native code I definitely wouldn’t say this means there are two Vs bec…

[image] Benny: “1.5-language problem” Yep, it’s like async functions: you can’t await an async function from a regular one, so you must either make that function async too or have two different pieces of your program: one dealing with async stuff, the other doing plain compute. I think there’…

Ok I see, I feel like it’s just better to have some kind of a 1.5 language problem (because you will never need to write wrapper from the static part to the dynamic since its the same code) than just keep stating julia is general purpose and have issues with real-time and embedded systems. So even i…

[image] ForceBru: …then this means that “strict Julia” could be very different from “dynamic Julia”, so much so that one could look at a package and tell whether it’s one or the other. All of SciML has been written in this form from basically the start and we just call that normal Julia. The …

Blog post: Review of trimming for AoC 2025

Community

frankwswang December 9, 2025, 5:50pm 18

Sounds like this:

Topic		Replies	Views
Roadmap for small binaries Internals & Design question	126	13369	November 10, 2024
What don't you like about Julia for "serious work"? Community	176	26470	April 20, 2024
Julia solves a two-language problem but the real problem is a 3-wants problem which Julia does not necessarily serve well atm Community	36	4840	March 22, 2023
Statically compiled and statically linked General Usage	35	10133	September 8, 2020
Building stand-alone helloworld produces many dlls, being 200MB big New to Julia	37	6555	November 18, 2021

Blog post: Review of trimming for AoC 2025

Related topics