LÖVE

I think that given the current LOVE community, the number of developers that would actually both have a game grand enough to benefit from a relational database and then also decide to use it would be extremely small. I like to think LOVE follows the same basic philosophy that Lua does, only adding features when it has an obvious and overwhelming benefit.

MarekkPie wrote:I think that given the current LOVE community, the number of developers that would actually both have a game grand enough to benefit from a relational database and then also decide to use it would be extremely small. I like to think LOVE follows the same basic philosophy that Lua does, only adding features when it has an obvious and overwhelming benefit.

This. Also who the hell puts game data in an SQL database!? I can't name a single example. It is highly unusual and overly complex. What's next, defining everything in some verbose yet unreadable XML format which is then stored in a SQL database and FactoryFactoryFactoryFactoryFactory methods i.e. going full Enterprise Java. Please don't.

Hexenhammer wrote:

MarekkPie wrote:I think that given the current LOVE community, the number of developers that would actually both have a game grand enough to benefit from a relational database and then also decide to use it would be extremely small. I like to think LOVE follows the same basic philosophy that Lua does, only adding features when it has an obvious and overwhelming benefit.

This. Also who the hell puts game data in an SQL database!? I can't name a single example. It is highly unusual and overly complex. What's next, defining everything in some verbose yet unreadable XML format which is then stored in a SQL database and FactoryFactoryFactoryFactoryFactory methods i.e. going full Enterprise Java. Please don't.

But DUDE! Just throw in an IoC Container!

Hexenhammer wrote:Also who the hell puts game data in an SQL database!?

Hex, even if you feel very strongly about the issue it's probably best not to deride anyone's choices. Doesn't create the right atmosphere.

Can the OP explain the specific use cases in more detail? I'm pretty interested in the issues you're facing.

PS: Sometimes Dependency Injection is just what you need.

I think Hex's point is that there is not much (or any?) precedent in using an SQL database to store clientside game data in games created by professionals - and if there is, it's probably a pretty niche use case. I've personally found it very helpful to look at what professionals are and are not doing, and try to understand why they made those choices.

Currently, it's possible to use libraries such as lsqlite in LÖVE via require - albeit with some file location limitations for the shared library.

Learning from pro's is useful, I agree 100%. I was just suggesting that Hex could have delivered the message with less sarcasm and derision.
My worry is that threads like this go two ways (1) the original poster gets offended and stops contributing (2) it devolves into a flamewar. Other than that, I can't wait to hear how the pros are doing it.

daviddoran wrote:I was just suggesting that Hex could have delivered the message with less sarcasm and derision.

Certainly. I admit I was a little rude there but the idea was just.. well let's just say I really don't follow the logic.

SQLite and other relational databases are used by a TON of developers, you guys are dead wrong. From games like Garry's Mod to every single MMO on the planet.


SQLite is extremely useful, and widely used within not only the gaming industry but the tech industry overall. It's also light and fast (probably faster than whatever shitty serialization technique you're using right now).

MattRB wrote:SQLite and other relational databases are used by a TON of developers, you guys are dead wrong. From games like Garry's Mod to every single MMO on the planet.


SQLite is extremely useful, and widely used within not only the gaming industry but the tech industry overall. It's also light and fast (probably faster than whatever shitty serialization technique you're using right now).

SQL is used a lot in server-side programs, but I think the discussion here is about adding it to LÖVE in general - it's already pretty trivial to use lsqlite together with Lua or LÖVE in a server, so I can't see why it should be included in LÖVE by default just for that.

One minor nitpick:

possibility to save game states, without worrying about file location and/or OS issues (like different paths)

In LÖVE, you shouldn't have that worry anyway. If you do, you're doing something terribly wrong.

Anyway, on this issue I wobble a bit back and forth between "LÖVE doesn't need an extra dependency that's going to be largely unused" and "Adding SQLite would give such POWA".