2) It's a programming language joke. MoleHillFactory (a Haskell example would be better, but I don't know it) wouldn't be able to return objects of type Mountain. Maybe it's not funny, but I kind of liked it:-)
2) It's a programming language joke. MoleHillFactory (a Haskell example would be better, but I don't know it) wouldn't be able to return objects of type Mountain. Maybe it's not funny, but I kind of liked it:-)
Your argument doesn't really sway me: I'm judging the program based on something real; you're judging it based on what must obviously be the case.
I don't completely write-off a YC-clone just because they put zero thought into the application form. But it does alter my impression.
I disagree with your static typing argument too. "Mountain out of a molehill" means making a bigger deal out of something than it is. Which means both things could be class Mound, just with different values. So in this case static typing wouldn't have saved the day ;-)