The other day someone on the NUG list posted a somewhat lengthy message on Web Edition bugs. They were asking “why was Web Edition so buggy after a whole year?” Here is my response (mostly the same but with some changes).
Sure, Web Edition has more than its share of bugs. Like all bugs, however, it all depends upon the beholder. What bug causes the most pain for RS’ is the one that gets fixed first. I’ve seen a lot of the same things the community has discovered and have just worked around them (where I can). I was using WE in a commercial project during the first beta ( a year ago) and while we got it to work it wasn’t very good. That one project probably generated over a hundred feedback reports. In my opinion WE really hasn’t really been usable until 2011 R3.
Part of the problem, in my opinion, is that RS has NOT created enough Web Edition applications for themselves. If you don’t thoroughly exercise the framework you just don’t see the things you’d see in a big, complex application (like we are creating). There is ONE real world example of Web Edition on their website. While I don’t know how many examples are ‘enough’, I know that one is definitely not enough.
Web Edition exposes the same problems that we all see in Cocoa, Carbon, and in the IDE on a regular basis. Unless RS experiences the pain it won’t get fixed in a timely manner because it’s not as important to them. The Reporting editor and generator and the database editor are but two examples of things in the IDE that RS doesn’t use in ANY of their products. It shows because there are gaping wholes in usage that make them unusable for many developers.
RS takes pride in saying they eat their own dog food because they use Real Studio to make Real Studio. Admirable, but they tend to be on a restricted diet since they don’t eat everything on the menu. They rarely change the menu’s for the IDE so the Menu Editor hasn’t seen many changes or enhancements. As far as I know, they don’t use a database in the IDE so I see no reason why they’d be using the database editor on a regular basis. They don’t do much with StyledText or Movies so its no surprise that those classes are minimalistic (at best).
Since the IDE has no need for date pickers, they have never provided one. Likewise, the Listbox is good enough for the IDE while we’ve been asking for a more powerful grid component for years. Full RTF support? Forget about it because StyledText is good enough for the IDE. A better toolbar control? Well that one’s a bit of a mystery since the IDE is obviously using something different than what they provide to us.
My point is I’m not sure why anyone would be perplexed about long standing bugs. Sure, they’re painful to you and me (and my clients), but they’re not (as) painful to RS.
Lobbying the community to get Feedback reports higher in the list is about the only way to realistically get a bug fixed. But even that is a crap shoot as there are quite a few bugs (not feature requests) very high on the list that have been there for a long time. So the only thing conclusion that I can come up with is that the bug that all the rest of us are seeing isn’t painful to RS so therefor it isn’t a priority for them.
This is my opinion as a ten year Real Studio consultant. I know and respect most of the engineers and staff at RS and I think they do a remarkable job. However, I think as a company they mostly ignore those like me (an Enterprise user that ponies up thousands of dollars per year) and focus, almost exclusively, on the hobbyists (that bring in a hundred dollars a year at best). If they could make me happy(ier) the hobbyists would come along anyway (see history of Visual Basic).
Bugs happen in every software product. I remember grousing about Visual Basic bugs when I was a big VB6 user. I know that my code back then had plenty of work arounds for bugs in their API. There is no doubt that Microsoft had more developers working on the product (as a whole) than RS has working on Real Studio. There’s also no doubt that VB6 has a considerably larger user base than Real Studio. I feel that this resulted in more workarounds being posted and more alternate solutions. The reverse is that our smaller community doesn’t have as many solutions and documented workarounds so it feels worse but I feel that it isn’t.
Anyway, that’s enough on my opinions about bugs and such. Have a good New Year and be safe. Happy coding!