I'm going to quote myself from a blog post I wrote back in 2012:
> Nethack is incredibly difficult, and near impossible to win without some knowledge. Whilst it could be argued that one could attain this knowledge through trial and error, it would take many many playthroughs to make any headway, even if you played in the invincible “Wizard” mode. Whilst I would recommend the use of spoilers if you wish to make progress in the game and discover what it has to offer, I wouldn’t suggest reading up on absolutely everything to give yourself an advantage. My general rule of thumb was to look something up when I came across it. I still found the game incredibly challenging, as I was placed in situations that I couldn’t predict or prepare for, and I still had that thrill of discovery and amazement.
> My general rule of thumb was to look something up when I came across it.
That is good advice. Nethack “spoilers” are more like being let in on an “in-joke” than being told the solution to a puzzle or the ending of an M. Night Shyamalan movie.
Reminds me of this blog post where someone was trying to reverse-engineer a hand-rolled encryption protocol in a crossword app by colorizing the output and looking for patterns.
It’s not just about money. It’s complexity, company size, management, etc.. Loss of focus by having to build a new app from ground up. Features and improvements take longer as they have to be done twice. Parity problems. Support debt. Maintaining multiple versions of the same app isn’t just “hire more”.
As you agreed with, they are successful. Maybe they’re happy with that.
I'm sure they can afford that, but would that end up paying for itself? Would that end up bringing in enough new paying users to justify spending all that money on a team of Android engineers?
They probably haven't done it because it doesn't make sense for them financially.
reply