| Yeah, it's beautiful if 1) you think mutable variables are beautiful 2) you think stuffing everything into one file is beautiful 3) you think defining functions at the root namespace is beautiful 4) you think consecutive repeated property accesses stuffed into a consecutively repeating boolean check like this are beautiful: if h.Time == "0" || h.Time == "100" || h.Time == "200" || h.Time == "300" || h.Time == "400" || h.Time == "500" || h.Time == "600" || h.Time == "700" || h.Time == "1400" || h.Time == "1500" || h.Time == "1600" || h.Time == "2300" 5) if you think embedding ANSI color codes across all strings instead of centralizing all that ugliness somewhere is beautiful 6) if you think not separating your command-line-handling code from your problem-modeling code is beautiful (see: Hexagonal Architecture http://alistair.cockburn.us/Hexagonal+architecture) 7) If you think having no fucking test suite to speak of, given all that mangled mutating code is beautiful (to me this is the MOST egregious non-beautiful thing in the entire "project") Then, yes. WeGo is beautiful. Frankly I'm shocked that what people call "beautiful" can differ that fucking much. |