Simply, the lsp is far less useful. An object might have a dozen methods that act like verbs or some attributes that act as adjectives.
In Julia there is a huge number of functions, that work differently for different types and different combinations of types. So finding the documentation involves finding the right name for a function that does different things for different types, then scrolling down the docs for the the behaviour that corresponds to the specific combination of inputs.
I moved from R/Py to Julia for a while before moving back to Py (and a little bit of Rust).
I love how fast Julia is and the 1-index is fine for me, but I still prefer py for the oop.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
Simply, the lsp is far less useful. An object might have a dozen methods that act like verbs or some attributes that act as adjectives.
In Julia there is a huge number of functions, that work differently for different types and different combinations of types. So finding the documentation involves finding the right name for a function that does different things for different types, then scrolling down the docs for the the behaviour that corresponds to the specific combination of inputs.
I moved from R/Py to Julia for a while before moving back to Py (and a little bit of Rust).
I love how fast Julia is and the 1-index is fine for me, but I still prefer py for the oop.
So there’s no LSP function to just show all of the multi-methods that accept a specific type? That’s a pretty serious tooling limitation.
Maybe Julia sounds better in theory than in practice, if the tooling still isn’t ready for production use.
Well it’s there, in one loooong print out. It’s not as bad as I’m making it out to be, however, I went back to python unfortunately.
The crucial issue with Julia, no error messages.
So I use Julia for things that need to be fast (e.g. moving hdf5 to SQL and ffts) but I use python for everything else (except ggplot).