HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
the-benchmarker
web-frameworks
PHP2018–2026
the-benchmarker / web-frameworks

web-frameworks

Which is the fastest web framework?

14Distinct people
14Mentions
0Explicit recommenders
7.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Which is the fastest web framework?

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:02:05 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year14 dated mentions

Observed mentions: 2018-01-09 20:34:36 UTC to 2026-10-17 06:06:10 UTC.

0123452018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC312
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC514
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC422
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC110

What Hacker News says

1 sources
gg582·Oct 17, 2026Submission

Show HN: Cwist; a hobby-grade C17 web framework that keeps your app simple

First of all, I'm not claiming that my framework will save industrial C/C++ development. It's just a hobby project. Industrial code needs safer code, not easier code. But when you're developing a blog at 8 PM, long template errors are annoying. You need CRUD and RDBMS. It's simple. CWIST is for that kind of work. It sacrifices memory safety, smart pointers, and modern C++ abstractions. In return, compile errors are more predictable. #include <stdio.h> #include <cwist/app.h> #include <cwist/core/db/pool.h> #include <cwist/core/template/template.h> static cwist_db_pool_t *g_db_pool; static void send_error(cwist_http_response *res, const char *msg) { res->status_code = CWIST_HTTP_INTERNAL_ERROR; cwist_http_header_add(&res->headers, "Content-Type", "text/plain"); cwist_sstring_assign(res->body, msg); } sta
Read the rest
tic void render(cwist_http_response *res, const char *path, cJSON *ctx) { cwist_sstring *html = cwist_template_render_file(path, ctx); if (html) { cwist_http_header_add(&res->headers, "Content-Type", "text/html"); cwist_sstring_assign(res->body, html->data); cwist_sstring_destroy(html); } cJSON_Delete(ctx); } static void handle_index(cwist_http_request *req, cwist_http_response *res) { (void)req; cJSON *ctx = cJSON_CreateObject(); cJSON_AddStringToObject(ctx, "title", "CWIST Example"); cJSON_AddStringToObject(ctx, "greeting", "Hello from CWIST"); render(res, "templates/index.html", ctx); } static void handle_users(cwist_http_request *req, cwist_http_response *res) { (void)req; if (!g_db_pool) return send_error(res, "database pool unavailable"); cwist_db_pool_exec(g_db_pool, "CREATE TABLE IF NOT EXISTS users (id INTEGER PRIMARY KEY, name TEXT);" "INSERT INTO users (name) SELECT 'Alice' WHERE NOT EXISTS " "(SELECT 1 FROM users WHERE name = 'Alice');" "INSERT INTO users (name) SELECT 'Bob' WHERE NOT EXISTS " "(SELECT 1 FROM users WHERE name = 'Bob');"); cJSON *rows = NULL; if (cwist_db_pool_query(g_db_pool, "SELECT id, name FROM users ORDER BY id;", &rows).error.err_i16) return send_error(res, "failed to query database"); cJSON *ctx = cJSON_CreateObject(); cJSON_AddItemToObject(ctx, "users", rows ? rows : cJSON_CreateArray()); render(res, "templates/users.html", ctx); } static void handle_health(cwist_http_request *req, cwist_http_response *res) { (void)req; cwist_http_header_add(&res->headers, "Content-Type", "text/plain"); cwist_sstring_assign(res->body, "ok"); } int main(void) { g_db_pool = cwist_db_pool_create("./app.db", 1); if (!g_db_pool) return 1; cwist_app *app = cwist_app_create(); cwist_app_get(app, "/", handle_index); cwist_app_get(app, "/users", handle_users); cwist_app_get(app, "/health", handle_health); cwist_app_use_https(app, "cert.pem", "key.pem"); cwist_app_listen(app, 8082); cwist_app_destroy(app); cwist_db_pool_destroy(g_db_pool); return 0; } Code style is old and still small. The code is simple and stupid. CWIST functions use the same `cwist_xx_xx` naming format. It's consistent. It's harder to make a slop in CWIST. Features - CWIST GC for fast prototyping. It's closer to a garbage sweeper than a traditional GC, and lighter. - Dev blog engine - HTML Template Engine - WASM External benchmark: https://web-frameworks-benchmark.netlify.app/compare?f=cwist... Latest results may be masked: https://github.com/the-benchmarker/web-frameworks/issues/977... Unofficial results (not reliable): https://github.com/c4punks/CWIST/actions/runs/39000473564/jo... Dev blog: https://oborona.zip Org: https://c4punks.github.io It doesn't help my portfolio, but please star the project if you enjoyed it. Special thanks to https://github.com/thegoodengineer for inviting organization members.
2 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.