Something like this is expected to be free
Show HN: I'm open-sourcing my game engine
21–30 of 94 posts
Re: Show HN: I'm open-sourcing my game engine
#22Unless it’s as advanced as Unity, is it possible to even sell an engine these days? Something like this is expected to be free
Re: Show HN: I'm open-sourcing my game engine
#23Earlier quoted context omitted.
Node of course can work on multiple cores, using worker threads [1]. You can even share large data efficiently using a SharedArrayBuffer. [1]: https://nodejs.org/api/worker_threads.html
It isn’t trivial to just split up a game into múltiple worker threads and keep everything in sync. With Go, it’s much easier.
What lends itself well to this?
Re: Show HN: I'm open-sourcing my game engine
#24Re: Show HN: I'm open-sourcing my game engine
#25Glad to see more open source projects like this out there. Surprised it has under 100 stars on GitHub.
Re: Show HN: I'm open-sourcing my game engine
#26Unless it’s as advanced as Unity, is it possible to even sell an engine these days? Something like this is expected to be free
Re: Show HN: I'm open-sourcing my game engine
#27You can absolutely make your own tech but at every step that tech should be tailored for your project, as opposed just a general game platform.
Re: Show HN: I'm open-sourcing my game engine
#28Earlier quoted context omitted.
It isn’t trivial to just split up a game into múltiple worker threads and keep everything in sync. With Go, it’s much easier.
Can you expand on the low hanging fruit of splitting a game into multiple goroutines? What lends itself well to this?
Re: Show HN: I'm open-sourcing my game engine
#29I wasn't expecting this to be modd.io when I saw the title. It's a popular framework/platform for building IO games.
Re: Show HN: I'm open-sourcing my game engine
#30It seems like Apps usually navigate away to a sign in, and then navigate back. Is that pattern hard to implement? Is the issue about cross platform support? Thanks