I don't have looked into Flame too much, but I would say the main difference is that Flame builds on top of Flutter while right now Bullseye2D only builds on the web package.
Flame offers more out-of-the-box features, while with Bullseye2D you have to build many things yourself, but it doesn't force you into a predefined structure as much. The API is more prodcedural style, making it relatively quick to learen in its entirety, without too much "magic" happening under the hood.
I think for most people Flame would be the better choice (it is also been around longer, which means better support...), however, I really love extremly simple approaches. I also believe it has advantages when you tailor your systems and architecture to your own requirements. Lots of stuff in 2D Game Development is also extremly simple (so often having to deal with a complex physics module or rendering pipeline or entity component system is contraproductive).
Yes, maybe it's a stupid thing to say. My thought was that the simplicity of the API takes out a lot of the complexity of it compared to engines with complex structures, entity hierarchies, event systems and features that need to fit a wide range of genres. Especially if you want to make something simple or just a prototype.
Probably better to say "Writing games is simple again" or something then. Though engines like unity or unreal would make 3d games a lot simpler to make than this, so it's only some kinds of games
I ported this game from the Book "Code The Classics" which was written in Python/PyGame. It should be relativley easy to add mobile touch inputs to it, but I didn't have time for that yet.
You can just read the documentation and write code, there's really no need for AI here. Your argument sounds a bit like "What is a problem is that I cant enjoy my hourly whisky while driving". Maybe the problem isn't the platform :)
This is not only an Apple problem. Most software developed today is in a terrible state. What boggles me the most is that how users are immune against it - it's so normal that software doesn't work or has bugs that most users don't even get upset - it's just the way it is. It's software - what can you do? :(
Yes, that's right. But social media platforms always tend to have something new on it each time you check them, which creates a strong incentive to check them even more often. News sites, for example, on the other hand, don’t use algorithms that encourage doom scrolling and keep you engaged far longer than you intended.
It’s not clear, yes: I think they have way too much power in the wrong hands. Now, hypothetically speaking: If they were to lose most of their users, they would lose their power. So, in one way or another, everyone supporting those platforms (by using them) is part of the problem - and that would be the reason to stop using them (again, I know this is quite hypothetically).
Yes but again, this is about stopping to USE them. Deleting your account versus not using your account at all doesn't have any difference of outcome here.
Flame offers more out-of-the-box features, while with Bullseye2D you have to build many things yourself, but it doesn't force you into a predefined structure as much. The API is more prodcedural style, making it relatively quick to learen in its entirety, without too much "magic" happening under the hood.
I think for most people Flame would be the better choice (it is also been around longer, which means better support...), however, I really love extremly simple approaches. I also believe it has advantages when you tailor your systems and architecture to your own requirements. Lots of stuff in 2D Game Development is also extremly simple (so often having to deal with a complex physics module or rendering pipeline or entity component system is contraproductive).