Who's using Web Client? Or, what about ABL clients?

In another thread, we got started talking about ABL clients versus other technologies.  I suggested that I could readily understand why someone who had already paid the price for client licenses would find it attractive to stick with ABL clients, especially since the ABL GUI for .NET now allows one to make so much more attractive and fundtional user interfaces.  But, since my personal focus is modernization and transformation in which potentially there are major changes to the application architecture, I wondered how often one would choose an ABL client for a new application.  Certainly, a question like this requires context.  E.g., an AP who is selling an application will be driven to a significant degree by market forces and may need to provide a particular client type since that is what the market requires.  The AP also tends to have a bigger budget motivation to make more radical changes to architecture, including a new UI and probably, on average has a larger staff, so having UI specialists is less of an issue.  Conversely, and end-user customer has really their own internal business drivers to consider so a move to a totally different technology for the client is most likely to happen in a move from ChUI than it is from existing ABL GUI clients.  With ChUI, the only software on the user's machine is the telnet client, so moving to ABL GUI clients, with or without .NET is as big a change as moving to any other technology client.

One of the issues which has often been raised in discussions of this sort is license costs.  Another is the overhead of having a software install on every user's system.  This is, of course, one of the reasons I am fond of the WUI alternative since the only licensing and management issue is the AppServer required in any modern architecture (yes, Greg, I know you also advocate Sonic and little or no AppServer, but for simplicity sake I want to leave that out of the discussion for the present since I think the idea needs more development and specification before we know how it fits). A .NET or Java client may require the per system install, but no per user license beyond the AppServer.  Conentional ABL clients require additional licensing ... unless they are Web Client.

So, what is the real story with Web Client?  Are lots of people actually using it?  Is it working for them to have a self-updating client?  I know that there are some things about it that are broken with OO features one can't use yet ... is that a major obstacle?   of are those using it still mostly pre-OO so it isn't an issue yet.

Bottom line, what kind of client would you pick for a new application (or one being so re-done as to effectively be new)?  And why?  And what real experience is behind that preference?