Seth Stadick
@ducktapeprogrammer.bsky.social
Bioinformatics. Rust. Mojo.
There’s dozens of us!
January 5, 2026 at 2:20 PM
There’s dozens of us!
I use it in place of both Rust and Python! 2026 should be the year they open source the compiler.
January 5, 2026 at 2:20 PM
I use it in place of both Rust and Python! 2026 should be the year they open source the compiler.
It’s hard to recommend till it’s truly open source, but there’s a lot to like for sure!
December 9, 2025 at 5:24 PM
It’s hard to recommend till it’s truly open source, but there’s a lot to like for sure!
With @Modular looking to hit Mojo 1.0 and open source the Mojo compiler in 2026, I strongly suspect we'll see a huge uptick in Mojo usage in bioinformatics and data science next year.
December 9, 2025 at 4:32 PM
With @Modular looking to hit Mojo 1.0 and open source the Mojo compiler in 2026, I strongly suspect we'll see a huge uptick in Mojo usage in bioinformatics and data science next year.
> “match” statement and enums
Overall, it's not going to have the sort of fantastic stability and backwards compat of Rust, but it should be better than Python at managing changes it seems.
Overall, it's not going to have the sort of fantastic stability and backwards compat of Rust, but it should be better than Python at managing changes it seems.
December 5, 2025 at 9:47 PM
> “match” statement and enums
Overall, it's not going to have the sort of fantastic stability and backwards compat of Rust, but it should be better than Python at managing changes it seems.
Overall, it's not going to have the sort of fantastic stability and backwards compat of Rust, but it should be better than Python at managing changes it seems.
Agreed! For the most part Rust intuitions carry over really well.
Learning to think like a borrow checker pays off I guess!
Learning to think like a borrow checker pays off I guess!
December 3, 2025 at 3:22 AM
Agreed! For the most part Rust intuitions carry over really well.
Learning to think like a borrow checker pays off I guess!
Learning to think like a borrow checker pays off I guess!
It used to be more useful when mojo could had widespread implicit copies. But they've since moved to something much more like Rust's Copy/Clone traits that leads to explicit copies, and so the ^ to force the use of the `__moveinit__` transfer isn't needed as much, and I keep using it out of habit
December 3, 2025 at 2:10 AM
It used to be more useful when mojo could had widespread implicit copies. But they've since moved to something much more like Rust's Copy/Clone traits that leads to explicit copies, and so the ^ to force the use of the `__moveinit__` transfer isn't needed as much, and I keep using it out of habit