Because it is targeted not only for PB developers but also for general .NET community.

The word "Power" does not indicate it is meant for PowerBuilder.

Power BI, PowerQuery, PowerPoint, PowerShell, PowerAutomate and all the MS Power-suite of apps do not indicate they are related to PowerBuilder in anyway. They are being used by general / .NET community (and also PowerBuilder developers ).

Coining new brand names loses consistency. Appeon products should ideally start with "Power" so users could easily relate them to their tech-stack and ecosystem. It becomes easier to communicate the tech-stack to the management saying, "We're gonna use PowerBuilder, PowerServer and PowerSharp on our new Cloud project. On our 2-Tier project, we're gonna use PowerBuilder and PowerClient". It's becomes a bliss.

For PowerBuilder developers, "PowerSharp" readily makes sense - for all others, it is a really COOL brand name! SnapDevelop name doesn't indicate it is a C# IDE either. "Power" for consistency and some "Sharp" (or "#") in it would have been cooler. Just saying...

Not that this will result in brand-name change (and not that it is too late to change it either) but I'm just an uncompromising, quality-conscious and detail-oriented front-end guy using PowerBuilder for over 27 years

If Appeon wants to rebrand SnapDevelop as "PowerSharp", it should be done before it is taken by Microsoft and claims its use in inter-state commerce! They seem to be intrigued by the "Power" word lately, LOL. Once it is gone, it is gone forever!

(I get a lot of calls for Power BI contracts from recruiters who are confused that it is the same as PowerBuilder. That "confusion" among the consumers was created in the market by Microsoft using "Power BI")

So, I gave a 45-slide presentation on PowerBuilder, PowerClient, PowerServer and SnapDevelop along with demos last week at my work for 90 minutes and some attendees (PowerBuilder developers) could not pronounce SnapDevelop - they kept saying "SnapChat", "SnapBuilder" - literally - even after I corrected them repeatedly. YIKES! I wasn't surprised and felt PowerSharp or Power# would have made things much easier