Hacker News Reader

I discovered LÖVE sometime around this february. We have a Game-making group at university, so I wanted to show them too. All went well until we looked at the libraries :/

View on HN

What was wrong with them?

Not the parent, but -- in my experience -- many libraries from the community were written by enthusiastic amateur developers. Finding ones I enjoyed using was very needle-in-a-haystack.

One recommendation: https://github.com/kikito

Along with that, a lot of the libraries (from what I could tell) put all the code in one massive file in a forum thread and update it from there, making it pretty time-consuming to keep up with changes.

That and there's no consistency between libraries as far as how they decide to use classes.

That and there's no consistency between libraries as far as how they decide to use classes.

This problem actually became so severe that there is now a "common interface" that libraries can use on each other's objects.

My solution to this was to not use any of them. The LÖVE APIs are pretty sane, so using your own tiny wrappers is not much work compared to dealing with the libraries.

first the names struck me(dirty mind). aside from that, the libraries that caught my attention were far from complete :/ (lure, it is)

Reply on news.ycombinator.com