Thanks, Alex, Nope, I didn't yet asked Adobe. To be honest, I don't really know whom to ask there. I was hoping this is a known issue, so I wouldn't need to do my own research.
Other than that, I do understand the benefits of updating, there are more options being discussed, Flex being only one of them, but I'm not in a decision making position, at most I could suggest. Best, Oleg On Sun, Jul 20, 2014 at 10:37 AM, Alex Harui <aha...@adobe.com> wrote: > On 7/18/14 7:17 AM, "Left Right" <olegsivo...@gmail.com> wrote: > >>I'm using SDK 4.6.0 (the last version officially released by Adobe), >>the RSLs load fine on machines with older players, but not on Windows >>with FP14. > Has this issue been raised at Adobe? > > >>Frankly, I'm looking for reasons to update. > The reason to update is this: By moving to Apache Flex, any bugs you want > fixed or features you want added can proposed as patches by yourself, and > should show up in the next release (assuming there isn't backward > compatibility issues or major bugs in the patch). Let's say you find a > bug in the SDK. Right now you can call Adobe and pay them to help you, > but I'm not sure that will be the case 3 years from now. You can > monkey-patch your fix, but what if the monkey-patch is big enough to > defeat the value of the RSLs? > > >>Cached RSLs had >>been a major argument against updating so far, so I'm looking to gain >>some confidence when I will try to convince my boss that we would be >>better off with the newer SDK. > > Yeah, losing the RSLs can be painful for certain scenarios, but instead of > worrying about getting hosed by a bad player release, help us develop > FlexJS so you no longer need RSLs. > > -Alex >
