Because the performance of existing web frameworks is... _absymal_. They are nowhere close to how fast they can be. And I don't mean slower by a bit, I mean close to a factor of 10x. My in-house framework can serve 600-700k requests/s on a single core, while beast (the best c++ framework i could identify) does 250k at best. nginx/apache and other prebaked servers are even slower, at 100k req/s. Tells you all you need to know.
If I were to open source a project these days, I will definitely have my progress be a clean, huge initial single commit. Too many busybodies trying to piece together code forensics to say something is vibe coded or not.
I write my open source code, because I need it and then maybe some other too. If they don't want to use it, because they wrongly think it's generated, I couldn't care less.
If new free projects had to have a "100% artisanal" pledge I wouldn't even consider starting one. Hand-crafting the core design is still superior. Not delegating the grunt work for copy-paste level stuff is just wasting time, though. I don't require the circuit boards in my electronics to be hand-drilled either.
I built Vermell, a minimal, zero-dependency C++ web framework designed to explore low-level networking, non-blocking I/O with Linux epoll, and simple Express-like routing under the hood.
I originally started this ~4 years ago and paused it over socket/memory security concerns. Recently, I picked it back up, audited the codebase, and packaged it with APT, Docker, and an NPX starter.
As cool as it sound, do we actually need it? also what problem are we solving?
Performance is probably the only angle that has some potential but only short requests, the db and other external IO/services is a bigger bottleneck.
Because the performance of existing web frameworks is... _absymal_. They are nowhere close to how fast they can be. And I don't mean slower by a bit, I mean close to a factor of 10x. My in-house framework can serve 600-700k requests/s on a single core, while beast (the best c++ framework i could identify) does 250k at best. nginx/apache and other prebaked servers are even slower, at 100k req/s. Tells you all you need to know.
It looks suspicious. It has only 18 commits, the majority of code was added via single initial commit. is it LLM-generated?
If I were to open source a project these days, I will definitely have my progress be a clean, huge initial single commit. Too many busybodies trying to piece together code forensics to say something is vibe coded or not.
I write my open source code, because I need it and then maybe some other too. If they don't want to use it, because they wrongly think it's generated, I couldn't care less.
If new free projects had to have a "100% artisanal" pledge I wouldn't even consider starting one. Hand-crafting the core design is still superior. Not delegating the grunt work for copy-paste level stuff is just wasting time, though. I don't require the circuit boards in my electronics to be hand-drilled either.
Read through the readme a bit, it's obv it is
sounds like you are envious of their productivity. define "suspicious"
I like the idea and the logo. But some real world examples like database usage, partials within templates and handling forms are missing.
You need examples for actually using different databases.
Hey HN,
I built Vermell, a minimal, zero-dependency C++ web framework designed to explore low-level networking, non-blocking I/O with Linux epoll, and simple Express-like routing under the hood.
I originally started this ~4 years ago and paused it over socket/memory security concerns. Recently, I picked it back up, audited the codebase, and packaged it with APT, Docker, and an NPX starter.
Site & docs: https://vermell.cc/
Would love any feedback on the architecture, security edge cases, or performance.