Hacker News new | past | comments | ask | show | jobs | submit login

One could always create a native python module in Rust/other and call it from Python. It might not work for videogames, for instance, but ML seems to do fine with this approach, and they require a lot of performance from the GPU.



So spend the time doing the hard bit, then introduce some complexity and a software turducken for the sake of calling it from a "simple" language. At which point I'd then ask the question are we really so scared of someone accusing us of overengineering that we're creating more complicated solutions to appear simple and pretending the complexity doesn't exist?


This is basically how Python is useful, calling native modules.

It might not be aesthetically pleasant but it works.

If we think about it, most of the time you do not need to do that because some library author has already done it.

If one needs to write the native code it is not overengineering. It is only overengineering if it was not needed in the first place.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: