Uploaded November 2026 | Updated November 2026, 5 days ago
The State of BioJulia by Kevin Bonham, PhD
PreTalx: pretalx.com/juliacon-2026/talk/3LGMBE
The BioJulia organization began as `Bio.jl` circa January 2014 (julia v0.2 era) and has grown into a loosely organized collection of packages for computational biology, from plotting protein structures (`BioMakie.jl`) to performing matrix manipulations on single-cell RNA sequencing data (`SingleCellProjections.jl`) to low-level biological file type I/O (`Automa.jl`, `FASTX.jl`, `XAM.jl`). Here, we will provide a brief history of the Org and recent efforts to provide more structure for the community, as well as growth areas and a vision for the future.
Computational biology has a rich history, and in many ways julia is an ideal language for working biologists, as it provides high-level interactivity, an excellent data stack, and the ability to optimize low-level performance. Yet growth of the Bio community has been slow. The purpose of this talk is threefold:
1. To provide a history of the organization, highlighting the unique aspects of julia for computational biology development, and the contributions that BioJulia community members have made to the broader julia ecosystem.
2. To describe recent and on-going efforts to improve the structure of the organization and community.
3. To share a vision for the future growth of BioJulia, and to solicit feedback from the community on priorities and opportunities for outreach.
Kevin Bonham asked his first Stack Overflow question about dictionaries in julia in June of 2014, and has been an active contributor across the julia ecosystem for more than 10 years. He became an admin of BioJulia sometime around 2020.
The State of BioJulia by Kevin Bonham, PhD
PreTalx: pretalx.com/juliacon-2026/talk/3LGMBE
The BioJulia organization began as `Bio.jl` circa January 2014 (julia v0.2 era) and has grown into a loosely organized collection of packages for computational biology, from plotting protein structures (`BioMakie.jl`) to performing matrix manipulations on single-cell RNA sequencing data (`SingleCellProjections.jl`) to low-level biological file type I/O (`Automa.jl`, `FASTX.jl`, `XAM.jl`). Here, we will provide a brief history of the Org and recent efforts to provide more structure for the community, as well as growth areas and a vision for the future.
Computational biology has a rich history, and in many ways julia is an ideal language for working biologists, as it provides high-level interactivity, an excellent data stack, and the ability to optimize low-level performance. Yet growth of the Bio community has been slow. The purpose of this talk is threefold:
1. To provide a history of the organization, highlighting the unique aspects of julia for computational biology development, and the contributions that BioJulia community members have made to the broader julia ecosystem.
2. To describe recent and on-going efforts to improve the structure of the organization and community.
3. To share a vision for the future growth of BioJulia, and to solicit feedback from the community on priorities and opportunities for outreach.
Kevin Bonham asked his first Stack Overflow question about dictionaries in julia in June of 2014, and has been an active contributor across the julia ecosystem for more than 10 years. He became an admin of BioJulia sometime around 2020.


, built on byte-precise lowering and abstract interpretation. This year, we focus on the core design behind it: loading parts of user code to reuse Julias macro handling and compiler type inference. We compare this runtime-integrated approach with the overhauled LanguageServer.jl/JuliaWorkspaces.jl stack and demo its progress on real-world code.
At JuliaCon 2025, we introduced [JETLS.jl](https://github.com/aviatesk/JETLS.jl), then an early-alpha Julia language server built on [JET.jl](https://github.com/aviatesk/JET.jl)s abstract interpretation and [JuliaLowering.jl](https://github.com/JuliaLang/julia/tree/master/JuliaLowering)s byte-precise, provenance-tracking lowering. One year later, this talk goes beyond a progress report to examine the core design that makes this compiler-grounded analysis possible.
JETLS selectively loads parts of the target program into its analysis process. This runtime integration enables JuliaLowering to execute the program’s actual macros while preserving byte-precise source provenance, and JET to reuse Julia’s compiler inference to derive type information for source-level developer tooling.
We compare this design in depth with the [LanguageServer.jl](https://github.com/julia-vscode/LanguageServer.jl)/[JuliaWorkspaces.jl](https://github.com/julia-vscode/JuliaWorkspaces.jl) stack, which has undergone a major overhaul over the past year. Rather than presenting JETLS simply as a replacement, we place the two approaches on a spectrum of runtime integration: JETLS aims to provide precise information about macro expansion and lowering, together with compiler-inferred types, while the largely static approach prioritizes responsiveness and safety and benefits from greater production maturity.
These architectural differences become concrete in a live demo using real-world code from CSV.jl and JuliaFormatter.jl. We show how JETLSs runtime-integrated design translates into practical editor features, most of which were either early prototypes at last years talk or did not yet exist.
Finally, we summarize JETLSs current feature coverage, installation and environment isolation, and editor setup. We also briefly show how the same analysis is exposed through a CLI for CI and AI-agent workflows, showcasing agentic bugfixes drawn from a [Julia Base audit with JETLS](https://github.com/JuliaLang/julia/issues/62526).
Time permitting, we share performance measurements before outlining future work. JETLS: Bringing Julia’s runtime into language-server analysis | Kadowaki, Pfitzner](https://i.ytimg.com/vi/m-K5Wij8Q38/mqdefault.jpg)







