I would agree that 1:1 mappings with the variables getting passed as-is is not the most compelling example. In my experience it's best to keep any information about the data model out of component templates. The variables passed to the component should be simple and agnostic of entity types, bundles, field names, etc. I don't have enough experience with the core themes to know if the benefits will shine through, but an easy example is rendering teasers of many different entity types/bundles through the same component. All while keeping the model-specific stuff in Twig (the Drupal templates, being careful to maintain cache metadata) rather than PHP (preprocessing and/or clever theme hook suggestions).
I spent half of my ten years as a front-end Drupal developer wrestling with component-based development on client projects. Components were clearly the future, but the path forward was not.
After that experience - and a few years with JS frameworks - SDC instantly makes perfect sense. It encapsulates exactly how components should work within a Drupal theme. It will also minimize the learning curve for the larger front end community. Teach them how to find the Drupal templates to include their components in and they'll be off to the races.
I identify with #41 and agree that this would be the biggest improvement since Twig. I look forward to building with Single Directory Components one day!
Mark,
After a thorough review of your profile and contribution history - and careful consideration of our ten years as colleagues and friends - I'm certain that you'll do an excellent job creating a Drupal 10 compatible release. I have added you as a co-maintainer with appropriate permissions.
Thanks for creating this issue and for all of your work moving forward!
Gus