this post was submitted on 15 Sep 2023
30 points (75.9% liked)

Rust

5398 readers
51 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
30
Should I Rust or should I Go? (kerkour.com)
submitted 9 months ago by [email protected] to c/[email protected]
21 comments fedilink hide all child comments
 

I think some raised points are relevant...

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 9 months ago

I work on a team that has some old projects in python that we're gradually deprecating. A major one is stuck on 3.7 because 3.8 added automatic async mocking (which is great!), but this broke the existing third-party async mocking framework and it's never been updated to be compatible with newer Python versions. So we'd have to invest time in porting all the tests from the 3rd-party framework to the standard library, but it's not worth it because we're hoping to deprecate the whole project soon anyway.