Not sure about the second game, but when you beat the first one it would tell you how to unlock hard mode. And if you beat that, it would tell you how to adjust your max health and starting lives so you could give yourself even more of a challenge.

But the DX version supported the Gameboy printer. How can you not love the Gameboy printer?!

In all seriousness though, the color dungeon and the tunics were fun additions.

I just looked it up since I didn’t know but the Game Gear version definitely looks different from the Gameboy one I remember.

https://youtu.be/45o2BgGZ9YA

It’s the one I owned, haha.

I never played any of the other Bomberman games (until Super Bomberman R) so I’m not sure how it compares.

Aside from a few classics I’m sure you’ve already played, I remember playing Wario Blast and Taz-Mania fairly often.

I haven’t played either one in years, so I don’t know how well they still hold up.

It makes more sense when you realize it’s based on code.golf submissions. No one is going to create a class like that for a code golf problem. They’re probably not going to create any classes (other than one just to hold the main function).

I’m pretty sure I can do the Fibonnaci one with less code than your simple class. Because these problems are simple enough they don’t benefit from any OOP stuff so you avoid most of the syntactic overhead.

I am surprised it’s not higher in the list since the overhead of setting up a main method is still quite significant compared to most languages. But other than that, these problems can be solved without running into any egregious examples of overhead.