- Iter expressions / LINQ
- High and low effort variants of async/await with Tasks/Futures
- Generics with full monomorphization and traits / Generics with struct monomorphization and constraints over interfaces
- par_iter / Parallel and PLINQ
- crates / nuget packages
Today, when you move past C# or Kotlin, you really aren't improving your productivity by picking any interpreted and dynamically typed languages, but lose out on performance massively. Just look at this throughput graph I posted recently in another discussion: https://github.com/LesnyRumcajs/grpc_bench/discussions/441 pay attention where Python, Ruby, Node and Elixir are.
> pickling
Sounds like if this is the tooling and the task at hand, about the most complex things that should be passing through the pickler are partitioned lists of filenames rather than raw data. E.g. you can have each partition generate a parquet for combining in a final step (pyarrow.concat_tables() looks useful), or if it were some other format you were working with, potentially sending flat arrays back to the parent process as giant bytestrings or similar
This is not to say the limitations don't suck, just that very often there are simple approaches to avoid most of the pain
It’s worth giving it a try if you haven’t before.
But, I have the same sentiment. Although, I find writing quick C++ extensions (swig is incredible) is a good balance.
2. Do not use loops, use itertools. (Python 3.12 got a nice 'batched' function, btw.)
3. Preallocate memory, where possible.
4. multiprocessing.shared_memory may help.
5. Something like cython may help.
6. Combination of multiprocessing with asyncio (or multithreading) may help.
7. memmap file access might help.
You see, you have a lot of options before you need to learn another language.
Most recent example - converting huge amount of xml files to parquet. I started very fast with python + pyarrow, but when I realized that parallelizing execution would help enormously, I hit GIL or picking/unpickling/multiprocessing costs.
It did work in python, in the end, but I feel that writing that in Rust/C# (even if I don't know Rust besides tutorials) in the end would be much more performant.