It's exciting to see some recent momentum into adopting DDEV as the official local development environment for Drupal, supported by core and contrib community leaders.
To summarize the linked thread, members want to get behind a single solution for running Drupal - DDEV. We (at Velir) recently made this same switch. From an anecdotal standpoint, I was able to get our BSAs, UX, and front ends running on it very quickly having them follow Randy's excellent instructions on installing it - most of those folks who have little to no Drupal/LAMP experience. This empowers those users to participate in projects beyond purely technical aspects and get 'hands on' with Drupal in a way that wasn't possible before (without a lot of technical expertise).
This speaks volumes to solving the difficult task of just 'running Drupal' if you are an evaluator, tester, want to experiment / try modules, or simply learn Drupal. It runs on all major operating systems and is very simple to install for anyone regardless of their technical expertise (which is a very important point). Beyond that, the support behind DDEV is phenomenal.
All of these things combined greatly simplify what is one of the most common complaints around Drupal - getting started. This to me is a very important step for the community to take an official stance on, because easing this process makes adoption, evaluation, testing and development easier for all sorts of job roles and will help make Drupal easier to approach while simplifying a lot of the documentation currently out there on how to 'run' Drupal locally.
I only wish I had done this sooner, I would have approached sections of the Drupal 10 Development Cookbook differently. Theres always a future revision to make those updates. From now on when it comes to Drupal development or testing articles, I am only going to be writing them from a perspective assuming you are (because you should be) using DDEV.
It's going to make things so much easier for everyone.