Mike can step in, but I think it is indeed the plan to have a Julia IDE bundle, causing the exact packages required on the julia and atom side to be invisible implementation details from the user's POV.
On Monday, March 28, 2016 at 1:27:01 PM UTC-4, David Anthoff wrote: > > I think the user experience for almost all people would be much easier if > they install Atom, then add one package for julia support and everything > works. Having multiple Atom packages (julia-language, ink, julia-client, > latex-completion and Jude right now) makes things confusing for most > people, installation a pain and most people probably won’t even discover > all of these packages. > > > > Maybe another solution to this would be to eventually have one “juno” > package that automatically installs all the individual useful plugins for > Atom that make it a good julia IDE. I also don’t think any of this is > urgent, right now the whole Atom story is so experimental in any case that > most likely only a small number of people is using it in the first place. > > > > *From:* [email protected] <javascript:> [mailto: > [email protected] <javascript:>] *On Behalf Of *James Dang > *Sent:* Sunday, March 27, 2016 4:57 AM > *To:* julia-users <[email protected] <javascript:>> > *Subject:* Re: [julia-users] Announcing JuDE: autocomplete and jump to > definition support for Atom > > > > Hi David, I think Jude's functionality is pretty orthogonal to > julia-client so they function pretty well as distinct, easier to manage > packages. julia-client is focused on live code execution and results > visualization while Jude is more about getting traditional IDE tools via > static syntax analysis. Why do you think they should merge? >
