4 ms·

My deep interest is multithreaded code. For a software engineer working on business software, I'm not sure if they should be spending too much time debugging mu

My deep interest is multithreaded code. For a software engineer working on business software, I'm not sure if they should be spending too much time debugging multithreaded bugs because they are operating at the wrong level of abstraction from my perspective for business operations. I'm looking for an approach to writing concurrent code with parallelism that is elegant and easy to understand and hard to introduce bugs. This requires alternative programming approaches and in my perspective, alternative notations. One such design uses monotonic state machines which can only move in one direction. I've designed a syntax and written a parser and very toy runtime for the notation. https://github.com/samsquire/ideas5#56-stateful-circle-programs-on-rails https://github.com/samsquire/ideas5#56-stateful-circle-progr... https://github.com/samsquire/ideas4#558-state-machine-formulation https://github.com/samsquire/ideas4#558-state-machine-formul... The idea is inspired by LMAX Disruptor and queuing systems.

btilly 3y ago
And your approach can be built into a system that does multi-threading away from Python, thereby achieving parallelism without requiring that Python supports it as well. That's basically what all machine learning code written in Python does. It calls out to libraries that can themselves parallelize, use the GPU, etc. And then gets the answer back. You get parallelism without any special Python support.
zo1 3y ago
Just to add a bit of my opinion after reading your comment in the context of this thread and not to the merit of your idea. You are precisely the type of person I'd keep very very far away from multithreading in any business software project and also why I advocate the GIL to stay. If you want to do that, go solo in your own time, or try apply for a research position in some giant tech Co.

btilly 3y ago

And your approach can be built into a system that does multi-threading away from Python, thereby achieving parallelism without requiring that Python supports it as well. That's basically what all machine learning code written in Python does. It calls out to libraries that can themselves parallelize, use the GPU, etc. And then gets the answer back. You get parallelism without any special Python support.

zo1 3y ago

Just to add a bit of my opinion after reading your comment in the context of this thread and not to the merit of your idea. You are precisely the type of person I'd keep very very far away from multithreading in any business software project and also why I advocate the GIL to stay. If you want to do that, go solo in your own time, or try apply for a research position in some giant tech Co.