3 ms·

But you have to type `python3` which is 7 letters to 5, if we're counting :) Seriously though, it's hard to write one manual which gives everyone the perfect o

But you have to type `python3` which is 7 letters to 5, if we're counting :) Seriously though, it's hard to write one manual which gives everyone the perfect on-ramp for their needs. I actually think it's fair to aim it low, make it easy for matlab refugees to get started, interactively. People who know how namespacing works in several other languages (and intend to write big projects) are the ones well-equipped to know how to dig deeper. Nobody has been victimised!

masklinn 8y ago
> But you have to type `python3` which is 7 letters to 5, if we're counting :) Of course, that was actually a pretty big consideration during the "vcs wars", both the length and the alternation of VCS commands. > I actually think it's fair to aim it low, make it easy for matlab refugees to get started, interactively. Then don't whine that people use that, and police your community. > Nobody has been victimised! Well how's that for dishonesty. ChrisRackauckas pretty much goes "this article is invalid because you're doing exactly what the languages suggests and incentivises" half a dozen comments above.
- improbable22 8y ago
  My point was that counting letters in one short command seems myopic here, it's not something you type in isolation. Julia package names tend to be much longer and more explicit than python/R ones. But julia code (at least mine) tends to be more compact, partly because I can write things like A ⊗ B instead of np.kron(A,B). As far as I'm aware there is no budget for a police force. There is, however, a double-your-money-back guarantee on all advice from blog posts! I do think the manual could be clearer about using/import. Perhaps this should be emphasised under workflow [1], and packaging differences from Python included in the list [2]. The experts have forgotten what the pain-points were; contributions from those who have not are thus welcomed. [1] https://docs.julialang.org/en/v1/manual/workflow-tips/ https://docs.julialang.org/en/v1/manual/workflow-tips/ [2] https://docs.julialang.org/en/v1/manual/noteworthy-differences/#Noteworthy-differences-from-Python-1 https://docs.julialang.org/en/v1/manual/noteworthy-differenc...

masklinn 8y ago

> But you have to type `python3` which is 7 letters to 5, if we're counting :) Of course, that was actually a pretty big consideration during the "vcs wars", both the length and the alternation of VCS commands. > I actually think it's fair to aim it low, make it easy for matlab refugees to get started, interactively. Then don't whine that people use that, and police your community. > Nobody has been victimised! Well how's that for dishonesty. ChrisRackauckas pretty much goes "this article is invalid because you're doing exactly what the languages suggests and incentivises" half a dozen comments above.

improbable22 8y ago
My point was that counting letters in one short command seems myopic here, it's not something you type in isolation. Julia package names tend to be much longer and more explicit than python/R ones. But julia code (at least mine) tends to be more compact, partly because I can write things like A ⊗ B instead of np.kron(A,B). As far as I'm aware there is no budget for a police force. There is, however, a double-your-money-back guarantee on all advice from blog posts! I do think the manual could be clearer about using/import. Perhaps this should be emphasised under workflow [1], and packaging differences from Python included in the list [2]. The experts have forgotten what the pain-points were; contributions from those who have not are thus welcomed. [1] https://docs.julialang.org/en/v1/manual/workflow-tips/ https://docs.julialang.org/en/v1/manual/workflow-tips/ [2] https://docs.julialang.org/en/v1/manual/noteworthy-differences/#Noteworthy-differences-from-Python-1 https://docs.julialang.org/en/v1/manual/noteworthy-differenc...