Heavy project development stack:

0. Research Driven Development
1. Documentation Driven Development
2. Community Driven Development
3. Test Driven Development
4. Resource Driven Development
5. Time Driven Development

Research Driven Development is when you need to research (learn) a bit, and do that bit, then research a bit, then do that bit, and so on ...

Documentation Driven Development is when you write the detailed documentation of the parts that you need, before actually implementing them in the project.
Not all projects require extensive documentations despite what most people try to tell you; but it's extremely helpful.

Community Driven Development is when the project is as big as its community of developers; sometimes that tasks cannot be handled by one person, so other experts will be included in the community and those experts are the ones that continue their parts of the project.

Test Driven Development is when you write a usage of the project, and then actually go and implement it. Many tools are available for this job.

Resource Driven Development is when you can only expand your project with more resources weather resources are money, servers, or even customers.

Time Driven Development is when the project grows when time passes, or shrinks when time passes. Time-sensitive usually sacrifice other resources weather its money, quality, or quantity in order to get the right time.

Oh, btw, I just made these up, don't need to go looking them up :)

This is the amount of Template Meta Programming I have to do just because I decided not to use virtual inheritance in C++ due to the run-time performance hit!

Does anyone have a better name for "extensie"? I made it up since I can't find any useful English word.

If anyone is interested, we will have a package manager or some sort for it in the future.
We will not work on it straight away because the proposal is not ready (we just started it) yet.

I suggest everyone who's interested, you can add more details about the proposal; or even edit it completely.

Here you will find the draft for it:
https://gitlab.com/webpp/webpp/-/blob/package-manager/proposals/package-manager.md

Macros. Just Marcos.

Old C++ was not a good language to do web dev in.
With a good web framework, C++ is totally capable of handling web development.
And it has many more features than other programming languages; specially in the world of TMP and compile-time execution.

I even talked about language features with the creator of JavaScript on twitter (I did not know who I was talking to at first 😁);
He believed we should strip down the features of a language to make sure it's easy to use; I believe, that's the libraries' implementer's job.

Code is not compile-able!

Kidding, now you can compile the project.

I'll keep the master branch compile-able from now on; but that means the master branch won't me the branch I'll be working on.

Transactional Memory TS:

https://en.cppreference.com/w/cpp/language/transactional_memory

Working on the new routing system since I'm now hopefully done with the extension system.
It's a time-lapse of only 2hrs of coding.
The result is in the "dev" branch.

I'm moving from 80 characters limit per line into 110 characters limit per line.
Some lines became just absolutely unreadable. I had to do something about it.

Even though I like the project to have 80 chars limit, but because of so many meta programmings done in the project I had to do something about it.

Example of an application that you can write with the help of this frame work (soon enough God willing).

The code above is a pseudo code for now; but most of it are half implemented.

Turns out doing "ConceptType auto&&input" in argument list is not a the best way when you end up needing decltype(input).
The consts and references are in the way.
There are other ways to deal with this of course.

My types are not long enough. I should work on that! 😁

It's because of my "extension system" which does some meta programming to make sure the user of the library can add extensions to the router and all the descendants of the router can be instantiated with the exact type (including the extension types).

For example we can have an extension that parses HTTP cookies and the library user can just write:

ctx.request.headers.cookies["session"]

I should make a comedy show with the bugs I make :)

I successfully made the errors longer. 😂

At the same time clang-format!!!

Till now GCC 10.1 was the best choice for this framework, now after adding this code, we'll be back to clang (even though currently clang does not support non-type template parameters which I'm planning to use).