Asadbek Kurbonov

Why Nothing Has Replaced CPython: A 2026 Tour of Python Runtimes

Wed, 08 Jul 2026 00:10:00 +0200

Python is the most popular programming language in the world, and one of the slowest in wide production use. That combination should be catnip for anyone building a faster runtime — and for fifteen years, people have. There is a version of Python with a tracing JIT that is genuinely several times faster. There are compilers that turn it into native code. There are ports to the JVM and the .NET CLR. Big companies have funded forks. And after all of it, the interpreter almost everyone actually runs is still plain CPython.

pon: A Compiled Python Built in a Week, Measured Against Its Claims

Tue, 07 Jul 2026 20:00:00 +0200

I came across pon, a project that sets out to be “the bun/v8 of Python”: a from-scratch native compiler and runtime for Python 3.14, written in Rust, with no interpreter and no bytecode. The pitch is ambitious enough to be worth taking seriously — and the repository is unusual in another way. It was built in about a week: 475 commits from a single author between June 30 and July 7, with an AGENTS.md file and conventional-commit discipline that make it fairly clear the bulk was produced with AI coding agents.

When You Can't Find the Bug: Architecting Around Production Issues

Mon, 24 Nov 2025 22:00:00 +0100

This is Part 2 of a series. Read Part 1: Pandas vs Polars in Production - Performance Comparison for the background on the Polars migration.

After migrating from Pandas to Polars, CPU performance improved dramatically—but a memory problem persisted. Despite extensive debugging, I couldn’t identify the root cause. So I made a pragmatic decision: architect around it.

This is the story of splitting a monolithic Python application into a Go orchestration service with Python workers, not because I fully understood the problem, but because I needed production to be stable.

Pandas vs Polars in Production: Performance Comparison

Sun, 23 Nov 2025 23:02:39 +0100

When performance bottlenecks started affecting my production data pipeline, I decided to test whether Polars could deliver on its performance promises. This is what I learned from migrating a real production workload from Pandas to Polars.

The Workload

The application was a data aggregation service running as a Kubernetes pod with the following constraints:

Resources: 2 CPUs, 3 GB RAM
Execution frequency: Every 2-2.5 minutes
Data volume: 5,000-7,000 rows × 100-150 columns per run
Operations: Multiple database calls, API requests, DataFrame merges, arithmetic operations (additions, multiplications), and group-by aggregations
Web server: FastAPI with Uvicorn handling production traffic

All operations were properly vectorized — no row-by-row iteration. The pipeline combined data from various sources into a single DataFrame, transformed it, and output the results.

Converting Wide Excel Tables to Single-Page PDFs with LibreOffice

Fri, 21 Nov 2025 23:42:51 +0100

The Problem

While working on a freelance project, I needed to generate PDF reports from Excel files. The challenge? The Excel files were wide and long. Here we see a sample Excel file around 15 columns containing employee data like ID, name, email, department, job title, hire date, salary, and more.

I used LibreOffice’s CLI utility convert-to in headless mode to convert the files. The conversion worked, but the result was unusable:

Setting Up a Telegram Bot on Google Apps Script

Tue, 22 Jul 2025 23:24:14 +0500

This is the technical companion to Automating Business Reports with Google Apps Script and Telegram, which covers the project this code came from. Here I’ll walk through running a Telegram bot on Apps Script: handling updates, routing messages, and managing the webhook.

Receiving updates

Telegram delivers updates to your webhook as HTTP POST requests. In Apps Script, a POST to a deployed web app invokes the doPost(e) function, so that’s where the bot starts:

Automating Business Reports with Google Apps Script and Telegram

Tue, 22 Jul 2025 22:39:19 +0500

Google Apps Script is easy to dismiss as a toy. Over two freelance projects it turned out to be a genuinely capable serverless platform for automation work built around Google Sheets and Telegram. This post covers the second of those projects — a reporting system for a US-market logistics business — and how I got there.

First encounter

I came across Apps Script on an earlier freelance job. A consulting firm needed a Telegram bot that generated templated Word contracts. They had started the work themselves in Apps Script but hadn’t finished it, so I picked it up and rebuilt the bot in Python with aiogram, rendering .docx files from templates using docxtpl and passing files around as base64. Apps Script was only incidental to that project, but it was my first look at the platform.