âšī¸ Skipped - page is already crawled
| Filter | Status | Condition | Details |
|---|---|---|---|
| HTTP status | PASS | download_http_code = 200 | HTTP 200 |
| Age cutoff | PASS | download_stamp > now() - 6 MONTH | 0.2 months ago |
| History drop | PASS | isNull(history_drop_reason) | No drop reason |
| Spam/ban | PASS | fh_dont_index != 1 AND ml_spam_score = 0 | ml_spam_score=0 |
| Canonical | PASS | meta_canonical IS NULL OR = '' OR = src_unparsed | Not set |
| Property | Value |
|---|---|
| URL | https://www.theserverside.com/video/Pythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo |
| Last Crawled | 2026-04-16 09:08:45 (4 days ago) |
| First Indexed | 2024-07-09 22:30:28 (1 year ago) |
| HTTP Status Code | 200 |
| Meta Title | Python's GIL removal is a poison pill and benefits Mojo | TheServerSide |
| Meta Description | Language architects want to remove Python's GIL from the CPython interpreter, but doing so will kill the language. |
| Meta Canonical | null |
| Boilerpipe Text | A major criticism of the Python programming language is that it can't thread across cores. The reason is because of the CPython's Global Interpreter Lock (GIL).
The inability to take advantage of more than one core in a multi-CPU system seriously limits
Python performance
. It's one of the reasons why Python embarrassingly lags its peers when it comes to speed and efficiency.
Developers have begged Python's stewards for almost 30 years to fix the GIL. With the steering committee's recent acceptance of
PEP 703
, it looks like Python's GIL removal might happen.
It's
a bad idea
.
Python's GIL is a poison pill
Removing Python's GIL is a poison pill. It will inevitably
kill off Python as we know it
.
Every piece of Python code that runs on the CPython interpreter assumes safe, single-threaded execution. Removing Python's GIL changes that assumption. Every library or Python program ever written that might be impacted by multithreaded data access will have to be retested and potentially rewritten.
Amid the transition from GIL to no-GIL Python runtimes, existing Python projects will likely have to maintain two codebases: one for GIL-based runtimes and another for where Python's GIL is removed. That promises to be a nightmare for open-source projects for which maintaining a single distribution is difficult enough.
Furthermore, the removal of the GIL will have negative impacts that extend beyond the boundaries of Python's interpreter.
Due to its many shortcomings, Python is seldom used to implement actual machine learning routines or run neural networks. Python's main use case is to simply format and massage input data as well as feed it to functions and routines that are implemented in languages such as C++ or Java that are more capable of threading across cores.
However, those functions expect to be invoked in a safe and single-threaded manner. Many of those programs that Python interacts with will require extra tests, updates and dual maintenance as well.
Python 2 to 3 all over again
All of this should feel familiar to maintainers of Python libraries. They were forced to do something similar with the fumbled switch from Python 2 to Python 3, when the stewards of the Python language turned their backs on the community and abandoned backwards compatibility.
During the Python 2 to 3 debacle, developers had little choice but to submit to the dictates of the language stewards and migrate. They received little lead time about the backwards incompatibility issues, but because no viable alternatives existed at the time, organizations that were heavily committed to Python were forced into expensive and disruptive Python version migrations.
Python fans likely have little appetite to go through that again for the GIL-to-no-GIL transition.
Fortunately, things are different now. The GIL's removal is slated to take five years, and my guess is it will take longer. Developers and architects will have time to plan around this change, and if they perform due diligence, their plans should involve completely porting away from Python.
Mojo to the rescue
The Mojo programming language didn't exist when developers struggled with the hastily forced move to Python 3. But it does now, and it will become the de-facto target runtime if Python swallows the no-GIL poison pill.
Mojo's creators knew that it's difficult to teach an old dog new tricks, so they built Mojo to fully support Python code. Just paste Python code into a Mojo file, and
it not only runs
, but it also immediately runs multiple times faster.
Mojo fully supports Python syntax. If not for the flame emoji extension, casual onlookers wouldn't even realize this was Mojo code and not Python.
Furthermore, Mojo works across the entire AI stack, from the CUDA cores on the GPU to the CPU-bound Python scripts that run on the desktop. C and C++ functions that will require updates to support multi-threaded Python code can be written in Mojo as well.
Many of the most popular, open-source machine-learning libraries are already ported to Mojo. Why would anyone who supports a Python project not do the same, if the stewards of the Python language once again force an unnecessary rewrite of all your working code?
I've always said that once the first, full-increment release of Mojo arrives, no greenfield AI or ML projects will be written in Python. All new projects will be developed using a Mojo-first approach, because coding against a CPython runtime won't make sense anymore.
Similarly, if Python removes the GIL, project leaders forced to reckon with rewrites and the long-term prospects of their codebase's health will move to Mojo as well. It will simply be negligent not to do so.
Slow at runtime and slow to adapt
Many developers in the Python community are frustrated with the language's slow evolution. Discussion of finally removing the GIL after 30 years has understandably excited them, but in their excitement over finally being heard, they fail to see the big picture.
The removal of Python's GIL is a poison pill that will kill the language and send users fleeing to higher ground and to the Mojo language. So long as Mojo presents a fast, efficient and professionally maintained alternative, the Python community should leave the GIL well enough alone.
Darcy DeClute is a technical trainer and Agile coach who helps organizations apply Scrum-based principles to adopt a modern DevOps stack. She is a certified Professional Scrum Master, Professional Scrum Developer and Professional Scrum Product Owner as well as author of
Scrum Master Certification Guide. |
| Markdown | [](https://www.theserverside.com/) [ ](https://www.theserverside.com/) [](https://www.techtarget.com/)
[Sign-up now. Start my free, unlimited access.](https://www.theserverside.com/login?fromURL=https%3A%2F%2Fwww.theserverside.com%2Fvideo%2FPythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo)
[Login](https://www.theserverside.com/login?fromURL=https%3A%2F%2Fwww.theserverside.com%2Fvideo%2FPythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo) [Register](https://www.theserverside.com/register?fromURL=https%3A%2F%2Fwww.theserverside.com%2Fvideo%2FPythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo)
[Informa TechTarget](https://www.informatechtarget.com/) [Explore the Network](https://www.theserverside.com/video/Pythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo)
- [App Architecture](https://www.techtarget.com/searchapparchitecture/)
- [Software Quality](https://www.techtarget.com/searchsoftwarequality/)
- [Cloud Computing](https://www.techtarget.com/searchcloudcomputing/)
- [Security](https://www.techtarget.com/searchsecurity/)
- [AWS](https://www.techtarget.com/searchaws/)
[An Informa TechTarget Publication](https://www.informatechtarget.com/) [Explore our brands](https://www.informatechtarget.com/our-brands)
[RSS](https://www.theserverside.com/rss)
- - [Core Java](https://www.theserverside.com/resources/Core-Java-APIs-and-programming-techniques)
- [DevOps](https://www.theserverside.com/resources/DevOps-driven-cloud-native-app-development)
- [More Topics](https://www.theserverside.com/video/Pythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo)
- [Development](https://www.theserverside.com/resources/Software-development-best-practices-and-processes)
- [Frameworks](https://www.theserverside.com/resources/Front-end-back-end-and-middle-tier-frameworks)
- [Skills and career](https://www.theserverside.com/resources/Professional-skills-development-and-career-advice)
- [Tools](https://www.theserverside.com/resources/Development-tools-for-continuous-software-delivery)
[Other Content](https://www.theserverside.com/video/Pythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo)
- [Videos](https://www.theserverside.com/videos)
- [Definitions](https://www.theserverside.com/definitions)
- [Webinars](https://www.theserverside.com/webinars)
- [Sponsored Sites](https://www.theserverside.com/sponsored_communities)
- [More](https://www.theserverside.com/video/Pythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo)
- [Answers](https://www.theserverside.com/answers)
- [Features](https://www.theserverside.com/features)
- [Opinions](https://www.theserverside.com/opinions)
- [Quizzes](https://www.theserverside.com/quizzes)
- [Tech Accelerators](https://www.theserverside.com/techaccelerators)
- [Tips](https://www.theserverside.com/tips)
- [Tutorials](https://www.theserverside.com/tutorials)
- [Home](https://www.theserverside.com/)
- [Core Java APIs and programming techniques](https://www.theserverside.com/resources/Core-Java-APIs-and-programming-techniques)
# Python's GIL removal is a poison pill and benefits Mojo
By
- [Darcy DeClute](https://www.techtarget.com/contributor/Darcy-DeClute), Scrumtuous Inc.
Published: 09 Jul 2024
Related Videos
- [](https://www.techtarget.com/searchitoperations/video/No-GIL-Python-is-a-mistake)
[No-GIL Python is a mistake](https://www.techtarget.com/searchitoperations/video/No-GIL-Python-is-a-mistake)
- [How to print any star pattern in Python -- or Mojo](https://www.theserverside.com/video/How-to-print-any-star-pattern-in-Python-or-Mojo)
- [](https://www.theserverside.com/video/SonarQube-tutorial-Get-started-with-continuous-inspection)
[SonarQube code coverage tutorial for beginners](https://www.theserverside.com/video/SonarQube-tutorial-Get-started-with-continuous-inspection)
- [](https://www.theserverside.com/video/Camel-case-vs-pascal-case-vs-snake-case-vs-kebab-case)
[Camel case vs. pascal case vs. snake case vs. kebab case](https://www.theserverside.com/video/Camel-case-vs-pascal-case-vs-snake-case-vs-kebab-case)
- [View All Videos](https://www.theserverside.com/videos)
[View All Videos](https://www.theserverside.com/videos)
- Share this item with your network:
A major criticism of the Python programming language is that it can't thread across cores. The reason is because of the CPython's Global Interpreter Lock (GIL).
The inability to take advantage of more than one core in a multi-CPU system seriously limits [Python performance](https://www.theserverside.com/tip/Tips-to-improve-Python-performance). It's one of the reasons why Python embarrassingly lags its peers when it comes to speed and efficiency.
Developers have begged Python's stewards for almost 30 years to fix the GIL. With the steering committee's recent acceptance of [PEP 703](https://peps.python.org/pep-0703/), it looks like Python's GIL removal might happen.
It's [a bad idea](https://www.techtarget.com/searchitoperations/video/No-GIL-Python-is-a-mistake).
## Python's GIL is a poison pill
Removing Python's GIL is a poison pill. It will inevitably [kill off Python as we know it](https://www.theserverside.com/blog/Coffee-Talk-Java-News-Stories-and-Opinions/Is-Pythons-GIL-the-software-worlds-biggest-blunder).
Every piece of Python code that runs on the CPython interpreter assumes safe, single-threaded execution. Removing Python's GIL changes that assumption. Every library or Python program ever written that might be impacted by multithreaded data access will have to be retested and potentially rewritten.
Amid the transition from GIL to no-GIL Python runtimes, existing Python projects will likely have to maintain two codebases: one for GIL-based runtimes and another for where Python's GIL is removed. That promises to be a nightmare for open-source projects for which maintaining a single distribution is difficult enough.
Furthermore, the removal of the GIL will have negative impacts that extend beyond the boundaries of Python's interpreter.
Due to its many shortcomings, Python is seldom used to implement actual machine learning routines or run neural networks. Python's main use case is to simply format and massage input data as well as feed it to functions and routines that are implemented in languages such as C++ or Java that are more capable of threading across cores.
However, those functions expect to be invoked in a safe and single-threaded manner. Many of those programs that Python interacts with will require extra tests, updates and dual maintenance as well.
## Python 2 to 3 all over again
All of this should feel familiar to maintainers of Python libraries. They were forced to do something similar with the fumbled switch from Python 2 to Python 3, when the stewards of the Python language turned their backs on the community and abandoned backwards compatibility.
During the Python 2 to 3 debacle, developers had little choice but to submit to the dictates of the language stewards and migrate. They received little lead time about the backwards incompatibility issues, but because no viable alternatives existed at the time, organizations that were heavily committed to Python were forced into expensive and disruptive Python version migrations.
Python fans likely have little appetite to go through that again for the GIL-to-no-GIL transition.
Fortunately, things are different now. The GIL's removal is slated to take five years, and my guess is it will take longer. Developers and architects will have time to plan around this change, and if they perform due diligence, their plans should involve completely porting away from Python.
## Mojo to the rescue
The Mojo programming language didn't exist when developers struggled with the hastily forced move to Python 3. But it does now, and it will become the de-facto target runtime if Python swallows the no-GIL poison pill.
Mojo's creators knew that it's difficult to teach an old dog new tricks, so they built Mojo to fully support Python code. Just paste Python code into a Mojo file, and [it not only runs](https://www.theserverside.com/blog/Coffee-Talk-Java-News-Stories-and-Opinions/First-Mojo-Program-AI-ML-Hello-World-Number-Guesser-Modular), but it also immediately runs multiple times faster.
Mojo fully supports Python syntax. If not for the flame emoji extension, casual onlookers wouldn't even realize this was Mojo code and not Python.
Furthermore, Mojo works across the entire AI stack, from the CUDA cores on the GPU to the CPU-bound Python scripts that run on the desktop. C and C++ functions that will require updates to support multi-threaded Python code can be written in Mojo as well.
Many of the most popular, open-source machine-learning libraries are already ported to Mojo. Why would anyone who supports a Python project not do the same, if the stewards of the Python language once again force an unnecessary rewrite of all your working code?
I've always said that once the first, full-increment release of Mojo arrives, no greenfield AI or ML projects will be written in Python. All new projects will be developed using a Mojo-first approach, because coding against a CPython runtime won't make sense anymore.
Similarly, if Python removes the GIL, project leaders forced to reckon with rewrites and the long-term prospects of their codebase's health will move to Mojo as well. It will simply be negligent not to do so.
## Slow at runtime and slow to adapt
Many developers in the Python community are frustrated with the language's slow evolution. Discussion of finally removing the GIL after 30 years has understandably excited them, but in their excitement over finally being heard, they fail to see the big picture.
The removal of Python's GIL is a poison pill that will kill the language and send users fleeing to higher ground and to the Mojo language. So long as Mojo presents a fast, efficient and professionally maintained alternative, the Python community should leave the GIL well enough alone.
*Darcy DeClute is a technical trainer and Agile coach who helps organizations apply Scrum-based principles to adopt a modern DevOps stack. She is a certified Professional Scrum Master, Professional Scrum Developer and Professional Scrum Product Owner as well as author of* Scrum Master Certification Guide.
Latest TechTarget resources
- [Application Architecture](https://www.theserverside.com/video/Pythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo)
- [Software Quality](https://www.theserverside.com/video/Pythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo)
- [Cloud Computing](https://www.theserverside.com/video/Pythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo)
- [Security](https://www.theserverside.com/video/Pythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo)
- [AWS](https://www.theserverside.com/video/Pythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo)
[Search App Architecture](https://www.techtarget.com/searchapparchitecture/)
- [AI agents' role in IT infrastructure is expanding](https://www.techtarget.com/searchapparchitecture/tip/AI-Agents-role-in-IT-infrastructure-is-expanding)
AI agents are moving from passive monitoring to active operators, handling incidents, optimizing infrastructure and forcing teams...
- [Pipeline as Code: Managing CI/CD complexity and sprawl](https://www.techtarget.com/searchapparchitecture/tip/Pipeline-as-Code-Managing-CI-CD-complexity-and-sprawl)
Pipeline as Code enhances CI/CD with automation and consistency but adds complexity. Explore benefits, risks and tools to improve...
- [What repos are trending on GitHub?](https://www.techtarget.com/searchapparchitecture/tip/What-repos-are-trending-on-GitHub)
GitHub Stars are a proxy for developer interest. Weekly GitHub star growth highlights fast-rising repos, giving early insight ...
[Search Software Quality](https://www.techtarget.com/searchsoftwarequality/)
- [Harness Artifact Registry strengthens supply chain governance](https://www.techtarget.com/searchsoftwarequality/news/366639489/Harness-Artifact-Registry-strengthens-supply-chain-governance)
Harness makes its artifact registry generally available beyond early preview customers, with a security twist that could ...
- [AWS Kiro 'user error' reflects common AI coding review gap](https://www.techtarget.com/searchsoftwarequality/news/366639129/AWS-Kiro-user-error-reflects-common-AI-coding-review-gap)
Even internal AWS Kiro users haven't always peer-reviewed AI code output, as evidenced by a reported December outage that ...
- [AWS AI IDE, AgentCore throw down gauntlets for Microsoft](https://www.techtarget.com/searchsoftwarequality/news/366635669/AWS-AI-IDE-AgentCore-throw-down-gauntlets-for-Microsoft)
Kiro emerges as a significant alternative to GitHub Copilot agents, while AWS AgentCore updates square off against Agent 365 in ...
[Search Cloud Computing](https://www.techtarget.com/searchcloudcomputing/)
- [AI is changing cloud operations, but not in the way orgs expect](https://www.techtarget.com/searchcloudcomputing/feature/AI-is-changing-cloud-operations-but-not-in-the-way-orgs-expect)
The defining question for organizations today is no longer whether AI can be deployed, but whether it can be operated reliably, ...
- [The hidden costs of technical debt in infrastructure](https://www.techtarget.com/searchcloudcomputing/tip/The-hidden-costs-of-technical-debt-in-infrastructure)
Technical debt is a strategic leadership issue rather than a budgeted maintenance concern. Orgs that actively manage technical ...
- [Is your cloud storage ready for AI workloads?](https://www.techtarget.com/searchcloudcomputing/tip/Is-your-cloud-storage-ready-for-AI-workloads)
Cloud storage design directly impacts AI performance, scalability and cost. Learn how to choose the right storage types, optimize...
[Search Security](https://www.techtarget.com/searchsecurity/)
- [Inside the SOC that secured RSAC 2026 Conference](https://www.techtarget.com/searchsecurity/feature/Inside-the-SOC-that-secured-RSAC-2026-Conference)
Take a behind-the-scenes look at the technology and teamwork that went into creating the security operations center that ...
- [How to roll out an enterprise passkey deployment](https://www.techtarget.com/searchsecurity/tip/How-to-roll-out-an-enterprise-passkey-deployment)
Passkey security sidesteps many of the end-user and cybersecurity issues that plague traditional passwords. Learn how to ...
- [How to improve the SOC analyst experience -- and why it matters](https://www.techtarget.com/searchsecurity/feature/How-to-improve-the-SOC-analyst-experience-and-why-it-matters)
Burned-out security analysts miss threats, take longer to investigate incidents and are more likely to quit. Here's how CISOs can...
[Search AWS](https://www.techtarget.com/searchaws/)
- [Compare Datadog vs. New Relic for IT monitoring in 2024](https://www.techtarget.com/searchaws/tip/Compare-CloudWatch-vs-Datadog-and-New-Relic-for-AWS-monitoring)
Compare Datadog vs. New Relic capabilities including alerts, log management, incident management and more. Learn which tool is ...
- [AWS Control Tower aims to simplify multi-account management](https://www.techtarget.com/searchaws/tip/AWS-Control-Tower-aims-to-simplify-multi-account-management)
Many organizations struggle to manage their vast collection of AWS accounts, but Control Tower can help. The service automates ...
- [Break down the Amazon EKS pricing model](https://www.techtarget.com/searchaws/tip/Compare-EKS-pricing-to-other-managed-Kubernetes-services)
There are several important variables within the Amazon EKS pricing model. Dig into the numbers to ensure you deploy the service ...
- Follow:
- [About Us](https://www.informatechtarget.com/editorial/)
- [Editorial Ethics Policy](https://www.techtarget.com/techtarget-editorial-ethics-policy)
- [Meet The Editors](https://www.techtarget.com/editorial-contacts)
- [Contact Us](https://www.informatechtarget.com/contact-us/)
- [Advertisers](https://www.informatechtarget.com/for-advertisers/)
- [Partner with Us](https://www.informatechtarget.com/partner-with-us/)
- [Media Kit](https://www.informatechtarget.com/wp-content/uploads/2023/09/TechTarget-Media-Kit-Handout-with-product-descriptions.pdf)
- [Corporate Site](https://www.informatechtarget.com/)
- [Contributors](https://www.theserverside.com/contributors)
- [Reprints](https://licensing.ygsgroup.com/ygspublishersolutions/)
- [Answers](https://www.theserverside.com/answers)
- [Definitions](https://www.theserverside.com/definitions)
- [E-Products](https://www.theserverside.com/eproducts)
- [Events](https://www.brighttalk.com/summits)
- [Features](https://www.theserverside.com/features)
- [Guides](https://www.theserverside.com/guides)
- [Opinions](https://www.theserverside.com/opinions)
- [Photo Stories](https://www.theserverside.com/photostories)
- [Quizzes](https://www.theserverside.com/quizzes)
- [Tips](https://www.theserverside.com/tips)
- [Tutorials](https://www.theserverside.com/tutorials)
- [Videos](https://www.theserverside.com/videos)
[Š2026 TechTarget](https://www.informatechtarget.com/terms-of-use), Inc. d/b/a Informa TechTarget. All Rights Reserved.
[Privacy Policy](https://www.informatechtarget.com/privacy-policy/)
[Cookie Preferences](https://www.theserverside.com/video/Pythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo)
[Cookie Preferences](https://www.theserverside.com/video/Pythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo)
[Do Not Sell or Share My Personal Information](https://techtarget.zendesk.com/hc/en-us/requests/new?ticket_form_id=360004852434)
Close
 |
| Readable Markdown | A major criticism of the Python programming language is that it can't thread across cores. The reason is because of the CPython's Global Interpreter Lock (GIL).
The inability to take advantage of more than one core in a multi-CPU system seriously limits [Python performance](https://www.theserverside.com/tip/Tips-to-improve-Python-performance). It's one of the reasons why Python embarrassingly lags its peers when it comes to speed and efficiency.
Developers have begged Python's stewards for almost 30 years to fix the GIL. With the steering committee's recent acceptance of [PEP 703](https://peps.python.org/pep-0703/), it looks like Python's GIL removal might happen.
It's [a bad idea](https://www.techtarget.com/searchitoperations/video/No-GIL-Python-is-a-mistake).
## Python's GIL is a poison pill
Removing Python's GIL is a poison pill. It will inevitably [kill off Python as we know it](https://www.theserverside.com/blog/Coffee-Talk-Java-News-Stories-and-Opinions/Is-Pythons-GIL-the-software-worlds-biggest-blunder).
Every piece of Python code that runs on the CPython interpreter assumes safe, single-threaded execution. Removing Python's GIL changes that assumption. Every library or Python program ever written that might be impacted by multithreaded data access will have to be retested and potentially rewritten.
Amid the transition from GIL to no-GIL Python runtimes, existing Python projects will likely have to maintain two codebases: one for GIL-based runtimes and another for where Python's GIL is removed. That promises to be a nightmare for open-source projects for which maintaining a single distribution is difficult enough.
Furthermore, the removal of the GIL will have negative impacts that extend beyond the boundaries of Python's interpreter.
Due to its many shortcomings, Python is seldom used to implement actual machine learning routines or run neural networks. Python's main use case is to simply format and massage input data as well as feed it to functions and routines that are implemented in languages such as C++ or Java that are more capable of threading across cores.
However, those functions expect to be invoked in a safe and single-threaded manner. Many of those programs that Python interacts with will require extra tests, updates and dual maintenance as well.
## Python 2 to 3 all over again
All of this should feel familiar to maintainers of Python libraries. They were forced to do something similar with the fumbled switch from Python 2 to Python 3, when the stewards of the Python language turned their backs on the community and abandoned backwards compatibility.
During the Python 2 to 3 debacle, developers had little choice but to submit to the dictates of the language stewards and migrate. They received little lead time about the backwards incompatibility issues, but because no viable alternatives existed at the time, organizations that were heavily committed to Python were forced into expensive and disruptive Python version migrations.
Python fans likely have little appetite to go through that again for the GIL-to-no-GIL transition.
Fortunately, things are different now. The GIL's removal is slated to take five years, and my guess is it will take longer. Developers and architects will have time to plan around this change, and if they perform due diligence, their plans should involve completely porting away from Python.
## Mojo to the rescue
The Mojo programming language didn't exist when developers struggled with the hastily forced move to Python 3. But it does now, and it will become the de-facto target runtime if Python swallows the no-GIL poison pill.
Mojo's creators knew that it's difficult to teach an old dog new tricks, so they built Mojo to fully support Python code. Just paste Python code into a Mojo file, and [it not only runs](https://www.theserverside.com/blog/Coffee-Talk-Java-News-Stories-and-Opinions/First-Mojo-Program-AI-ML-Hello-World-Number-Guesser-Modular), but it also immediately runs multiple times faster.
Mojo fully supports Python syntax. If not for the flame emoji extension, casual onlookers wouldn't even realize this was Mojo code and not Python.
Furthermore, Mojo works across the entire AI stack, from the CUDA cores on the GPU to the CPU-bound Python scripts that run on the desktop. C and C++ functions that will require updates to support multi-threaded Python code can be written in Mojo as well.
Many of the most popular, open-source machine-learning libraries are already ported to Mojo. Why would anyone who supports a Python project not do the same, if the stewards of the Python language once again force an unnecessary rewrite of all your working code?
I've always said that once the first, full-increment release of Mojo arrives, no greenfield AI or ML projects will be written in Python. All new projects will be developed using a Mojo-first approach, because coding against a CPython runtime won't make sense anymore.
Similarly, if Python removes the GIL, project leaders forced to reckon with rewrites and the long-term prospects of their codebase's health will move to Mojo as well. It will simply be negligent not to do so.
## Slow at runtime and slow to adapt
Many developers in the Python community are frustrated with the language's slow evolution. Discussion of finally removing the GIL after 30 years has understandably excited them, but in their excitement over finally being heard, they fail to see the big picture.
The removal of Python's GIL is a poison pill that will kill the language and send users fleeing to higher ground and to the Mojo language. So long as Mojo presents a fast, efficient and professionally maintained alternative, the Python community should leave the GIL well enough alone.
*Darcy DeClute is a technical trainer and Agile coach who helps organizations apply Scrum-based principles to adopt a modern DevOps stack. She is a certified Professional Scrum Master, Professional Scrum Developer and Professional Scrum Product Owner as well as author of* Scrum Master Certification Guide. |
| Shard | 23 (laksa) |
| Root Hash | 7434987543936799023 |
| Unparsed URL | com,theserverside!www,/video/Pythons-GIL-removal-is-a-poison-pill-and-benefits-Mojo s443 |