21–26 of 26 posts
It would be great if Julia were to take a page from the Rust playbook and have some focused initiatives around making the language more accessible to its potential audience. I've been impressed with how introspective and constructively self-critical the Rust stewardship has been. I don't get the same sense from Julia, but maybe I'm missing things. The "time to first plot" issue bothers me far less than the weak docum…
I have been willing to try Julia for a long time now. Yesterday I finally put time aside to port some stuff I have been doing in Python to Julia. 1st: install Julia - used a snap on Ubuntu, fine 2nd: get jupyter to work with Julia: a bit complex, but achievable 3rd: install Julia support for vscode: Julia kernel keeps crashing in vscode 4th: Port a routine from Python to Julia: some nice language features, some scary…
Use import instead of using if you don't want things in your namespace.
I have been willing to try Julia for a long time now. Yesterday I finally put time aside to port some stuff I have been doing in Python to Julia. 1st: install Julia - used a snap on Ubuntu, fine 2nd: get jupyter to work with Julia: a bit complex, but achievable 3rd: install Julia support for vscode: Julia kernel keeps crashing in vscode 4th: Port a routine from Python to Julia: some nice language features, some scary…
When doing `using SomePackage` it only imports the names that are explicitly exported by `SomePackage`. Even collisions don't cause problems very often because exported type names tend to be fairly unique and when two packages use the same name for a function, there's a strong chance it's actually the same generic function shared between the packages so there's no collision. When that's not the case and the name is fairly generic, e.g. `connect`, then it's quite common to use the API as `SomePackage.connect` rather than as just `connect`. This is quite a bit different from class-based object-oriented languages, so it takes a little while to get used to.
The issues with Parquet files are likely to get sorted out in the near future (a few months), so try again soon.
It would be great if Julia were to take a page from the Rust playbook and have some focused initiatives around making the language more accessible to its potential audience. I've been impressed with how introspective and constructively self-critical the Rust stewardship has been. I don't get the same sense from Julia, but maybe I'm missing things. The "time to first plot" issue bothers me far less than the weak docum…
There's already work in progress to improve Documenter.jl (the package that generates Julia docs) to change the TOC style to something less annoyingly detailed and different from Sphinx [2]. Julia's own manual has grown incrementally, written by various people and definitely needs a once-over by someone who is good at clear technical writing; it's hard to find the time when there's so much other work to be done.
[1] https://github.com/JuliaLang/julia/pull/31954
[2] can't find the PR now but part of a GSoC project
It would be great if Julia were to take a page from the Rust playbook and have some focused initiatives around making the language more accessible to its potential audience. I've been impressed with how introspective and constructively self-critical the Rust stewardship has been. I don't get the same sense from Julia, but maybe I'm missing things. The "time to first plot" issue bothers me far less than the weak docum…
The documentation style (permanent TOC on the right) seems to copy python's Sphinx style. And you are quite right about the lack of visible effort in making error messages more useful.
Earlier quoted context omitted.
The documentation style (permanent TOC on the right) seems to copy python's Sphinx style. And you are quite right about the lack of visible effort in making error messages more useful.
Until very recently, there have been higher priority issues such as complete multithreading support. Now that we have that, error messages are now a top priority (see my other comment). Some work has already been done but not yet merged: https://github.com/JuliaLang/julia/pull/31954 .
The Julia team and community are constantly advancing the frontiers of language design while grounding it in real number crunching applications. I wouldn't be too concerned about trying to have the same documentation and content approach as the Rust community as their goals were to usurp the mindshare of systems programmers (C/C++) with a novel ownership paradigm.
Looking forward to the progress on error messages.