Suggestions
Sviatoslav Kalina
Software Engineer
Sviatoslav Kalina is a Software Engineer based in Bucharest, Romania who works at SD Solutions.1 He has a profile on LinkedIn with the username sviatoslavkalina.
Some key details about Sviatoslav Kalina:
- He studied at Simon Kuznets Kharkiv National University of Economics.1
- He has over 6,000 followers on LinkedIn.1
- Previously, he worked at a company called CybearSoft, which shut down in May 2022.2
While the available information is limited, it appears Sviatoslav Kalina is an experienced software engineer who has worked for multiple companies in his career. His educational background in economics combined with his current role as a software engineer suggests he may have transitioned into the tech industry after his studies.
Highlights
I’m happy to share that I’ve obtained a new certification: Ethereum and Solidity: The Complete Developer's Guide from Udemy!
GIL(Global Interpreter in Lock soon) will be OPTIONAL in python 3.13 or 3.14 **current latest version is 3.12.5
It might sound like a distant dream to be free from the GIL, but it’s actually closer than ever.
With the upcoming release of Python 3.13 in October or next one, there’s a groundbreaking feature on the horizon: the ability to configure the Python interpreter without the GIL 🤯. This is a massive shift that could be a game changer for software engineering.
Of course, it's important to note that the "no-GIL" option may not immediately deliver 100% of the performance improvements we might hope for. There are complexities involved, and the ecosystem will need time to adapt fully. However, the potential impact is enormous.
You might argue that Python has managed well with the GIL, especially since you can use multiprocessing to achieve parallelism. While that's true, multiprocessing comes with its own trade-offs. Each process in a multiprocessing setup runs its own interpreter instance and has its own memory allocation. This isolation means that, although you can bypass the GIL, the approach isn't always cost-effective. The overhead of spawning processes and the need for inter-process communication can reduce the overall efficiency, especially for tasks requiring a lot of shared data.
The introduction of a no-GIL option offers a different paradigm, potentially allowing for true parallelism in multi-threaded programs without the same level of overhead. This could lead to more efficient resource use and faster performance in many scenarios, fundamentally changing the way Python is used in multi-threaded applications.
What’s your take on the no-GIL option in Python 3.13? Do you think it will revolutionize Python development, or could it introduce more challenges than benefits? Share your thoughts below!
add here video where you can see little benchmarks and professional opinion for this topic 🤗
https://lnkd.in/dy64MnGj
Post on Reddit with a link with discussion about committing to Python source code possibility to turn off the GIL https://lnkd.in/dEUJy7_M
and commit to the Python repository itself https://lnkd.in/dfQ35HCB
