It’s not been a great week – even though it’s been a short week. I’ve now seen two separate bugs that are HUGE and affecting me for Windows. In REAL Studio Release 3.1 there is memory leak in the Timer Class and in the StaticText class. The end result is that my app, in Windows, will eventually chew up all available memory and bog the entire machine down to the point of being unusable.
Not good at any time, but this mean that both 3 and 3.1 are not usable for me, at least for Windows builds. R 3 has some issues and a memory leak as well. Thankfully, the leak is not as bad. I would go back to R 2.1 but since *that* release also has a nasty Windows bug I can’t go back to it. Dare I go back to R 2?
Initial indications are that RS will not be issuing an interim 3.2 release, however. This is why I think their Rapid Release Model stinks. I’ve got two bugs that keep me from using the latest and greatest release and now have to wait to get a fix.
Your plan runs out in the next 60 days or so? Sorry. You’re S.O.L. It might be great for RS but the Rapid Release Model is becoming the Rapid Bug Model for me. Pretty soon, it’s going to start costing me clients.
A couple people have asked me what I think about Apple changing their stance on letting 3rd party development tools for developing iOS apps and what that means for REAL Software. Meh.
Really, there are so many items RS has to get done before thinking about iOS that it’s not even a concern right now. The only thing that would concern me is if they decided to jump both feet first and devote a lot of resources to it. Cocoa has taken way longer than anyone ever dreamed of (I feel that personnel changes have bit them hard on that one) and now the highly anticipated Web Edition will distract them too.
Don’t get me wrong, I’m looking forward to the Web Edition. I think being able to leverage all my RB knowledge for iOS apps is a great idea too. But, as they say in Missouri, “Show Me!” – I’ll get excited when I see them and can work with them and keep my business in the black.