Open gerchicov-bp opened 7 years ago
To be honest, the complete framework would require an update for 2017 ... ðŸ˜
I must say that the project is currently on hold. As a single developer, it was just too much effort to support two such frameworks (Sparrow and Starling) simultaneously; furthermore, when Apple introduced SpriteKit, interest in Sparrow became quite low.
Sorry! I wish I had better news.
@PrimaryFeather interest in Sparrow should rise because Cocos2d owners decided to kill objc-cocos2d and to develop Fiber2D which is still raw. So today the only actual engine is SpriteKit. But the problem is people usually use swift with it (for example the most of tutorials are about SpriteKit+swift). And in the same time Sparrow looks like more adopted to use with objc
I didn't know about those Cocos2D changes — thanks for the heads-up! But do you think many developers are still interested in an ObjC library? Isn't the majority of developers moving over to Swift?
Let we look at libraries on the main page of cocoacontrols.com: ~43% of projects are written in Objective-C I think it will be still popular because it is stable more or less. In the same time Swift is changed significantly every year. And they change syntax a lot even in the intermediate releases.
@PrimaryFeather I have found out much more serious issue: http://www.dailymail.co.uk/sciencetech/article-4199130/32-bit-iPhone-apps-obsolete-iOS-11.html
Mhm, that's probably one of the reasons why they cleaned up the App Store, removing apps that hadn't received an update for a long time. Seems quite likely. :-/
Hello https://github.com/Gamua/Sparrow-Framework/blob/master/BUILDING.md this instruction is out of date. Could you please update it according to 2016 year?