Skip Navigation

Programmer Humor @programming.dev

Lena @gregtech.eu

2个月前

Synapse is the epitome of this

72 评论

all programs are single threaded unless otherwise specified.
- It’s safe to assume that any non-trivial program written in Go is multithreaded
  
  But it's still not a guarantee
  
  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.
  
  I absolutely love how easy multi threading and communication between threads is made in Go. Easily one of the biggest selling points.
- 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...
  
  Experimentally, yes
  
  Are you still using matlab? Why? Seriously
- I think OP is making a joke about python's GIL, which makes it so even if you are explicitly multi threading, only one thread is ever running at a time, which can defeat the point in some circumstances.
  
  no, they're just saying python is slow. even without the GIL python is not multithreaded. the thread library doesn't use OS threads so even a free-threaded runtime running "parallel" code is limited to one thread.
  apparently not!
- I initially read this as “all programmers are single-threaded” and thought to myself, “yeah, that tracks”

https://docs.python.org/3/whatsnew/3.13.html#whatsnew313-free-threaded-cpython
- Oooooh this is really cool, thanks for sharing. How could I install it on Linux (Ubuntu)? I assume I would have to compile CPython. Also, would the source of the programs I run need any modifications?
  
  From memory I can only answer one of those: The way I understand it (and I could be wrong), your programs theoretically should only need modifications if they have a concurrency related bug. The global interlock is designed to take a sledgehammer at "fixing" a concurrency data race. If you have a bug that the GIL fixed, you'll need to solve that data race using a different control structure once free threading is enabled.
  I know it's kind of a vague answer, but every program that supports true concurrency will do it slightly differently. Your average script with just a few libraries may not benefit, unless a library itself uses threads. Some libraries that use native compiled components may already be able to utilize the full power of you computer even on standard Python builds because threads spawned directly in the native code are less beholden to the GIL (depending on how often they'd need to communicate with native python code)
  
  In this case, it's a feature of the language that enables developers to implement greater amounts of parallelism. So, the developers of the Python-based application will need to refactor to take advantage of it.

Oh wow, a programming language that is not supposed to be used for every single software in the world. Unlike Javascript for example which should absolutely be used for making everything (horrible). Nodejs was a mistake.
- Nodejs was a mistake.
  More choice is always better
  
  And some of those choices are mistakes.
  
  Citations Needed: Episode 95: The Hollow Vanity of Libertarian "Choice" Rhetoric
  Episode webpage: https://dts.podtrac.com/redirect.mp3/traffic.libsyn.com/secure/citationsneeded/CN95_20191205_choice_Stites_v2.mp3
  Fucking Citations Needed, every time I finish an episode, someone comment something related to it.

don't worry it'll use all the RAM anyway
- I paid for all the memory. I'll use all the memory.
  
  JG Memoryworth
- No RAM gets wasted!

let's be honest here, he actually means 0.01 core performance
- Yes, 0.99 performance being consumed by the interpreter.

Do you mean Synapse the Matrix server? In my experience, Conduit is much more efficient.
- i wish they would switch the reference implementation to conduit
  there is core components on the client side in rust so maybe that's the way for the future
- Yep, I mean as in matrix. There is currently no was to migrate to conduit/conduwuit. Btw from what I've seen conduwuit is more full-featured.
- I may have something to read up on.
  
  The documentation is kinda lacking, but if you could figure out how to set up Synapse then you can probably figure out Conduit too. https://conduit.rs/

I tough this was about excel and was like yeah haha!
But is about Python, so I'm officially offended.

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

https://docs.python.org/3/library/concurrent.futures.html#concurrent.futures.ProcessPoolExecutor

Python
..so.. so you made it single threaded?

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

It only took us how many years?

!lemmySilver

72 评论