I feel like we had this discussion already :)... like 8 months ago right after WA announced they were only going to be building PHP products in the future.
But, while I feel your pain - I also see WebAssist's decision to actually be very wise. I, too, used to code in a non-PHP language, exclusively (ColdFusion). But, I found that learning PHP not only was easy after getting my feet wet, I became a better programmer all the way around. As far as it concerns WebAssist, by focusing on the most broadly used server side language, they are able to generate far more products and extensions than if they were researching, developing, and testing on three separate platforms. They are also able to get through the development stage much quicker and have new releases, as well as, fixes deployed much quicker.
But, WA's decision is also somewhat indicative of how some of these languages are faring. We have seen the debacle at Microsoft... who knows which version of ASP they will continue to enhance or support. Adobe has even dropped ASP.net support beginning in DWCS4. While DW stiill has an ASP tab, Microsoft stopped developing plain ASP and is only developing ".net". I am not sure how WebAssist - a company that makes products for Dreamweaver use - could even consider developing ASP apps anymore, anyway.
As far as ColdFusion goes, while it is probably the cleanest and strongest of the 3 server side languages, it is very expensive to license and most people outside of huge corporate web infrastructures use it far less than a choice like PHP.
