Do you mean Synapse the Matrix server? In my experience, Conduit is much more efficient.
this post was submitted on 26 Mar 2025
546 points (97.1% liked)
Programmer Humor
23848 readers
2404 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
I'll be honest, this only matters when running single services that are very expensive. it's fine if your program can't be pararlelized if the OS does its job and spreads the love around the cpus
I prefer this default. Im sick of having to rein in Numba cores or OpenBlas threads or other out of control software that immediately tries to bottleneck my stack.
CGroups (Docker/LXC) is the obvious solution, but it shouldn't have to be
Python
..so.. so you made it single threaded?
all programs are single threaded unless otherwise specified.
It’s safe to assume that any non-trivial program written in Go is multithreaded
And yet: You’ll still be limited to two simultaneous calls to your REST API because the default HTTP client was built in the dumbest way possible.
load more comments
(3 replies)
load more comments
(5 replies)
Does Python have the ability to specify loops that should be executed in parallel, as e.g. Matlab uses parfor instead of for?
python has way too many ways to do that. asyncio, future, thread, multiprocessing...
Of the ways you listed the only one that will actually take advantage of a multi core CPU is multiprocessing
yup, that's true. most meaningful tasks are io-bound so "parallel" basically qualifies as "whatever allows multiple threads of execution to keep going". if you're doing numbercrunching in pythen without a proper library like pandas, that can parallelize your calculations, you're doing it wrong.
load more comments
(2 replies)
I've always hated object oriented multi threading. Goroutines (green threads) are just the best way 90% of the time. If I need to control where threads go I'll write it in rust.
nothing about any of those libraries dictates an OO approach.
If I have to put a thread object in a variable and call a method on it to start it then it's OO multi threading. I don't want to know when the thread spawns, I don't want to know what code it's running, and I don't want to know when it's done. I just want shit to happen at the same time (90% of the time)
load more comments
(1 replies)
Are you still using matlab? Why? Seriously
I was telling a colleague about how my department started using Rust for some parts of our projects lately. (normally Python was good enough for almost everything but we wanted to try it out)
They asked me why we're not using MATLAB. They were not joking. So, I can at least tell you their reasoning. It was their first programming language in university, it's safer and faster than Python, and it's quite challenging to use.
load more comments
(1 replies)
No, I'm not at university anymore.
Good for you
Poor prof
We weren't doing any ressource extensive computations with Matlab, mainly just for teaching FEM, as we've had an extensive collection of scripts for that purpose, and pre- and some post processing.
load more comments
(1 replies)
load more comments
(10 replies)