The main thing that struck me as odd was the distinction between "Simple Static Site" and "Dynamic Web App". If I choose the latter, I am recommended stacks with backends and databases.
However, static sites can have tons of app-like interactivity. And web apps don't necessarily need a backend and a database. It seems to me that if someone knows what you are getting at here, they are probably already capable of evaluating tech stacks without your help.
If you want to separate people who need a backend from people who don't, maybe better questions to ask are "Do you need users to have an account?", "Do you need users to share data with you or each other?", or something along these lines.
Looks interesting but I have to say it seems a bit limited. For example I cannot find Java/Spring Boot anywhere which is one of the go-to frameworks for web app backends where performance and reliability counts.
Are you planning to add more languages and frameworks or is there a specific reason that is is so biased in this regard?
The main thing that struck me as odd was the distinction between "Simple Static Site" and "Dynamic Web App". If I choose the latter, I am recommended stacks with backends and databases.
However, static sites can have tons of app-like interactivity. And web apps don't necessarily need a backend and a database. It seems to me that if someone knows what you are getting at here, they are probably already capable of evaluating tech stacks without your help.
If you want to separate people who need a backend from people who don't, maybe better questions to ask are "Do you need users to have an account?", "Do you need users to share data with you or each other?", or something along these lines.