Reading Grounds
Programming, Web Development, Articles
Read practical articles about Python, JavaScript, React, TypeScript, Linux Shell, Rust, Zig, and modern software tools.
Python JIT-Compiling
Python JIT-Compiling explains how CPython traditionally executes bytecode and how experimental JIT compilation may improve some Python workloads over time. The article compares Python’s JIT efforts with Java, JavaScript, PyPy, and other runtimes while keeping expectations realistic about performance gains.
Python
Read article →Python Packaging Wars
A beginner-friendly guide to the modern Python packaging debate.
Python
Read article →pip vs uv: Is Python Finally Getting a Package Manager People Can Agree On?
For small scripts, pip may be enough. For modern projects, uv is hard to ignore.
Python
Read article →Python Data Types?
This article explains how Python data types have evolved from a beginner topic into a larger engineering discussion about type hints, validation, tooling, testing, and scale.
Python
Read article →State of the Bun
State of the Bun explains Bun as a fast, all-in-one JavaScript toolkit that combines a runtime, package manager, bundler, and test runner. The article covers Bun’s history, motivation, adoption, strengths, weaknesses, and controversies while keeping the focus on what Bun means for the future of JavaScript tooling.
JavaScript
Read article →Where Is Deno Today?
Where is Deno today? examines Deno as a secure, TypeScript-first JavaScript runtime that has become more practical through stronger Node/npm compatibility and built-in tooling. The article also explains Deno Deploy, its free-tier limits, and how Deno’s platform strategy compares with Node.js and Bun.
TypeScript
Read article →JavaScript History Recap 2026
Recap of JavaScript History traces how JavaScript grew from a fast-built Netscape browser scripting language into the central language of modern web development. The article covers its creator, early motivations, language influences, ecosystem growth, production uses, and future direction toward TypeScript, faster tooling, full-stack frameworks, and edge deployment.
JavaScript
Read article →Python History Recap 2026
Recap the History of Python traces how Guido van Rossum’s readable, practical successor to ABC became a major language for automation, web development, data science, AI, education, and scientific computing. The article covers Python’s origins, ecosystem, production uses, key turning points, and future direction toward faster CPython, stronger typing, better packaging, and improved multi-core execution.
Python
Read article →React History Recap 2026
Explore how React.js evolved from an internal Facebook prototype into a dominant library for web and native user interfaces. This 2026 recap covers React’s creators, architecture, ecosystem, production adoption, relationship with Next.js and future direction.
React
Read article →C++ History Recap 2026 - Part 1 of 3 Parts
Part 1 explores the creation of C++, the story of Bjarne Stroustrup, and the ideas that shaped the language’s first versions. It explains how C++ built on C while developing its own identity as a language for efficient abstraction and large-scale systems programming.
CPP
Read article →C++ History Recap 2026 - Part 2 of 3 Parts
Part 2 explores the creation of C++, the story of Bjarne Stroustrup, and the ideas that shaped the language’s first versions. It explains how C++ built on C while developing its own identity as a language for efficient abstraction and large-scale systems programming.
CPP
Read article →C++ History Recap 2026 - Part 3 of 3 Parts
Part 3 explores the creation of C++, the story of Bjarne Stroustrup, and the ideas that shaped the language’s first versions. It explains how C++ built on C while developing its own identity as a language for efficient abstraction and large-scale systems programming.
CPP
Read article →Next.js History Recap 2026 - Part 1 of 3 Parts
Next.js History Recap 2026 Part 1 of 3 explores the creators, origins, and motivations behind Next.js, including its early development at ZEIT and its relationship with React. It explains how Next.js turned the complex process of building server-rendered React applications into a more integrated and practical development workflow.
React
Read article →Next.js History Recap 2026 - Part 2 of 3 Parts
Next.js History Recap 2026 Part 2 of 3 explains how Next.js builds a complete application framework around React’s existing server-rendering capabilities. It also follows the framework’s evolution from its original release through the App Router, Turbopack, explicit caching, and Next.js 16.
React
Read article →Next.js History Recap 2026 - Part 3 of 3 Parts
Next.js History Recap 2026 Part 3 of 3 explores where Next.js is used, the ecosystem and production tools surrounding it, and its position as a leading full-stack React framework. It also examines adoption, criticism, notable deployments, and the technical trends shaping Next.js in 2026.
React
Read article →Rust History Recap 2026 - Part 1 of 3 Parts
*Rust History Recap 2026 - Part 2 of 3* explores Rust’s editions, stability model, expressive type system, error handling, traits, macros, async programming, and zero-cost abstractions. It also examines Cargo, crates.io, rustup, Clippy, rustfmt, rust-analyzer, rustdoc, Miri, and the libraries and frameworks that define modern Rust development.
Rust
Read article →Rust History Recap 2026 - Part 2 of 3 Parts
Next.js History Recap 2026 Part 3 of 3 explores where Next.js is used, the ecosystem and production tools surrounding it, and its position as a leading full-stack React framework. It also examines adoption, criticism, notable deployments, and the technical trends shaping Next.js in 2026.
Rust
Read article →Rust History Recap 2026 - Part 3 of 3 Parts
*Rust History Recap 2026 - Part 3 of 3 Parts* explores Rust’s production applications, notable software, commercial adoption, and the practical strengths and challenges that define the language in 2026. It also examines Rust’s direction through improved ergonomics, faster compilation, safer low-level abstractions, stronger async and trait support, embedded growth, Linux integration, and industrial adoption.
Rust
Read article →C History Recap 2026 - Part 1 of 3 Parts
*C History Recap 2026 - Part 1 of 3 Parts* explores the creation of C at Bell Labs, Dennis Ritchie’s role, and the influence of BCPL, B, Unix, and the PDP-11. It explains how C developed its own identity as a compact language that combines native efficiency, portability, procedural structure, and direct control over memory and hardware.
C
Read article →C History Recap 2026 - Part 2 of 3 Parts
*C History Recap 2026 - Part 2 of 3 Parts* follows C’s standardization and technical evolution from the K&R era through C23. It also examines the compilers, standard libraries, build systems, analyzers, debuggers, testing frameworks, and embedded toolchains used in contemporary C development.
C
Read article →C History Recap 2026 - Part 3 of 3 Parts
*C History Recap 2026 - Part 3 of 3 Parts* explores C’s major production uses, enduring strengths, notable software, and persistent safety and maintenance challenges. It also examines current C2y work and the language’s likely future as a compact native foundation within increasingly multilingual systems.
C
Read article →Zig History Recap 2026 - Part 1 of 3 Parts
*C History Recap 2026 - Part 3 of 3 Parts* explores C’s major production uses, enduring strengths, notable software, and persistent safety and maintenance challenges. It also examines current C2y work and the language’s likely future as a compact native foundation within increasingly multilingual systems.
Zig
Read article →Zig History Recap 2026 - Part 2 of 3 Parts
*C History Recap 2026 - Part 3 of 3 Parts* explores C’s major production uses, enduring strengths, notable software, and persistent safety and maintenance challenges. It also examines current C2y work and the language’s likely future as a compact native foundation within increasingly multilingual systems.
Zig
Read article →Zig History Recap 2026 - Part 3 of 3 Parts
*C History Recap 2026 - Part 3 of 3 Parts* explores C’s major production uses, enduring strengths, notable software, and persistent safety and maintenance challenges. It also examines current C2y work and the language’s likely future as a compact native foundation within increasingly multilingual systems.
Zig
Read article →Python JIT-Compiling
Python JIT-Compiling explains how CPython traditionally executes bytecode and how experimental JIT compilation may improve some Python workloads over time. The article compares Python’s JIT efforts with Java, JavaScript, PyPy, and other runtimes while keeping expectations realistic about performance gains.
Python
Read article →Python Packaging Wars
A beginner-friendly guide to the modern Python packaging debate.
Python
Read article →pip vs uv: Is Python Finally Getting a Package Manager People Can Agree On?
For small scripts, pip may be enough. For modern projects, uv is hard to ignore.
Python
Read article →Python Data Types?
This article explains how Python data types have evolved from a beginner topic into a larger engineering discussion about type hints, validation, tooling, testing, and scale.
Python
Read article →State of the Bun
State of the Bun explains Bun as a fast, all-in-one JavaScript toolkit that combines a runtime, package manager, bundler, and test runner. The article covers Bun’s history, motivation, adoption, strengths, weaknesses, and controversies while keeping the focus on what Bun means for the future of JavaScript tooling.
JavaScript
Read article →Where Is Deno Today?
Where is Deno today? examines Deno as a secure, TypeScript-first JavaScript runtime that has become more practical through stronger Node/npm compatibility and built-in tooling. The article also explains Deno Deploy, its free-tier limits, and how Deno’s platform strategy compares with Node.js and Bun.
TypeScript
Read article →JavaScript History Recap 2026
Recap of JavaScript History traces how JavaScript grew from a fast-built Netscape browser scripting language into the central language of modern web development. The article covers its creator, early motivations, language influences, ecosystem growth, production uses, and future direction toward TypeScript, faster tooling, full-stack frameworks, and edge deployment.
JavaScript
Read article →Python History Recap 2026
Recap the History of Python traces how Guido van Rossum’s readable, practical successor to ABC became a major language for automation, web development, data science, AI, education, and scientific computing. The article covers Python’s origins, ecosystem, production uses, key turning points, and future direction toward faster CPython, stronger typing, better packaging, and improved multi-core execution.
Python
Read article →React History Recap 2026
Explore how React.js evolved from an internal Facebook prototype into a dominant library for web and native user interfaces. This 2026 recap covers React’s creators, architecture, ecosystem, production adoption, relationship with Next.js and future direction.
React
Read article →C++ History Recap 2026 - Part 1 of 3 Parts
Part 1 explores the creation of C++, the story of Bjarne Stroustrup, and the ideas that shaped the language’s first versions. It explains how C++ built on C while developing its own identity as a language for efficient abstraction and large-scale systems programming.
CPP
Read article →C++ History Recap 2026 - Part 2 of 3 Parts
Part 2 explores the creation of C++, the story of Bjarne Stroustrup, and the ideas that shaped the language’s first versions. It explains how C++ built on C while developing its own identity as a language for efficient abstraction and large-scale systems programming.
CPP
Read article →C++ History Recap 2026 - Part 3 of 3 Parts
Part 3 explores the creation of C++, the story of Bjarne Stroustrup, and the ideas that shaped the language’s first versions. It explains how C++ built on C while developing its own identity as a language for efficient abstraction and large-scale systems programming.
CPP
Read article →Next.js History Recap 2026 - Part 1 of 3 Parts
Next.js History Recap 2026 Part 1 of 3 explores the creators, origins, and motivations behind Next.js, including its early development at ZEIT and its relationship with React. It explains how Next.js turned the complex process of building server-rendered React applications into a more integrated and practical development workflow.
React
Read article →Next.js History Recap 2026 - Part 2 of 3 Parts
Next.js History Recap 2026 Part 2 of 3 explains how Next.js builds a complete application framework around React’s existing server-rendering capabilities. It also follows the framework’s evolution from its original release through the App Router, Turbopack, explicit caching, and Next.js 16.
React
Read article →Next.js History Recap 2026 - Part 3 of 3 Parts
Next.js History Recap 2026 Part 3 of 3 explores where Next.js is used, the ecosystem and production tools surrounding it, and its position as a leading full-stack React framework. It also examines adoption, criticism, notable deployments, and the technical trends shaping Next.js in 2026.
React
Read article →Rust History Recap 2026 - Part 1 of 3 Parts
*Rust History Recap 2026 - Part 2 of 3* explores Rust’s editions, stability model, expressive type system, error handling, traits, macros, async programming, and zero-cost abstractions. It also examines Cargo, crates.io, rustup, Clippy, rustfmt, rust-analyzer, rustdoc, Miri, and the libraries and frameworks that define modern Rust development.
Rust
Read article →Rust History Recap 2026 - Part 2 of 3 Parts
Next.js History Recap 2026 Part 3 of 3 explores where Next.js is used, the ecosystem and production tools surrounding it, and its position as a leading full-stack React framework. It also examines adoption, criticism, notable deployments, and the technical trends shaping Next.js in 2026.
Rust
Read article →Rust History Recap 2026 - Part 3 of 3 Parts
*Rust History Recap 2026 - Part 3 of 3 Parts* explores Rust’s production applications, notable software, commercial adoption, and the practical strengths and challenges that define the language in 2026. It also examines Rust’s direction through improved ergonomics, faster compilation, safer low-level abstractions, stronger async and trait support, embedded growth, Linux integration, and industrial adoption.
Rust
Read article →C History Recap 2026 - Part 1 of 3 Parts
*C History Recap 2026 - Part 1 of 3 Parts* explores the creation of C at Bell Labs, Dennis Ritchie’s role, and the influence of BCPL, B, Unix, and the PDP-11. It explains how C developed its own identity as a compact language that combines native efficiency, portability, procedural structure, and direct control over memory and hardware.
C
Read article →C History Recap 2026 - Part 2 of 3 Parts
*C History Recap 2026 - Part 2 of 3 Parts* follows C’s standardization and technical evolution from the K&R era through C23. It also examines the compilers, standard libraries, build systems, analyzers, debuggers, testing frameworks, and embedded toolchains used in contemporary C development.
C
Read article →C History Recap 2026 - Part 3 of 3 Parts
*C History Recap 2026 - Part 3 of 3 Parts* explores C’s major production uses, enduring strengths, notable software, and persistent safety and maintenance challenges. It also examines current C2y work and the language’s likely future as a compact native foundation within increasingly multilingual systems.
C
Read article →Zig History Recap 2026 - Part 1 of 3 Parts
*C History Recap 2026 - Part 3 of 3 Parts* explores C’s major production uses, enduring strengths, notable software, and persistent safety and maintenance challenges. It also examines current C2y work and the language’s likely future as a compact native foundation within increasingly multilingual systems.
Zig
Read article →Zig History Recap 2026 - Part 2 of 3 Parts
*C History Recap 2026 - Part 3 of 3 Parts* explores C’s major production uses, enduring strengths, notable software, and persistent safety and maintenance challenges. It also examines current C2y work and the language’s likely future as a compact native foundation within increasingly multilingual systems.
Zig
Read article →Zig History Recap 2026 - Part 3 of 3 Parts
*C History Recap 2026 - Part 3 of 3 Parts* explores C’s major production uses, enduring strengths, notable software, and persistent safety and maintenance challenges. It also examines current C2y work and the language’s likely future as a compact native foundation within increasingly multilingual systems.
Zig
Read article →Python JIT-Compiling
Python JIT-Compiling explains how CPython traditionally executes bytecode and how experimental JIT compilation may improve some Python workloads over time. The article compares Python’s JIT efforts with Java, JavaScript, PyPy, and other runtimes while keeping expectations realistic about performance gains.
Python
Read article →Python Packaging Wars
A beginner-friendly guide to the modern Python packaging debate.
Python
Read article →pip vs uv: Is Python Finally Getting a Package Manager People Can Agree On?
For small scripts, pip may be enough. For modern projects, uv is hard to ignore.
Python
Read article →Python Data Types?
This article explains how Python data types have evolved from a beginner topic into a larger engineering discussion about type hints, validation, tooling, testing, and scale.
Python
Read article →State of the Bun
State of the Bun explains Bun as a fast, all-in-one JavaScript toolkit that combines a runtime, package manager, bundler, and test runner. The article covers Bun’s history, motivation, adoption, strengths, weaknesses, and controversies while keeping the focus on what Bun means for the future of JavaScript tooling.
JavaScript
Read article →Where Is Deno Today?
Where is Deno today? examines Deno as a secure, TypeScript-first JavaScript runtime that has become more practical through stronger Node/npm compatibility and built-in tooling. The article also explains Deno Deploy, its free-tier limits, and how Deno’s platform strategy compares with Node.js and Bun.
TypeScript
Read article →JavaScript History Recap 2026
Recap of JavaScript History traces how JavaScript grew from a fast-built Netscape browser scripting language into the central language of modern web development. The article covers its creator, early motivations, language influences, ecosystem growth, production uses, and future direction toward TypeScript, faster tooling, full-stack frameworks, and edge deployment.
JavaScript
Read article →Python History Recap 2026
Recap the History of Python traces how Guido van Rossum’s readable, practical successor to ABC became a major language for automation, web development, data science, AI, education, and scientific computing. The article covers Python’s origins, ecosystem, production uses, key turning points, and future direction toward faster CPython, stronger typing, better packaging, and improved multi-core execution.
Python
Read article →React History Recap 2026
Explore how React.js evolved from an internal Facebook prototype into a dominant library for web and native user interfaces. This 2026 recap covers React’s creators, architecture, ecosystem, production adoption, relationship with Next.js and future direction.
React
Read article →C++ History Recap 2026 - Part 1 of 3 Parts
Part 1 explores the creation of C++, the story of Bjarne Stroustrup, and the ideas that shaped the language’s first versions. It explains how C++ built on C while developing its own identity as a language for efficient abstraction and large-scale systems programming.
CPP
Read article →C++ History Recap 2026 - Part 2 of 3 Parts
Part 2 explores the creation of C++, the story of Bjarne Stroustrup, and the ideas that shaped the language’s first versions. It explains how C++ built on C while developing its own identity as a language for efficient abstraction and large-scale systems programming.
CPP
Read article →C++ History Recap 2026 - Part 3 of 3 Parts
Part 3 explores the creation of C++, the story of Bjarne Stroustrup, and the ideas that shaped the language’s first versions. It explains how C++ built on C while developing its own identity as a language for efficient abstraction and large-scale systems programming.
CPP
Read article →Next.js History Recap 2026 - Part 1 of 3 Parts
Next.js History Recap 2026 Part 1 of 3 explores the creators, origins, and motivations behind Next.js, including its early development at ZEIT and its relationship with React. It explains how Next.js turned the complex process of building server-rendered React applications into a more integrated and practical development workflow.
React
Read article →Next.js History Recap 2026 - Part 2 of 3 Parts
Next.js History Recap 2026 Part 2 of 3 explains how Next.js builds a complete application framework around React’s existing server-rendering capabilities. It also follows the framework’s evolution from its original release through the App Router, Turbopack, explicit caching, and Next.js 16.
React
Read article →Next.js History Recap 2026 - Part 3 of 3 Parts
Next.js History Recap 2026 Part 3 of 3 explores where Next.js is used, the ecosystem and production tools surrounding it, and its position as a leading full-stack React framework. It also examines adoption, criticism, notable deployments, and the technical trends shaping Next.js in 2026.
React
Read article →Rust History Recap 2026 - Part 1 of 3 Parts
*Rust History Recap 2026 - Part 2 of 3* explores Rust’s editions, stability model, expressive type system, error handling, traits, macros, async programming, and zero-cost abstractions. It also examines Cargo, crates.io, rustup, Clippy, rustfmt, rust-analyzer, rustdoc, Miri, and the libraries and frameworks that define modern Rust development.
Rust
Read article →Rust History Recap 2026 - Part 2 of 3 Parts
Next.js History Recap 2026 Part 3 of 3 explores where Next.js is used, the ecosystem and production tools surrounding it, and its position as a leading full-stack React framework. It also examines adoption, criticism, notable deployments, and the technical trends shaping Next.js in 2026.
Rust
Read article →Rust History Recap 2026 - Part 3 of 3 Parts
*Rust History Recap 2026 - Part 3 of 3 Parts* explores Rust’s production applications, notable software, commercial adoption, and the practical strengths and challenges that define the language in 2026. It also examines Rust’s direction through improved ergonomics, faster compilation, safer low-level abstractions, stronger async and trait support, embedded growth, Linux integration, and industrial adoption.
Rust
Read article →C History Recap 2026 - Part 1 of 3 Parts
*C History Recap 2026 - Part 1 of 3 Parts* explores the creation of C at Bell Labs, Dennis Ritchie’s role, and the influence of BCPL, B, Unix, and the PDP-11. It explains how C developed its own identity as a compact language that combines native efficiency, portability, procedural structure, and direct control over memory and hardware.
C
Read article →C History Recap 2026 - Part 2 of 3 Parts
*C History Recap 2026 - Part 2 of 3 Parts* follows C’s standardization and technical evolution from the K&R era through C23. It also examines the compilers, standard libraries, build systems, analyzers, debuggers, testing frameworks, and embedded toolchains used in contemporary C development.
C
Read article →C History Recap 2026 - Part 3 of 3 Parts
*C History Recap 2026 - Part 3 of 3 Parts* explores C’s major production uses, enduring strengths, notable software, and persistent safety and maintenance challenges. It also examines current C2y work and the language’s likely future as a compact native foundation within increasingly multilingual systems.
C
Read article →Zig History Recap 2026 - Part 1 of 3 Parts
*C History Recap 2026 - Part 3 of 3 Parts* explores C’s major production uses, enduring strengths, notable software, and persistent safety and maintenance challenges. It also examines current C2y work and the language’s likely future as a compact native foundation within increasingly multilingual systems.
Zig
Read article →Zig History Recap 2026 - Part 2 of 3 Parts
*C History Recap 2026 - Part 3 of 3 Parts* explores C’s major production uses, enduring strengths, notable software, and persistent safety and maintenance challenges. It also examines current C2y work and the language’s likely future as a compact native foundation within increasingly multilingual systems.
Zig
Read article →Zig History Recap 2026 - Part 3 of 3 Parts
*C History Recap 2026 - Part 3 of 3 Parts* explores C’s major production uses, enduring strengths, notable software, and persistent safety and maintenance challenges. It also examines current C2y work and the language’s likely future as a compact native foundation within increasingly multilingual systems.
Zig
Read article →pip vs uv: Is Python Finally Getting a Package Manager People Can Agree On?
Take away point:
For small scripts, pip may be enough. For modern projects, uv is hard to ignore.
Python has always been loved for its simplicity, but Python packaging has a reputation for being anything but simple.
For years, beginners were told to use pip, then create a virtual environment, then maybe use requirements.txt, then maybe use pip-tools, then maybe use pipx, then maybe learn Poetry, Conda, pyenv, Hatch, or PDM depending on who they asked.
That is where the controversy starts.
Some developers look at uv and say, “Finally, Python has a fast modern tool that brings everything together.”
Others say, “Do we really need another Python package tool?”
And then there is the deeper question:
Should Python’s future packaging workflow be centered around a newer external tool, or should the traditional pip workflow remain the main path?
That is the heart of the pip vs uv debate.
The Simple Difference
At the simplest level:
pip = the traditional Python package installer
uv = a newer, faster Python package and project manager
pip installs Python packages.
uv can install packages too, but it also handles virtual environments, lockfiles, Python versions, project dependencies, development tools, and more.
So a very short comparison would be:
pip installs packages.
uv manages Python projects.
That does not mean pip is bad. It means pip has a narrower job.
Why pip Is Still Important
pip is the familiar standard. Almost every Python developer has seen this:
python -m pip install requestsIt is simple, widely documented, and supported across countless tutorials, courses, hosting platforms, and deployment guides.
For beginners, pip is still useful because it teaches the basic idea:
I need a package → I install the package
For example:
python -m pip install flaskThat command is easy to understand. It installs Flask.
The problem is that real projects usually need more than one package. They need isolated environments, repeatable installs, development dependencies, and version control over the full dependency tree.
That is where plain pip starts to feel limited.
The Lockfile Problem
One of the biggest differences between pip and uv is the lockfile.Plain pip does not have a first-class lockfile workflow like uv, Poetry, npm, Cargo, or pnpm.
With traditional pip, people often use[1]:
python -m pip freeze > requirements.txtThat creates a file like this:
requests==2.32.5
urllib3==2.5.0
certifi==2025.10.5
charset-normalizer==3.4.4
idna==3.11
This is useful, but it is not quite the same thing as a modern lockfile.
A requirements.txt file can be a pinned snapshot of what is currently installed, but it is not usually a resolver-managed record of the project’s full dependency decision process.
A simple way to think about it:
requirements.txt = a package install list or pinned snapshot
lockfile = the exact resolved dependency graph chosen for the project
That difference matters because projects often depend on packages that depend on other packages.
For example, your project might directly depend on:
requests
But requests may bring in other packages such as:
urllib3
certifi
charset-normalizer
idna
A lockfile records the exact resolved versions of both direct and indirect dependencies.
With uv, the lockfile is:
uv.lock
In a modern uv project, your pyproject.toml says what your project needs, and uv.lock records the exact versions that were resolved.
In plain terms:
pyproject.toml says what you want.
uv.lock says exactly what you got.
pyproject.toml: Python’s package.json?
pyproject.toml is often compared to JavaScript’s package.json. That comparison is not perfect, but it is useful.
A basic pyproject.toml might look like this:
[project]
name = "my-python-app"
version = "0.1.0"
description = "A simple Python project"
requires-python = ">=3.11"
dependencies = [
"requests",
"fastapi",
]
This file describes the project. It can include the project name, version, Python version, dependencies, build settings, and tool settings.
For example, it can also configure tools like Ruff, Black, Pytest, and Mypy:
[project]
name = "my-python-app"
version = "0.1.0"
requires-python = ">=3.11"
dependencies = [
"requests",
"fastapi",
]
[dependency-groups] dev = [
"ruff",
"black",
"pytest",
"mypy",
]
[tool.ruff]
line-length = 100
[tool.black]
line-length = 100
[tool.pytest.ini_options]
testpaths = ["tests"]
[tool.mypy]
python_version = "3.11"
strict = true
Those tools do different jobs:
Ruff = checks code and can format code Black = formats code Pytest = runs tests Mypy = checks type hints
So yes, pyproject.toml is a lot like Python’s modern version of package.json[2].
But the lockfile is separate.
pyproject.toml = project configuration
uv.lock = exact resolved dependency versions
How pip Usually Works
A common traditional pip workflow looks like this:
python -m venv .venv
source .venv/bin/activate
python -m pip install requests
python -m pip freeze > requirements.txt
On Windows PowerShell, activation usually looks more like:
.venv\Scripts\Activate.ps1This workflow is familiar and still works.
The weakness is that you are manually combining several ideas:
venv creates the environment pip installs packages pip freeze records installed versions requirements.txt stores the package list
That is a lot of separate mental steps, especially for beginners.
How uv Works
With uv, you can still use a pip-like workflow:
uv venv
source .venv/bin/activate
uv pip install requests
But uv also supports a more project-centered workflow:
uv init my-python-app
cd my-python-app
uv add requests
uv run python main.py
In that style, uv updates your pyproject.toml, resolves dependencies, manages the environment, and creates or updates the lockfile.
That is the major shift.
With pip, you usually think:
Create environment → activate environment → install packages → freeze dependencies
With uv, you can think:
Declare dependencies → lock dependencies → sync environment → run project
Creating Virtual Environments with uv
By default, this command creates a virtual environment named .venv in the current project directory:
uv venv
That is similar to:
python -m venv .venv
You can also choose a custom environment name in the current directory:
uv venv my_custom_env
That creates:
./my_custom_env
You can also create the virtual environment in a custom location:
uv venv ~/python-envs/my-project-env
Or with an absolute path:
uv venv /home/andy/python-envs/my-project-env
So yes, uv can create virtual environments outside the current directory.
That is useful if you do not want every project folder to contain a .venv directory.
For a project-managed uv environment, .venv is the default, but uv also supports a custom project environment path through UV_PROJECT_ENVIRONMENT.
For example, a custom relative path:
UV_PROJECT_ENVIRONMENT=envs/my-app uv syncThat creates or uses a project environment relative to the workspace root.
A custom absolute path can also be used:
UV_PROJECT_ENVIRONMENT=/home/andy/python-envs/my-app uv syncThat tells uv to use that exact location as the project environment.[3]
What Tools Does uv Replace?
One reason uv gets so much attention is that it does not only compete with pip.
It aims to replace or reduce the need for several tools in the Python workflow.
Here is the rough picture:
pip → package installation
pip-tools → dependency compiling / pinned requirements
pipx → installing and running Python command-line tools
poetry → project and dependency management
pyenv → Python version management
twine → package publishing virtualenv → virtual environment creation
uv tries to bring many of those jobs into one tool.
For example:
uv add requestsadds a dependency.
uv syncsyncs the environment from the lockfile.
uv run pytestruns a command inside the project environment.
uv tool install ruffinstalls a Python command-line tool.
uv python install 3.12installs a Python version.
This is why uv feels different from pip. pip is an installer.
uv is trying to be a full Python workflow manager.
Why Some Developers Prefer pip
There are still good reasons to use pip.
Use pip when:
You are following older tutorials. You want the most universal Python command. You are teaching absolute beginners. You need the simplest possible install command. You are working in an environment where uv is not available.
For example, this is still clear and useful:
python -m pip install djangoAlmost everyone understands it.
pip is also deeply established. It is not going away just because uv exists.
Why Some Developers Prefer uv
Developers like uv because it is fast, modern, and more complete.
Use uv when:
You are starting a new Python project. You want faster package installation. You want a lockfile. You want cleaner virtual environment management. You want one tool instead of several tools. You want a workflow closer to npm, Cargo, or pnpm.
A typical uv project can look like this[4]:
uv init my-app
cd my-app
uv add fastapi
uv add --dev ruff pytest mypy
uv run pytest
That is clean.
It also feels familiar to developers coming from JavaScript, Rust, or other ecosystems with stronger project management tools.
The Real Debate
The real debate is not just speed.
Yes, uv is fast. That matters.
But the deeper debate is about Python’s identity.
Python has always been flexible. You can use pip, venv, Conda, Poetry, Hatch, PDM, pyenv, pipx, pip-tools, or some combination of them.
That flexibility is powerful.
It is also confusing.
uv is popular because it says:
What if one tool handled most of this?
That is exciting, but it also makes some developers cautious.
They may wonder:
Is uv mature enough? Should beginners learn uv before pip? Will uv become the new default workflow? Is Python packaging becoming simpler, or just changing tools again? So Which One Should You Use?
For beginners, it still helps to understand pip. pip teaches the basic idea of installing packages, and it appears everywhere in Python documentation and tutorials.
But for new real-world projects, uv is very attractive.
A balanced recommendation would be:
Learn what pip is. Use uv for modern project workflows.
Or even simpler:
pip is the classic installer. uv is the modern project manager.
If you only need to install one package quickly, pip is fine.
If you are building a project with dependencies, development tools, virtual environments, and reproducible installs, uv may give you a cleaner path.
The pip vs uv debate is not really about whether pip is useless.
It is not.
pip is still important, familiar, and widely supported.
The debate is about whether Python developers should keep stitching together several separate tools, or whether a tool like uv should become the new center of the Python workflow.
Takeaway Points
pip installs packages.
uv manages projects, environments, tools, Python versions, and lockfiles.
For small scripts, pip may be enough.
For modern projects, uv is hard to ignore.