Continuing the discussion from Solid section cuts:
When SketchUp was first created, the vision was to have such a simple toolset that you could access every tool that you would need right from the home screen. And for advanced users, they could quickly use modifier keys to make those simple tools powerful.
A flaw in many other applications at the time (and this is still true today) was that features were added over and over again so that a once-simple application is now cumbersome and complicated. We wanted to avoid this at all costs. Which is why SketchUp integrated Ruby so that users could create those “missing” tools that are key to their workflow.
We get a lot of feature requests that “should” be part of the core and should be “easy” to implement. And in some cases, this may be true (even though we have a “Just” and “Basically” Swear Jar to emphasize that implementing anything is not simple), but it would fly in the face of our original vision for SketchUp: keep it simple, powerful, and accessible. And we have to make difficult trade-offs deciding which new features should be part of the core and which features should be part of the extension ecosystem. So my ask to you is – and to others who have any feature request – if it’s important to you then rally people around your idea. If we know that a ton of people would love to see feature XYZ in SketchUp, it helps a lot when we have to make those tough development choices.