I did choose an odd path. Using pure Go as foundation, I almost always get score 100. By not using a framework, I also save some extra code detours. And gets cheaper and hence greener hosting (small footprint saves environment and money).
Frameworks gives a shortcut to the market. I admit. But using a framework for decades, I realized that it also created in my case a maintenance hell when a new version arrived.
I found that the shortcut to the market has a price tag in my case was more expensive in the long term. As it creates a maintenance and dependency hell that comes some years after. Find and create workarounds for all “new features” in a new version of the framework.
So my challenge was to find a way to reduce maintenance time and cost created by magic that I do not understand. And I was willing to pay for the extra time to market…