But it has a few judgemental statements, which are controversial.
Like it is "... frequently littered with #[attributes]." -Actually I think it is a very clean way to transport the information.
The build is slow is another controversial - imo not compared to more complex c/c++ projects where includes are parsed over (c++ really needs modules but C++20 adaption is not there yet)) and over again and you really and where you need several best practices for fast compiling code and tricks like cmake unity build (all not the standard for many projects)
Also yes, static linking and huge binaries are the default, but not required. You can very well work with dynamic linking, but will have the extra work as always to somehow make sure the user has everything in place then.
There are some more controversial statements and I would maybe give it another review, to show at least both sides instead of using judgemental verbs and adjectives.
But it has a few judgemental statements, which are controversial.
Like it is "... frequently littered with #[attributes]." -Actually I think it is a very clean way to transport the information.
The build is slow is another controversial - imo not compared to more complex c/c++ projects where includes are parsed over (c++ really needs modules but C++20 adaption is not there yet)) and over again and you really and where you need several best practices for fast compiling code and tricks like cmake unity build (all not the standard for many projects)
Also yes, static linking and huge binaries are the default, but not required. You can very well work with dynamic linking, but will have the extra work as always to somehow make sure the user has everything in place then.
There are some more controversial statements and I would maybe give it another review, to show at least both sides instead of using judgemental verbs and adjectives.