For the best experience on desktop, install the Chrome extension to track your reading on news.ycombinator.com
Hacker Newsnew | past | comments | ask | show | jobs | submit | history | hc5's commentsregister

> Most Go-ic? Maximally Go-ful? What's Go's equivalent to "Pythonic"?

Gophery



Goistic?


Choco Pie isn't like "chocolate pie" in the Western vernacular. It's a knock-off (of a knock-off) moon pie. [1]

> In the wake of World War II and the Korean War, the snack gained popularity in East Asia through its introduction by American GIs. Starting in 1958, a similar type of marshmallow filled cake was developed by Morinaga in Japan as 'Angel Pie'.

> Tongyang Confectionery began selling a similar product known as 'Orion Choco Pie' in 1974.

[1] http://en.wikipedia.org/wiki/Choco_Pie


thank you


Also, 680/880 is severely underserved by public transit. Every day it's bumper-to-bumper traffic from Walnut Creek->San Jose.

BART will eventually connect this, but you would still need to transfer in Oakland, which is roughly 20-30 minute detour. Walnut Creek -> Fremont currently takes over 1 hour on BART, to cover a distance of roughly 30 miles.


> People in Korea, who typically do have 3 names but who don't usually initialize them...

No, not really. This is a completely wrong interpretation of Korean names. Most of us have two names: family/clan name ("last" name like "Park", "Kim", etc) followed by given name ("first" name like "Chan-Ho" or "Geun-Hye"). The given name typically consists of two parts, but that doesn't mean we have three names.


I was always curious as to why nearly every Korean person I've met has "two" first names. According to Wikipedia [1], traditionally Korean names were "generation names", where everyone in a specific family of a specific generation shares part of the first name. The example they give of an equivalent Chinese name would be someone named Xia Zhou-jin might have a brother named Xia Zhou-sui, and children Xia Han-zheng and Xia Han-Li (in this case Xia is the family name, Zhou and Han are generation names, Jin, Sui, Zheng and Li are personal given names).

I'm curious - is this no longer the case, or do you (either you personally or, if you can speak to it, the zeitgeist in Korea) not think of the "generation" part of the "generation name" to be a separate name?

1. https://en.wikipedia.org/wiki/Korean_name#Given_names


The "generation" part is only part (one syllable) of the given name and doesn't constitute a separate name. The "yong" in my name is "generation name", but no Korean will call me "Yong" any more than an English speaker would call Richard "Chard".

Because most Korean names are neatly split into three characters (each character is a syllable in Korean), many people also write their names in three space-delimited words in Latin alphabet. And then westerners get confused and end up with patterns like "Gil D. Hong". (I'm not blaming them; you can't expect everyone to understand all the world's naming systems.)


Just to push back on this a bit, the fact that the "generation name" part of the name carries some additional semantic information in some ways makes it even more of a name than a "middle name" that is somewhat popular in the West. In a sense, my name is my full name (first, middle and last), but it is split into three parts. The last one has some meaning (it's a family name), the first two are given names, and the cultural default here is that I would go by my first name, and if a conflict is found, I'd go by the first + last, and if a conflict still exists, you'd default to first + middle name or first + middle initial. I don't think it's that unreasonable to consider generation names to be "compound names", consisting of two sub-names, even if the cultural default is to always use the full compound and not either of the parts.

I also think that "Richard"->Chard is a disingenuous choice, because people named Richard often go by Rich. People named Andrew very frequently go by either Andy or Drew, similarly people named Alexander often go by either Alex or Xander. Of course, there's no semantic meaning associated with the component parts of those names anyway, so it's not like you can infer something from the fact that someone is named Alfred and someone else is named Albert, and either one might go by "Al".


Well, OK maybe Richard was a poor example. What I'm saying is: some Richards go by Rich, but few goes by Chard, and certainly nobody interprets Richard as a combination of two name components "Ri + Chard" (or "Rich + Ard"). The probability a typical Korean would consider their given name as a combination of two parts is probably higher than that of Richards, but not much higher.

Maybe a better example is Anderson, which historically meant "Anders's son", but few living Andersons would consider "Anders" an acceptable way of writing their family name.


That's because it's really a combination of "Ric + Hard".

Seriously: https://en.wikipedia.org/wiki/Richard

:-)


FWIW, my parents didn't give me a generation name, and my kids don't have one. I have cousins and uncles (I think this is for males only? I could be wrong) who do have generation names. From what I understand, this practice is slowly dying out in favor of better sounding or more native-Korean names (without Chinese characters) in recent generations.


We're currently in PDT not PST.




Thanks! There is a corollary to this that would have prevented all this - when I went back in the Chrome settings and set the settings to the same order, it reset my header to this: "en-US,en;q=0.8,ko;q=0.6" - which makes things work for all sites again. I haven't touched my language settings since ~2012, so it's possible Chrome "fixed" this a while back, but didn't change my existing settings.


This is my guess as well - our app updated and Facebook connect works just fine.


EDT not EST


N+9.1: Non leap years will never contain a leap day.

http://support.microsoft.com/kb/214326


But that's a bug in Excel. "Non leap years will never contain a leap day" is true.


It was a bug in Lotus 1-2-3 that was intentionally implemented into Excel, so technically it was a backwards-compatibility "feature". And some items from the original list aren't exactly "truths" as much as implementations or configurations, e.g.

> 19. The system clock will never be set to a time that is in the distant past or the far future.

> 20. Time has no beginning and no end.


'items from the original list aren't exactly "truths" as much as implementations or configurations' QFT.


For now.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search:

HN For You