Thanks for the info. I did look into JETLS.jl some time ago. Might be interesting someday. I initially used LanguageServer.jl but I recently switched to a custom build languageserver in Rust that uses an AST parser to parse Julia code with some post processing to build a symbol table for stuff like “Goto definition” and such. Type inference is rather difficult/impossible for Julia using only static analysis.
2 Likes
Are you using MacOS or Linux? Both are on the TODO list.
Apologies, I should have said, I use Arch Linux. 
2 Likes
@elan8 It does look amazing, I love the design and it definitely moves the goal posts! I am happy to donate to a great home-grown software project, especially FOSS, but as a pure unpaid hobbyist, I would not be in the market to buy your IDE outright. But I am really impressed by what you’ve done. I will look out for a version that makes it to Arch’s AUR and I’ll give it a try. I wish you every success!
As a Windows user who find the current Julia Extension Debugging experience to be “not good” I’d be happy to give this a try.
Yet having the Debugger only in the pro option makes it less attractive to try.
Setting Remote Development, AI Coding Assist and Pair Programming as the higher pricing option makes more sense to me.
On top of that, I’d be happy for an option without “Integrated Julia” which works on my pre installed Julia.
Also on Windows it would be great to have a Portable version of the IDE.
2 Likes
It looks very promising. Apart from obvious features such as support for additional operating systems and remote work, I’d like to highlight support for MCP (Model Context Protocol) in the Julia REPL. Some time ago I became interested in the package originally developed by @hexaeder called MCPRepl.jl (and its derivatives), and I put some work to a similar package belonging to the same category and I find such feature very useful (though still not perfect).
Moreover, one, I believe an important point, concerns the use of the Julia name in as I understand your commercial product. As far as I know, Julia is a registered trademark, so without explicit permission for commercial use this may violate trademark law. It might currently be and could become even a more serious issue in the medium‑to‑long term. I would recommend verifying this information and, if accurate, contacting the trademark owners to discuss a solution. Just to be clear, this is absolutely not to discourage you working on a commercial product - I hope this intent remains an honest, constructive suggestion, not a deterrent.
2 Likes
Congratulations, I’ve watched the video on the website and it looks pretty good.
However, I haven’t downloaded and installed the software and this post is a fair critic which I shared the similar thoughts.
Given all the feedback I got from the Julia community, I have decided to make JuliaJunction available open source. Pro features might be offered via a plugin system in the future. I need to do some cleaning up: I will add a new post once the repository on Github is available.
16 Likes
FWIW you can also try “source available” in order to get off the ground, as a lesser alternative to open source. That is more reversible than releasing under an open-source license, if your commercial strategy changes, and may help you get the experience to decide whether to open-source the core of your IDE (open-source parts, have other parts as paid “pro” features / plugins).
People will tell you that they won’t even look/try if your product is not open-source. But many people really mean: They won’t try unless they can look at the code (without signing an NDA) and install from sources.
Whether the license is MIT or AGPL or “click an EULA” (without having to contact you as a sales-person) probably doesn’t matter too much for getting people to give it a spin.
cf eg dyad-lang/LICENSE.md at main · DyadLang/dyad-lang · GitHub
3 Likes
QCAD is an example of software that is available both as open source and with a “professional”, paid license: QCAD - QCAD: 2D CAD
In addition, they offer a paid e-book.
I think, one advantage of the paid version is that it comes with an installer. For the open-source version, you need Git and a compiler to install it. Another advantage are improved import/export filters.
1 Like