I think it is time for us to stop trying to make sense of Adobe's decisions and strategy, it is not the first time Adobe spent a lot of time and effort for nothing (Flash Lite anyone?). We should not base any choice or decision on what Adobe did or did not, their interest (selling tools and apparently making them cheap too) is not something we share and their decisions, from laying off a quarter of their European and American workforce to send those jobs to India, to disfranchising developers and trying to seduce designers with technologies they do not even have yet, to letting Apple and Microsoft enslave them, to killing Flash... the list is too long!
Let's define what is good for us and ignore why Adobe did what. Stephane ' On Tue, Jan 10, 2012 at 10:01 AM, Doug McCune <d...@dougmccune.com> wrote: > The saddest thing to me is how much time and effort went into building an > entirely new (yet still incomplete) component model (Spark) that was built > all around the idea of Catalyst. That's not to say that the Spark > architecture doesn't have good ideas when you remove Catalyst from the > picture, but the amount of time that went into designing it to work with > the Fc tooling was all for naught. I have to believe many decisions would > have been made differently, and a lot of time would have been invested > differently had the Catalyst tooling support not been the priority. > > Personally I'm happy to see Catalyst go, and would have been happier to see > it go long ago.
