I have been working on a Zig web framework that is explicit and simple, but also includes batteries that can be added explicitly if you need to accelerate your work. I was really annoyed by existing frameworks that take away your freedom by imposing strict project structures and conventions, even for simple use cases. This is something I wished was out there so I embarked on building it. I would really appreciate those who are willing to try it out and report bugs
2 Likes
I was going to ask why there is URL for the project, but then realised the title is a URL.
However that is not a link and when I click it, ziggit prompts me to edit it:
which is rather not what I intended.
You might want to put the URL in the body of the message as well.
I am definitely going to have a look at this.
I was looking at the server code, as it’s interest to me due to my work on async I/O and concurrency, and I see that you are only handling one connection at a time. Is this only meant for small development servers? Or am I looking at the wrong code?
Thanks for the feedback
I’m working hard to make a complete IO migration. The project was started with Zig 0.15, where io wasn’t included yet. And also implementing custom database support because currently it only supports the shipped SQLite which is not aimed for production. But contributions are welcome
I use SQLite in production all the time! Sometimes you have to get clever with it (like giving every user/org their own DB) but until you start doing deep queries on large tables, you hardly notice a difference 