minion VS mojo

What finally drove me over the edge was writing some code for a client using the Minion job queue. The queue is solid, but it creates new database connections, thus ensuring that it can’t see anything in your database transactions. I figured out a (hackish) solution, but I was tired of hackish solutions.

Since Minion relies on PostrgeSQL the actual implementation was very simple. Just a few lines of Perl to spawn spare processes and one small change in the SQL query used to dequeue jobs.

https://github.com/modularml/mojo/blob/main/LICENSE Is this not it?

Interesting, but the intent seems similar to Chris Lattner's new Mojo language which arguably has similar characteristics and is further along in its development.

https://docs.modular.com/mojo/

Mojo is a programming language that combines the performance and control inherent in systems languages like C++ and Rust with the flexibility and simplicity of use typical of dynamic languages like Python. Because of its combination of performance, extensibility, and usability, its design makes it possible to construct high-performance systems, which makes it a good option for AI development.

If you take a look at the optimized Mojo code doing the matrix multiply [1], it takes an expert to understand. It’s not just some simple for-loops in Mojo they’re comparing against.

[1] https://github.com/modularml/mojo/blob/5ce18c47a27c0c4123de1...

Mojo truly unlocks a world of possibilities in high-performance computing.

For a concrete example of Liquid Haskell, see how Gabriella Gonzalez safely removed bound checks of high-performance protocol parsing, in "Scrap your Bounds Checks with Liquid Haskell" [1].

With Liquid Haskell, the bound checks are moved from runtime to compile time, semi-automatically handled by SMT-solvers. With static types, programmers can write correct programs faster, and the programs also run faster.

As an aside, speeding up programs with static analysis (constrained dynamism) are also present in Mojo (a variant of Python) or Swift [2].

[1]: https://github.com/Gabriella439/slides/blob/main/liquidhaske... "Scrap your Bounds Checks with Liquid Haskell"

[2]: https://github.com/modularml/mojo/discussions/466 "Mojo and Dynamism"