JulIDE - an IDE for the Julia programming language

Tooling
1

Hi! so i built an IDE for the Julia programming language, since i saw there arent really any Julia IDEs out there, its based on tauri (react and rust), its still in alpha, so expect some bugs and issues.
JulIDE features a code editor based on Monaco, LSP based on LanguageServer.jl, a debugger, a git panel and integrations with pluto.jl and revise.jl
github: GitHub - sinisterMage/JulIde · GitHub
i would greatly appreciate feedback!

9 Likes
2

Very cool. Need to check it out! Good job!

1 Like
3

Thanks! i appreciate that :slight_smile:

4

Earned yourself a first star, too :slight_smile:

1 Like
5

And the award for best README of 2026 goes to @sinisterMage

6

is there such an award? or is it a joke? sorry i am kinda new here :sweat_smile:

1 Like
7

You gotta get a 5star from me too this project is coool WOW. I loved it

1 Like
8

NGL he has the best readme

1 Like
9

thank you so much! i greatly appreciate that :slight_smile:

1 Like
10

The award was newly minted by me for the occasion. Truly outstanding work.

2 Likes
11

ahhh i see, thank you so much, and sorry for my confusion

12

An IDE is an ambitious project!

initial commit to master
committed 6 hours ago

…but I’d recommend putting more effort into it before announcing it.

Also, it’s best to avoid using Julia in your package name or prefixing it with Ju.

1 Like
13

Took it out for a test drive. Sweet.

Easy to install. Familiar layout. Clean design, with less is more. Gone are all the features for a zillion other languages and gone are the endless configurable options. Tastes great, less filling.

2 Likes
14

Do you consider VSCode to be just a text editor?

15

Wow! thank you for trying it out :slight_smile:
did you encounter any issues or bugs? or you have any suggestions? if so, please let me know if there are any!

16

VSCode can be both an IDE and a code editor, just depends on how its configured, when I said I didn’t see any other Julia IDEs, I meant dedicated ones, sorry for the confusion

1 Like
17

Haven’t run into anything I’d call a bug. When I said that the paring down of settings to a set of sensible defaults it was based on my first reaction—where’s SHIFT ENTER to send a block for execution. Muscle memory was screaming. But on thinking it over, I’m still highlighting a block, right? And there’s no shortage keyboard macros to click run, and maybe a little slowdown is going to make me think more about things before letting rip. I did get the one benign warning about breakpoints

warning: field `breakpoints` is never read
  --> src/debugger.rs:39:5
   |
37 | struct DebugSession {
   |        ------------ field in this struct
38 |     stdin: Box<dyn Write + Send>,
39 |     breakpoints: Vec<Breakpoint>,
   |     ^^^^^^^^^^^
   |
   = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default

warning: `julide` (lib) generated 1 warning
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 4.12s
     Running `target/debug/julide`
warning: field `breakpoints` is never read

All in all, I expect to be doing new stuff in it and will let you know should I see anything I think you should know.

1 Like
18

Installed without issue, including dependencies.

Very nice work!