maturin VS ale

This story unfolds as a captivating journey where the agile Flounder, representing the Python programming language, navigates the vast seas of coding under the wise guidance of Sebastian, symbolizing Rust. Central to their adventure are three powerful tridents: cargo, PyO3, and maturin.

-- Maturin on GitHub

My new favorite way to write very fast libraries for Python is to just use Rust and Maturin:

https://github.com/PyO3/maturin

It basically automates everything for you. If you use it with Github actions, it will compile wheels for you on each release for every platform and python version you want, and even upload them to PyPi (pip) for you. Everything feels very modern and well thought out. People really care about good tooling in the Rust world.

Python first, you will be able to experiment quickly with the notebooks. Then maybe write (or rewrite) some modules in Rust that you can expose as python modules, with py03 and maturin. Feel free to publish useful packages on both crates.io and pypi.org, so you can contribute to Python and Rust ecosystems.

Now if you really want to use Rust, you can rewrite only the part that are slowing down your consumer. It's easy by using Py03 and maturin. Maybe also rayon to parallelize.

It's relatively easy to extend Python with project like Py03[0] and Maturin[1]. Polars[2] is the perfect example of that.

It's not easy to push coworkers/companies to use an unfamiliar language. Rust isn't fast to learn. You need very good arguments and a good usecase to make it works.

I doubt that learning Rust will help you more that learning more about the data engineers tools, so this isn't really "worth" your time.

[0] -- https://pyo3.rs/v0.18.3/

[1] -- https://github.com/PyO3/maturin

[2] -- https://www.pola.rs/

In this case, PyO3/maturin does all the setup and getting the module into Python. They also have docs going into a lot more depth on this.

Lastly if you're willing to introduce Rust, I'd consider a gradual approach using native libraries built in rust with PYO3. Check the maturin guide that helps you to streamline the build process of native libraries : https://github.com/PyO3/maturin . From there you could try to find hotspots in your python app and replace those with a native implementation.

I saw no mention of RBS+Steep, the latter providing a LSP. I use it a lot and very much like it, although it's still young and needs love, but it's making good, steady progress! I've been very pleasantly surprised by some of the crazy things Steep can catch, completely statically!

You appear to be working on projects with Sorbet (which I tried to like but found it fell short in practice, notably outside of the app use case i.e it's mostly useless for gems) so it may be a tall order to try on those. Maybe you can give RBS+Steep a shot on some small project?

RBS: https://github.com/ruby/rbs

RBS collection (for those gems that don't ship RBS signatures in `sig`, integrates with bundler): https://github.com/ruby/gem_rbs_collection

Steep: https://github.com/soutaro/steep

VS Code: https://github.com/soutaro/steep-vscode

Sublime Text: https://github.com/sublimelsp/LSP

Vim (I'm working on it): https://github.com/dense-analysis/ale/pull/4671

Support for code quality tools are provided by the ALE plugin. These are supported for PHP:

I mostly agree, though I find Allegro and LispWorks severely lacking in areas too. The companies themselves don't seem to care much about their IDEs. Certainly not in the way JetBrains cares about IntelliJ.

Tucked away in the McCLIM project is Clouseau, which you can quickload and use as a normal user: https://codeberg.org/McCLIM/McCLIM/src/branch/master/Apps/Cl... One small cool thing it does is if you inspect a complex number it will also draw a little x-y vector. (Though trying it out again just now it's overlapping with the text... maybe I should file a bug, but I've only now just learned they moved off github, and I'm not going to make a codeberg account. Friction wins this round.) It does take a while to first compile and load all the dependencies, especially 3bz, another weakness of at least our free Lisps; AFAIK there's still no equivalent of make -j for compiling systems.

I'm a happy vim user (though there is some jank with slimv, admittedly, but it's mostly prevalent around multiple thread situations) and setup the command ,ci to call my own clouseau-inspect function; it just inspects a symbol with clouseau instead of slimv's inspector. Also have a janky watch/unwatch pair of functions that just refreshes the inspector every second. (https://github.com/Jach/dots/blob/master/.sbclrc#L113 if curious, some other junk in .swank.lisp and .vimrc too, and there's https://github.com/dense-analysis/ale/issues/4061 to call sblint on your project...)

But better forms of these sorts of graphical tools are what I hope to one day see more of and are how the free Lisps can close the gap in this area with the commercial Lisps. I believe there's not much Allegro can do that poking around SBCL can't do, but for many things it's just nicer to have a GUI. Want to explore all the symbols and values in a package? Easy enough to script that, but not as nice as just having a table of symbols, and even nicer if you can set watches on some of them. None of the tools need to be tightly integrated with a single IDE either, because all the stuff necessary to debug Lisp is in the running Lisp itself. It's just that the GUI situation continues to suck.

LSP has gotten more popular with other languages and editors, sometimes I wonder if the acronym was made as an inside joke because it's basically how Lisp + Slime/Swank have worked...

Hello Everyone! w0rp here. I thought I'd ask on Reddit if there's anyone out there would like to help maintain ALE. It would be nice to have another willing volunteer who is up for providing relevant feedback on PRs, answering common questions, merging good PRs, and managing GitHub issues. I'll mention to anyone interested that I have a general policy of never closing issues, no matter how old, unless they are actually either solved or invalid. I bear no compulsions to ensure an that a number of issues, which is arbitrary, remains low. I have a relatively simple vetting process, which mostly just requires building trust over time.

A similarly useful list is vim's famous ALE plug-in's list of supported linters:

* https://github.com/dense-analysis/ale/blob/master/supported-...

While less comprehensive¹, this is my go-to list when I start working with a new language. Just brew/yum/apt installing the tool makes it work in the editor²

¹this list mostly has foss,static analyzers, however anyone can contribute (mine was the gawk linting)

²alright,there are some. Tools that might need some setup

Ctrl-X Ctrl-L is line based completion, see :help CTRL-X_CTRL-L for details.

:help ins-completion gets the useful docs, Vim's own docs are very good and worth spending some time learning how to use, so you can learn Vim itself better.

Another favorite of mine is 'gf' to open the filename under the cursor, very useful combined with ^X ^F.

Omni completion is also useful: https://vim.fandom.com/wiki/Omni_completion although you're better off with plugin that uses LSP now, for example https://github.com/dense-analysis/ale

FWIW, I still use regular vim with ale [0] and it does everything I want. It formats files with Black and isort, shows ruff and pyright errors, supports jumping to definitions, and has variable information available on hover. I have collected my config over the past several years, but I pretty rarely encounter errors with it.

[0]: https://github.com/dense-analysis/ale [1] https://github.com/CGamesPlay/dotfiles/blob/master/files/.co...

At some of those syntax things neovim behaves better, and like. But there is https://github.com/dense-analysis/ale.

I replace ALE with :!, like :! %. If the linter output is compatible with default errorformat , then I do :! % > /tmp/linter.txt then :cgetfile (or in one-go: :cgetexpr systemlist(''))

I'm not doing much of anything in Python, but according to :help ale-python-pylint: