I have been willing to try Julia for a long time now.
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: importing a package exposes all its functions to the all namespace - this seems quite awful! (EDIT: Thank you for pointing out that I should use `import` instead of `use`, in order not to put everything in the same namespace). 5th: Try to read a Parquet file - doesn't work because it was compressed with zstd (something all 3 libraries for parquet in Python support) 6th: realize that there is no package in Julia that even allows to write parquet files Conclusion: maybe in a few years Julia will be my go-to language, but right now, it's too underdeveloped in order to be able to do real work with it.
Posted by wtdata on Aug 2, 2019, 1:16 PM
Tags
Related issues
- The only thing keeping me on VSCode these days is the remote SSH development.
- Something similar was done in a sheep model: "A bioactive supramolecular and covalent polymer scaffold for cartilage repair in a sheep m...
- Proposal for OpenHarmony Adaptation of [ ThreadPool ]
- Proposal for a pipe-like operator to chain constructor/method invocations without nesting
- Implement support for Node Stashing
- RSC and CDN interaction makes next.js inefficient for highload projects
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
support (E-commerce)
The only thing keeping me on VSCode these days is the remote SSH development.
Something similar was done in a sheep model: "A bioactive supramolecular and covalent polymer scaffold for cartilage repair in a sheep m...
Proposal for OpenHarmony Adaptation of [ ThreadPool ]
Proposal for a pipe-like operator to chain constructor/method invocations without nesting
Implement support for Node Stashing
RSC and CDN interaction makes next.js inefficient for highload projects
Extract Action Notifier framework for push notifications
Improve support for monorepo by supporting git options such as depth, and sparse checkout
I have been willing to try Julia for a long time now.
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: importing a package exposes all its functions to the all namespace - this seems quite awful! (EDIT: Thank you for pointing out that I should use `import` instead of `use`, in order not to put everything in the same namespace). 5th: Try to read a Parquet file - doesn't work because it was compressed with zstd (something all 3 libraries for parquet in Python support) 6th: realize that there is no package in Julia that even allows to write parquet files Conclusion: maybe in a few years Julia will be my go-to language, but right now, it's too underdeveloped in order to be able to do real work with it.
Comments (0)
No comments yet. Start the discussion.