Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
by gromitski on Thursday April 08, 2010 @09:17PM
(#1251566)
I'm sorry but that is a terrible excuse for what they've done. As a flash developer hit hard by the recession, having another (strong) string in my bow was essential for survival. Like others in my industry, I don't have time to completely re-train every time a new product comes onto the market. Being able to produce for a different device using my current skills is a blessing. Apple should be thoroughly ashamed with themselves and I for one will be approaching the Monopolies Commission regarding this.
[ Parent
| on HN ]
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
by bobwaycott on Friday April 09, 2010 @03:02AM
(#1252100)
While it sucks when times are tough, if you want to develop for a new platform to make money, then make and take tge time necessary to learn the platform and its tools.
Your complaint here is disingenuous. When you learned to be a Flash developer, did you complain that Macromedia should be ashamed cos they didn't build their tool in HTML & CSS?
If you want to develop for the iPhone, then develop for the iPhone.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
by gabrielroth on Thursday April 08, 2010 @10:25PM
(#1251677)
I sympathize with your economic plight. But the fact that you're having a hard time making a living using Flash doesn't give Apple the obligation to provide you with a development platform.
Since the iPhone has less than 20 percent of the smartphone market, it seems unlikely that the Monopolies Commission will be interested.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
by barrkel on Friday April 09, 2010 @12:20AM
(#1251857)
Apple isn't obliged to actively deprive people of development platforms either.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
by stevenN on Sunday April 11, 2010 @03:17AM
(#1256507)
I thought of doing the same thing with my Pl/M experience. Decided to learn new tool sets/languages instead:-)
You will find your self in serious trouble moving forward if you tie yourself to only knowing a single company's toolset and tying your future to the well being of that companies tool set. Especially Adobe's; a company as fickle as Apple.