There's more than a couple situations where Swift forces you to repeat yourself. No default implementations for protocols and missing language features for deal

There's more than a couple situations where Swift forces you to repeat yourself. No default implementations for protocols and missing language features for dealing with enums would probably be more prominent examples than this narrow availability of default arguments problem. I'm not sure any one of these "work in progress" related issues are a reason to "hate Swift" (or at least, where Swift is going). It's more a reason to hate the current status of Swift as a project – since it will probably be a year or two before these sorts of non-critical issues bubble to the top of the Swift development team's priority list.