The biggest hurdle on that is the question "How do I move the discomfort to the side of pleasure?".

Not necessarily. Quoting Greg Lemond on training: "It never gets any easier, you just get faster". Constantly pushing yourself into discomfort is the only way to improve and maintain the highest level of performance. Once you think you've "made it" and stop pushing your boundaries, you're already well into decline.

How do you realize that one is building the wrong thing?

Not OP, but asking yourself who would use what you are building, and then checking whether they will use what you build is a good start. Of course, the "checking" part is hard, even with a lot of methodology.

As with almost everything. Moderate use is key.

Moderate use of what ?

Edit: https://en.wikipedia.org/wiki/Thought-terminating_clich%C3%A...

Sex, presumably. How parent thinks people should determine when to have sex or not, dunno.

>> "but you open-sourced it, surely you must know that people will then put it in their commercial code?"

this is a general problem in open source. And with obfusication in an AI it is just unfair. If AI / codepilot would reference the source in a nice way, then I woundn't mind.

Especially given the history of the last 30 years where major open source licenses carefully fought over just how much "commercial code" could use the works involved.

So I can just, slap this onto my AI generated art?

Hey, why does it matter if it's made in 'common lisp' ?

I'd say that to the end-user it doesn't matter (which is why it's not mentioned on the linked store page), but to the HN crowd it's interesting because lisp is a nifty hacker topic and seeing someone manage to write a game in it is pretty cool.

(It's probably more interesting than all the "X, a clone of Y but in Rust" posts, at least.)

Common Lisp is pretty cool, and to my knowledge this is the first major game title using it that is actually released.

Maybe not common lisp, but look up crash bandicoot by naughty dog software for the playstation.

That was an exclusive playstation title, probably the third biggest title in terms of sales on the playstation, and it was written in Lisp.

I have a private conspiracy theory that one of the reasons for the recent remaster of The Last of Us is to move all of Naughty Dog's go-forward IP off a Lisp-based workflow. Through at least The Last of Us (2013), ND had been still sneaking in Lisp through the back door: while the engine was in C++, a toolchain in Racket would generate all the entity component types as well as data for various animations, etc. I think there's been a shift in developer talent at ND in the past few years, and Druckmann wants to get rid of all the Racket stuff (because it's hard to find maintainers for it) and stick with a standard C++ workflow.

All of which makes Kandria even more refreshingly welcome.

To my knowledge, Naughty Dog have never fully implemented a game in a Lisp. They used it and custom languages written in Racket as scripting and automation tools.

The game posted here appears to be written in Common Lisp from the engine up.

Though all their games written in GOOL or GOAL had their development environments implemented in Common Lisp.

The first few Jak & Daxter games were written from the ground up in GOAL.

Yeah I know about GOAL and OpenGOAL and all that.

This is an unnecessarily cynical comment, IMO. The title already establishes the value prop of the project as a "Show" entry; it's an action RPG, i.e. game. It's not "I made a clone of a C tool but in Rust" where there is no actual value prop.

It's a bonus that it's written in something a bit more interesting than your average game.