The release of Julia 2.0 could spark additional interest in the Julia community and thus, provide a unique opportunity to promote Julia. What steps should the Julia community take from now until the release of Julia 2.0 to bring Julia to the next level of popularity?

Exactly. It seems to me that things are actually going fine. We just need to keep that moving. Julia is almost entirely built on pull requests to base and packages. Code, docs whatever: PRs are where things actually happen and real decisions and changes are made. Not in these threads. So improving…

[image] johnmyleswhite: I’ll make a radical proposal: let’s close this thread. Before closing the thread, I would suggest one last thing. I hope the Julia community can revisit the topic of this thread each year through a roundtable at Julia Con or a question in the annual survey.

[image] xiaoxi: I hope the Julia community can revisit the topic of this thread I would not worry about this. A variation of this thread seems to happen every month or so.

[image] rdavis120: would prefer to require registered packages to have every exported function and the corresponding arguments and return type to be documented I agree, but this is hard to automate. You can keep an eye on #new-packages-feed on Slack (or Zulip) and leave a blocking comment on …

If I might make a few final constructive comments before this gets closed, I do think we need a “clearer” ecosystem for users. As I’ve come to understand Julia, it tries to have a minimal standard library with only some basic packages likely to have fairly broad applicability. For example, the Lin…

[image] dlakelan: I sort of do a fair amount of this too. And it doesn’t feel that difficult. I think this is another very big problem to getting new users to adopt Julia–the difficulty in recognizing the importance of defaults and informational constraints. Among experienced Julia devs, th…

coincidentally enough, I disagree with your preference about the right choice of default as well as with your characterization of the opposition to that choice for each and every item on that list…besides maybe 4.

[image] goerz: [image] rdavis120: would prefer to require registered packages to have every exported function and the corresponding arguments and return type to be documented I agree, but this is hard to automate. You can keep an eye on #new-packages-feed on Slack (or Zulip) and leave a b…

For instance, I’d love to be able to simply do Pkg.add_organization( "JuliaMath" ) Organizations could already now publish a wrapper package that reexports all (or at least the best supported) packages in the org. You probably want to exclude experimental ones.

I’m not surprised! All of these defaults are examples I chose because they appeal to the kinds of people who are extremely used to writing Julia, have been using it for a long time (possibly pre-1.0) and post on the Discourse and Slack. I picked them because they’re examples where the opinions of a …

[image] ParadaCarleton: Other examples of poor defaults that are easy to miss when you’re learning Julia: FMA (not default because it could confuse devs if someone ran a computation on a pre-2008 computer) The inability to use positional arguments with keywords (because then, developers wouldn…

What steps should the Julia community take to bring Julia to the next level of popularity?

Community

Topic		Replies	Views
What can we do to make Julia grow fast? Community	114	13719	November 16, 2018
How do we Julians win big when the situation is so unfair? Community	100	6199	November 22, 2023
Can juliac increase julia adoption? General Usage question	61	3945	April 14, 2025
Designated Target Audience of Julia 1.0? Community	152	11193	July 25, 2018
Julia losing popularity among Data Science users (KDnuggets Software Poll) Community	146	20718	June 23, 2018

What steps should the Julia community take to bring Julia to the next level of popularity?

Related topics