I also imagine I'd use a bowling alley in my car ~2 times per year, tops. So that seems like a better analogy to me.
edit: I guess I should bring up that I don't use go's switch statement much either, and when I do, 99% of the time I'm using the naked switch as more of an analog to lisp's cond clause.
Re: custom UnmarshalJson implementation - you still have to remember, and do it for every serialized format (e.g. sql).
A default case in a switch only solves, well, switching. If a rogue value comes in, it will go out somewhere. E.g. json to sql or whatever things are moving.
I mean, yeah, but eventually you have to do something with it. And the only useful thing you can really do with an enum is switch on it...
The point the others are making is you are using a less safe type of programming equivalent to driving without ABS and TC.
From your point of view, "TC and ABS is useful so I use it unlike enums".
From their point of view though, you are the person not using ABS and TC insisting that they offer nothing useful.
Can you explain how owning a car without ABS and not driving it is less safe?
Edit: Wait, or am I not using breaks? I think the analogy changed slightly during this whole process.
I don't know that it is, I'm speaking based on the implication in this thread that no-enum and no-ABS people are overconfident to a fault.
I do believe that those who claim they don't need enums, static typing, etc are probably overconfident and have a strong desire or need to feel more control.
I'm not sure though, at least for GC'd languages, how enums sacrifice control.