4 ms·
> If I'm going to rewrite - why not go the whole hog and do it in rust We use black at work. One of the challenges with it is that it doesn't play very nicely
by andreareina 3y ago
> If I'm going to rewrite - why not go the whole hog and do it in rust
We use black at work. One of the challenges with it is that it doesn't play very nicely with pandas, specifically its abundant use of []. So we forked it and maintain a trivial patch that treats '[' the same as '.' and everybody's happy.
What was maybe 15 minutes of work for me to get everybody's buy-in to use a formatter would not have been so quick or easy if it had been written in rust and now either we maintain our own repo of binary wheels, or all our devs now need to include rust in their build tooling.
I'm not invested in the argument one way or the other, just wanted to note that having the stack be accessible to easy modification by any user is itself a feature and one some people (including me in general, not so much in this particular case) derive a lot of benefit from.
P.S. cheers and congratulations!
- heyoni 3y agoThis is so on point but is already the case with any package written in C. I feel like there’s such a strong push towards having rust backends for python packages that you might have to learn it to become a decent python developer…and I think I might be ok with that. For the price of having 1 dev on your team understand rust, you can keep using python as a top performing language. We’ve got Ruff, Pydantic and Rye (experimental?) just off the top of my head being written in rust. It seems like that’s where we’re heading as a community.
- andreareina 3y agoI'm talking about the rest of my team being able to use the fork. A compiler and toolchain is much more likely to be installed for c than for rust.
- carlmr 3y agoWith Rust drivers in the Linux kernel I don't think this will be for long.
- andreareina 3y agoGood point, and gcc is getting a roast front end as well!