Contributers here,

First of all amazing library here. It's penetrated every part of my product. I have just have one concern, what's the ultimate direction of this and how much priority is being taken in Vibe.d?

From my perspective Vibe.d is like Express.js. It's not a framework rather a library that can be used to build your own ideas on top of. Love it!

However I see a lot of small details that stop this from being 100% production ready (aside from being in beta and aside from the fact I'm already using it in production) and I'm wondering what the strategies are to make Vibe.d a stable framework. I feel like this alone is a huge benefit of using Dlang.

Also, Vibe.d has been around for a long time. I feel like a lot could be done to spring it's growth and popularity. These kinds of tools is what makes using Dlang worth it. Otherwise, I would have ditched it a long time ago and went with Node.js.

I would also love to contribute since I'm a 7+ year Dlang developer and feel like there are a few parts that need fixing.

Two things I'd look into first (let me know if I'm welcome):

• Fix max header line length of 4000 characters (which for us is an ongoing issue)
• Fix the issues with leaked FDs that seem to happen all the time for me for years.
• Create a library for handling permissions that comes out of the box with Vibe.d
• A library for rate limiting

Let me know what you all think of this. My goal is to add a few features that allow businesses to build lucrative products in Vibe.d. I know a lot of companies are already doing that but I'd love to contribute here to make it more viable across the board.