I think that's the point the parody is making. A simple "piece" of code can have thousands of edge cases that a normal developer doesn't think about. That's the advantage of the UNIX-style "everything does one thing and does it well" philosophy that Node mirrors.
I think FizzBuzz is far more complex problem than this isThirteen. This FizzbuzzEE solution shows where Java truly shines: powerful dependency management, industry leading design patterns. My only wish is to add parallel streams, lambda and other latest Java 8 feature support.
This is a great example of why it is important to use modules. If I were to try implementing this myself, I might have thought to check for the Chinese string "十三", but I doubt I would have known to check for the uppercase version of the Chinese string "拾叄".
More seriously, does anyone know what "uppercase" means in Chinese? Do they literally have two (seemingly unrelated) forms for each of their characters?
Works fine for me (Firefox on Android and Windows)—I think your browser doesn't handle Unicode combining characters properly. (Chrome gets a little funky with them on Android, haven't used Windows Chrome in a while).
The reason is it's two codepoints but one "grapheme", and some software doesn't handle grapheme clusters well.
Uppercase is just a simple way to put it, but it's not exactly precise. Chinese has different numeral forms depending on the usage context. The more complex versions are also known as Financial.
Half the issues suggest the use of actual NPM modules, and I'm at a loss to tell which ones are jokes. For example: "Replace noop3 with noop4 (also keep an eye out for noop5)" https://github.com/jezen/is-thirteen/issues/151
I think it depends on the format, so cards have to handle the case of many players.
I think there are quite a number of many player formats actually.
Like, in one, some number of packs a cracked, and they are passed around in a circle, each person picking one card, until everyone has a deck, and then they play.
56 comments
[ 3.1 ms ] story [ 129 ms ] threadThen I looked at the unit tests. [1] Now my reaction is more like, "Your commitment to this bit is both admirable and slightly disturbing."
[1] https://github.com/jezen/is-thirteen/blob/master/test.js
This whole thing is hilarious.
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
https://github.com/jackdcrawford/five
More seriously, does anyone know what "uppercase" means in Chinese? Do they literally have two (seemingly unrelated) forms for each of their characters?
The Chinese characters are unicode strings.
The answer would be the same about an uppercase emoji.
I̶ ̶d̶o̶n̶'̶t̶ ̶k̶n̶o̶w̶ ̶w̶h̶y̶,̶ ̶b̶u̶t̶ ̶I̶'̶m̶ ̶h̶a̶r̶d̶l̶y̶ ̶a̶n̶ ̶e̶x̶p̶e̶r̶t̶ ̶i̶n̶ ̶C̶h̶i̶n̶e̶s̶e̶.̶ ̶T̶h̶e̶y̶'̶r̶e̶ ̶n̶o̶t̶ ̶u̶s̶e̶d̶ ̶m̶u̶c̶h̶.
EDIT: Nevermind me, see xiaq's much better comment.
I really hope using strikeout unicode does not catch on around here. It is horrible.
The reason is it's two codepoints but one "grapheme", and some software doesn't handle grapheme clusters well.
https://en.wikipedia.org/wiki/Chinese_numerals#Standard_numb...
Fellow House fan!
Added Klingon translation and and test for word "thirteen"
https://github.com/jezen/is-thirteen/commit/512813f
http://media.wizards.com/2016/aksdjciawolkcc0_soi/en_CMrxVcz...
I think there are quite a number of many player formats actually.
Like, in one, some number of packs a cracked, and they are passed around in a circle, each person picking one card, until everyone has a deck, and then they play.
Iirc. (Haven't played it myself.)
I think it would be better done with 11 though.
"Check if this one goes to..."