--- title: Projects I Wouldn't Use Python For in 2026 | daily.dev description: A developer who built their career on Python shares a talk given at a Christchurch Python NZ meetup about when Python is no longer the best tool for the job.... canonical: https://daily.dev/posts/projects-i-wouldn-t-use-python-for-in-2026-0arzr6s2a twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Projects I Wouldn't Use Python For in 2026 | daily.dev og:description: A developer who built their career on Python shares a talk given at a Christchurch Python NZ meetup about when Python is no longer the best tool for the job.... og:url: https://daily.dev/posts/projects-i-wouldn-t-use-python-for-in-2026-0arzr6s2a og:image: https://api.daily.dev/og/posts/0ARzr6S2A.png og:image:alt: Projects I Wouldn't Use Python For in 2026 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Projects I Wouldn't Use Python For in 2026 **[Lobsters](https://daily.dev/sources/lobsters)** · 1 min read · 0 upvotes · 0 comments ## Summary A developer who built their career on Python shares a talk given at a Christchurch Python NZ meetup about when Python is no longer the best tool for the job. The presentation covers their journey from using Python for everything to recognizing its limitations, what alternatives they now reach for, and where Python still excels. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community take How the wider developer community reacted, aggregated from 1 discussion and 10 comments across lobsters (as of 2026-09-14). **TL;DR:** The Lobsters community is largely sympathetic to the post's premise that static typing has become more attractive, but several experienced Python developers push back on the specific arguments as oversimplified or unconvincing, and one commenter disputes a factual claim about Moore's Law. **Sentiment:** 25% positive · 50% mixed · 25% skeptical **The case for** - Commenters agree that modern type systems are genuinely better than the C++98/Java-era ones that made dynamic languages appealing in the first place. - The post is seen as valuable for helping newer developers know that better-typed alternatives exist. - Python being 'the second-best language for everything' is highlighted as a genuine strength worth celebrating. **The pushback** - The refactoring-bug example used to argue for static types is considered facile by experienced Python developers, since IDEs and linters already handle it. - The claim that 'Moore's Law is over' is disputed as misleading — transistor cost and GPU price-performance are still dropping exponentially. - The arguments as presented in the slides are seen as not fully convincing, even by developers broadly sympathetic to the conclusion. - The framing is criticized as a binary choice, ignoring the 'alternate hard and soft layers' approach. **By community** - lobsters (mixed): Experienced Python developers broadly agree static typing has improved but find the specific arguments in the slides unconvincing or oversimplified, with one factual dispute over Moore's Law. **Hottest debate:** Whether the concrete examples given for why static types are better (e.g., the refactoring bug) actually hold up against modern Python tooling like PyCharm and linters. **Open questions** - Is the 'hard layer / soft layer' hybrid approach still a viable alternative that the post ignores? - Does the cost-of-transistors metric mean performance improvements are still on an exponential curve, undermining the 'Moore's Law is over' framing? **Highlights** > Agreed but with a “hang on a tick”. Not sure if it’s the nature of slides eliding the details, but while the author has almost ten years on me in terms of Python experience (which is nice to run into nowadays), the examples about why “real” types work better seem facile. The refactoring bug is something I can’t imagine I’ve hit since the early 2010s; PyCharm or similar will do the refactor for you and if it somehow screws up, linters should be catching an undefined function. As someone whose career has been like 85% Python, I think posts like this are important because newer codes should know there are other options and that they work better, but I am not sold on the arguments as presented in the slides. As always, trend lines drawn through a single data point (my own perspective here included) should be read with a cocked eye. Edited to add: yes my first paragraph does not cover “but an asshole could have done X with magic methods or Python plumbing”. I decided long ago not to judge a language on what a bog-standard asshole could do with it. Having typed it out, maybe that’s Stockholm Syndrome from working in Python though. > — [tclancy on lobsters · 2 points, 1 comments](https://lobste.rs/s/ib4tko/projects_i_wouldn_t_use_python_for_2026#c_li0s8s) > Arguments against dynamic typing very often come down to "who are you going to believe, me or your lying eyes?" Well, my allegedly lying eyes tell me that plenty of large successful projects exist in dynamically-typed languages (and plenty of large projects in statically-typed languages fail), that IDEs and editors can do automated refactorings of dynamically-typed languages and have been able to for years, that my codebase isn't a tower of thousands of defensive `assert not isinstance` statements, etc. So I'm going to stick with the evidence of my eyes. > — [ubernostrum on lobsters · 3 points, 1 comments](https://lobste.rs/s/ib4tko/projects_i_wouldn_t_use_python_for_2026#c_8wiwz0) > I don't have a big opinion about the rest of the talk but [slide 11](https://menno.io/presentations/not-python-2026/index.html#/11) triggers a pet peeve of mine: > Moore's Law is over This might be technically true but Moore's law like laws are still very much in effect. Specifically, the [cost of transistor is still dropping exponentially](https://web.archive.org/web/20250330101143/https://ourworldindata.org/grapher/gpu-price-performance?yScale=log) and that is the statistic we care more about. The slide almost says this but, in my opinion, wildly misses the point: > We now only get performance improvements through concurrency, specialisation & better compilers Performance is achieved through *parallelism*. Specialization might help. Compilers [double computing power roughly 18 years](https://zeux.io/2022/01/08/on-proebstings-law/). > — [abetusk on lobsters · 2 points](https://lobste.rs/s/ib4tko/projects_i_wouldn_t_use_python_for_2026#c_olae02) **Source threads** - [lobsters](https://lobste.rs/s/ib4tko/projects_i_wouldn_t_use_python_for_2026) · 8 points · 10 comments ## Similar posts on daily.dev - [Python Development vs PHP in 2026: Which One Should You Choose?](https://daily.dev/posts/python-development-vs-php-in-2026-which-one-should-you-choose--8z7sgv9bz) · Medium · 1 upvotes · 0 comments --- Tags: [#python](https://daily.dev/tags/python), [#architecture](https://daily.dev/tags/architecture) [View this post on daily.dev](https://daily.dev/posts/projects-i-wouldn-t-use-python-for-in-2026-0arzr6s2a) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Projects I Wouldn't Use Python For in 2026","url":"https://daily.dev/posts/projects-i-wouldn-t-use-python-for-in-2026-0arzr6s2a","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/projects-i-wouldn-t-use-python-for-in-2026-0arzr6s2a"},"datePublished":"2026-08-04T09:03:26.172Z","dateModified":"2026-09-14T08:05:01.733Z","description":"A developer who built their career on Python shares a talk given at a Christchurch Python NZ meetup about when Python is no longer the best tool for the job....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d79350c082b6b3a8cd5e9166da4bf56b?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d79350c082b6b3a8cd5e9166da4bf56b?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Lobsters","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Lobsters","logo":"https://media.daily.dev/image/upload/s--tl8v_Fku--/f_auto,t_logo/v1698841318/logos/lobste.jpg","url":"https://daily.dev/sources/lobsters"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/projects-i-wouldn-t-use-python-for-in-2026-0arzr6s2a","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"python,architecture","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Lobsters","item":"https://daily.dev/sources/lobsters"},{"@type":"ListItem","position":3,"name":"Projects I Wouldn't Use Python For in 2026"}]} ```