OSS Game Engines are increasing their stars on GitHub due to Unity's missteps
1–10 of 215 posts
Re: OSS Game Engines are increasing their stars on GitHub due to Unity's missteps
#2I'm actually kinda excited to start learning some of these. How nice of Unity to force me out of my comfort zone!
Re: OSS Game Engines are increasing their stars on GitHub due to Unity's missteps
#3I’ve been enjoying all the new discussions, comparisons, and content surrounding open source game engines.
Even if it’s clickbait or shallow content, it still raises the awareness of these tools.
Re: OSS Game Engines are increasing their stars on GitHub due to Unity's missteps
#4I'm actually kinda excited to start learning some of these. How nice of Unity to force me out of my comfort zone!
Godot is quite easy to learn as far as general purpose game engines go. Lots of material around too, I know a lot of people like GDQuest and HeartBeast. Their subreddit and discord are also popular.
Re: OSS Game Engines are increasing their stars on GitHub due to Unity's missteps
#5Sad for Unity devs' predicament here, but happy to see Godot gaining increased interest. It's still not as mature as Unity, of course, but they're making steady progress, it definitely seems to be headed in the right direction.
Re: OSS Game Engines are increasing their stars on GitHub due to Unity's missteps
#6Im not well versed in game programming, however I have some knowledge on how to properly structure your software architecture in other domains.
In regards to third party dependencies I agree with what Uncle Bob says, which is to keep them as far away from your stuff as possible. Only introduce a hard dependency if you have to. In my current project I have been doing that and I enjoy the flexibility that this gives me.
For example I can exchange the DI framework for the whole project in a matter of days if need be.
Which leads me to my question with the Unity debacle.
Is it not possible in game development to also structure your architecture that way ? Is the extra work not justified if you have deadlines ? Or is there just a lack of common interfaces that can serve as proper abstraction ?
I am really interested if someone with more insight on game development could shed some light on that.
Thanks.
Re: OSS Game Engines are increasing their stars on GitHub due to Unity's missteps
#7https://nitter.net/OSSInsight/status/1703087927763542305
Which just links onwards to https://ossinsight.io/collections/game-engine with a screenshot: https://nitter.net/pic/orig/media%2FF6KVDQPb0AAi4Lj.jpg
If you click through to pull requests or issues created, the trend is between modest and potentially not statistically significant (there's also a lot of red digits).
The stars graph from godot is vertical since last month though, especially given that they already had the most stars by far (67k in August, compared to 43k for the runner-up pixijs) and an account has only one star to give so that's a lot of new interest.
Re: OSS Game Engines are increasing their stars on GitHub due to Unity's missteps
#8Im not well versed in game programming, however I have some knowledge on how to properly structure your software architecture in other domains. In regards to third party dependencies I agree with what Uncle Bob says, which is to keep them as far away from your stuff as possible. Only introduce a hard dependency if you have to. In my current project I have been doing that and I enjoy the flexibility that this gives me…
My very limited understanding (speaking only as a professional software developer but not a game developer) is that there’s very rarely an abstraction that’s common across multiple libraries in the same domain, or that, in order to make an abstraction that could be adapted to different libraries, you would have to give up a significant amount of performance.
Re: OSS Game Engines are increasing their stars on GitHub due to Unity's missteps
#9Im not well versed in game programming, however I have some knowledge on how to properly structure your software architecture in other domains. In regards to third party dependencies I agree with what Uncle Bob says, which is to keep them as far away from your stuff as possible. Only introduce a hard dependency if you have to. In my current project I have been doing that and I enjoy the flexibility that this gives me…
Yes, it is possible, but you need to use a game framework not a game engine.
Example of a game framework: http://www.monogame.net.
Still, if you don't map everything all the time, common value types will propagate through the codebase.
Re: OSS Game Engines are increasing their stars on GitHub due to Unity's missteps
#10Im not well versed in game programming, however I have some knowledge on how to properly structure your software architecture in other domains. In regards to third party dependencies I agree with what Uncle Bob says, which is to keep them as far away from your stuff as possible. Only introduce a hard dependency if you have to. In my current project I have been doing that and I enjoy the flexibility that this gives me…
Can you abstract away your website so it can run on node.js or angular?
Game development is typically very tightly linked to a mess of proprietary tools and products and platforms. It is the game engine itself that abstracts away for example) the payment/subscription api.
If you were to write your own game abstraction layer we would call what you did a game engine.
Secondly, performance (frames per second) is key in game software. Imagine if you wrote a lightweight abstraction layer for a physics/gravity engine. You’re effectively writing code to slow down your game FPS.
Thirdly, game development is often done by young beginner programmers, who often don’t even know programming yet. They get into game programming by following online YouTube tutorials in a specific game engine. If you know the importance of abstraction your already too high paid to work in a game development position :)