Flask Explained: The Small Framework That Does Just Enough

Introduction

Django (covered earlier) gives you everything: an ORM, an admin panel, authentication, and a project structure, decided for you. Flask, created by Armin Ronacher in 2010, gives you almost nothing — routing, request handling, and a template engine — and lets you add the rest yourself. That minimalism is the point: for small apps, APIs, and learning, a framework that stays out of the way teaches you more than one that does everything.

A complete app in a few lines

Flask's famous "hello world" is a whole working web app:

from flask import Flask

app = Flask(__name__)

@app.route("/")
def home():
    return "Hello, Flask!"

@app.route("/users/<name>")
def greet(name):
    return f"Hello, {name}!"

The @app.route decorator maps a URL to a function, <name> captures part of the URL as a variable, and returning a string sends it as the response. Add a database with an extension like Flask-SQLAlchemy, add login with Flask-Login, add forms with Flask-WTF — each piece is a choice, not a default, which is why Flask apps look different from each other in a way Django apps rarely do.

The honest trade

Flask's freedom is also its cost: every project must choose its own database layer, auth, structure, and tooling, so two Flask apps can be organised completely differently, and large teams can drift into inconsistency without discipline. Django's "batteries included" approach avoids that by deciding for you. The rule of thumb: Flask for small services, prototypes, APIs, and learning how the web actually works; Django when you want a full, opinionated structure for a large app from day one.

Takeaway

Flask is Python's microframework: routing and requests, with everything else added by choice. Its smallness is a feature for learning and small apps, and a cost for large teams that need consistency. If Django felt like too much framework, Flask is the other end of the scale — and a fine place to understand what a web framework actually does.

Comments

Post a Comment

Popular posts from this blog

Swift Explained: Apple's Language for iPhone, Mac, and More

Introduction Swift is Apple's language for its platforms: iPhone, iPad, Mac, Apple Watch, and Apple TV. Introduced in 2014 to replace the older Objective-C, it was designed to be safe, fast, and — unusually for a systems language — genuinely pleasant to read and write. Even if you never ship an app, Swift teaches one idea every developer should understand: optionals. Optionals: saying "this might be missing" Most bugs in app development come from one cause: code assuming a value exists when it does not. Swift makes that assumption impossible to hide. A value that might be missing is wrapped in an Optional, and you must unwrap it before use. var nickname: String? = nil nickname = "Waqas" if let name = nickname { print("Hello, \(name)!") } else { print("No nickname set.") } String? means "a String, or nothing". The if let unwraps it safely: inside the block, name is guaranteed to exist. There is no way to accidentally us...
Read more

Flutter Explained: One Codebase, Every Screen

Introduction Flutter is Google's framework for building apps from a single codebase: write once in Dart, and ship to iOS, Android, web, Windows, macOS, and Linux. It powers apps from Google Pay to the New York Times crossword app. Its core idea is simple and radical: everything on screen is a widget, and the interface is rebuilt from data whenever that data changes. Everything is a widget In Flutter, there are no separate concepts for layout, styling, and controls — everything is a widget, nested inside other widgets like HTML elements, but in code: import 'package:flutter/material.dart'; class Greeting extends StatelessWidget { @override Widget build(BuildContext context) { return Center( child: Text( 'Hello, Sara!', style: TextStyle(fontSize: 24, color: Colors.teal), ), ); } } Center positions its child, Text displays words, TextStyle styles them — each a widget, composed by nesting. Layout widgets (like Row, Column, ...
Read more

Go Explained: Simple Code That Runs Fast

Introduction Go was built at Google for a specific frustration: large programs that were slow to build and hard to read. The answer was a language that is deliberately small — fewer features, but the right ones, done well. If you know one programming language already, Go will feel familiar within an hour. The interesting parts are not the syntax, but two ideas: goroutines and channels. Goroutines: cheap concurrency Most languages make running things at the same time feel heavy — threads, thread pools, and careful setup. A goroutine is Go's lightweight version: you start one by writing go in front of a function call. package main import ( "fmt" "time" ) func say(text string) { for i := 0; i < 3; i++ { fmt.Println(text) time.Sleep(100 * time.Millisecond) } } func main() { go say("hello") say("world") time.Sleep(500 * time.Millisecond) } The go say("hello") line does not wait — it st...
Read more