A first criterion that we use is the support of host platforms. By this we mean whether the solution works on everyone's favourite operating system. Web development is common on Mac or Linux. In very recent history, more and more developers are also appearing who want to work on Windows.
As a second criterion we look at control and compatibility. As a (seasoned) developer you want full control over your local development solution. After all, it is very important to test or investigate new features or any errors as correctly as possible. By fine-tuning locally to lean as close to the production environment as possible, you also avoid a lot of potential problems.
The third criterion is flexibility. In the current IT landscape there is a very wide range of technologies that you want to use. The versions of those technologies follow each other more and more quickly. As a developer you want to be able to switch between all these possibilities very quickly. This is also very important for agencies that offer long-term support because they need to be able to switch quickly between existing websites.
Finally, we have development speed. Once your website is running locally you don't want it to take dozens of seconds for your web page to load. Also, the execution of commands in your terminal window is ideally limited in time. For the sake of simplicity, this duration is directly proportional to the turnaround time of a website.