search

thelukester92 / swift-engine

An entity-component-system game engine built in the Swift programming language.
MIT License
35 stars 7 forks source link

Why stop the project? #86

Open phnessu4 opened 7 years ago

phnessu4 commented 7 years ago

Hi, Luke. I was trying to write a game engine with swift , then i google , it lead me here. Thanks for your project, it really helps me a lot. but i want to ask, why you stop the project? Do you find something new or swift is not proper for a game engine?

thelukester92 commented 7 years ago

At the time that I made this project, Swift was not yet optimized and the game engine ran too slowly. Since then, Swift has improved considerably and should be good for a game engine, I just haven't come back to it. I've been doing more work in C++ and Lua.

On Dec 18, 2016, at 10:19 AM, jason han notifications@github.com wrote:

Hi, Luke. I was trying to write a game engine with swift , then i google , it lead me here. Thanks for your project, it really helps me a lot. but i want to ask, why you stop the project? Do you find something new or swift is not proper for a game engine?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

phnessu4 commented 7 years ago

Thanks for reply. I'll try to develop an engine with swift3, hope the performance will be good. Considering the platform support, I think the final answer should be C++ and Lua. Do you have some suggest for the c++ and Lua engine? Cocos2d-x is a good start ?

thelukester92 commented 7 years ago

I like SDL for C++ and LÖVE2D for Lua, but there are a lot of different ways to go with it.

Luke

On Dec 19, 2016, at 3:37 AM, jason han notifications@github.com wrote:

Thanks for reply. I'll try to develop an engine with swift3, hope the performance will be good. Considering the platform support, I think the final answer should be C++ and Lua. Do you have some suggest for the c++ and Lua engine? Cocos2d-x is a good start ?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.