sidereal life is rubbish
... though with the late professor's cremation, I welcome his more speedy becoming of part of us all.
2662 publicly visible posts • joined 8 Nov 2007
He is all-knowing and all-powerful.
He can't go anywhere since He is already everywhere.
He can't do anything since the act of doing presupposes
opposition.
His universe is irrevocably thermodynamic having no
friction by definition. So, He has to create friction:
War, Fear, Sickness, Death,
To keep his dying show on the road.
Sooner or later, "Look boss we don't have enough energy
left to fry an elderly woman in a flea bag hotel bar."
"Well, we'll have to start faking it."
Joe looks after him sourly and mixes a bicarbonated
soda. "Sure, start faking it. Sure, and leave the
details to Joe."
Thanks, but I did mention needing to use binmode (the use utf8 was only there so I could use a bareword 私 as a hash key)... and yes, I have come across times when I've had to turn UTF8 upgrading off locally on stderr/stdout after turning it on globally. Mainly because some libs or functions don't properly set the utf8 flag on returned data, so going back to raw output is often quicker/easier than messing around with utf8 internals that correctly set the utf8 flag on variables that have been affected. Especially if all you want to do is just add a quick print/warn for debugging a section of code.
Anyway, thanks for the clarification, but I've been there, believe me :)
> I started to learn perl - from books - and it was the worst experience ever.
I started learning it as a substitute for awk and various horrible shell variants. It was a great replacement for awk because it did everything that did, but with more power. It was better than shells because it had all the features a proper programming language has (eg, associative arrays) and had a single, fairly logical way of doing string interpolation (the worst part of all shells, which all decided on slightly different ways to handle the problem). Oh, and it's obviously much quicker to write in Perl than something like C.
For people who come at Perl from the same direction I did, it was a brilliant language. I guess that people who came to it later, and who aren't building on previous awk/sed/*sh experience, it can be kind of hard to understand the power (and even simplicity) that Perl delivered.
First I've heard of it. I write a lot of code that uses utf8 and then has to binmode stderr and stdout to avoid "wide character" warnings when printing utf8 strings. It seems that common::sense solves the latter problem
$ perl -le 'use common::sense; my $a = { 私 => "あなた"}; print $a->{"私"};'
あなた
$ perl -le 'use utf8; my $a = { 私 => "あな た"}; print $a->{"私"};'
Wide character in print at -e line 1.
あなた
Now if only I didn't have to open files with 'open FILE, "<:encoding(UTF-8)", $fn' every time ...
In memory of Fats Domino"
to talk about how programmers actually code up the selection of a random combination or permutation. You need something like a Fisher-Yates shuffle (using lists) or Floyd's algorithm (using sets) to ensure that the results aren't biased in some way.
It's all to easy to come up with a naive algorithm for, eg, dealing a hand from a deck of cards that seems to work but favours picking certain hands over others.
Yup. Well, C1 and XU4. The C1/C2 have gbit Ethernet and are faster than the Pi boards. You can also fit emmc (from the same supplier) for faster onboard storage. USB2, like Pi.
XU4 with "cloudshell" case is very nice. Uses one of the USB3 ports for a SATA bridge so you can put in a laptop drive. The other USB3 is accessible for other uses. The whole thing makes a nice small-form NAS. It's also got a small LCD screen (CGA res) integrated in the case so it can be used as a (tiny) terminal in a pinch, or most likely you'll want to use it for status messages. It has an IR sensor, so you could use remote to turn on the screen and control the box without a keyboard. Also has Gbit Ethernet.
Horses for courses, I reckon. Pi is cheap and cheerful, but C2 gets you more bang per buck, benchmark-wise. The more expensive Odroid boards are just more grown up with more RAM and faster I/O interconnects. Better for more serious projects/roles.
Bear with me on this...
http://gwydir.demon.co.uk/jo/solid/buckynet.gif
Remove those pentagons from the template and sew it up around a spherical ball. Granted, the holes will be pentagonal and the ball itself prone to bursting due to the inner bladder being exposed, but still...
I had to read to the middle of the article before I read "I know it when I see it."
Unfortunately, the Pai approach is "I'll see [to] it when I believe it", with cash and political capital being a powerful reason to believe almost anything, even before breakfast.
SMS did (still does?) have a 140-byte limit because it was piggy-backing on an existing control channel. The standard didn't include UTF-8 support so what happened was that if you used any Unicode char, a flag was set and all the message was sent as UTF-16, thus losing half the space or being twice as expensive.
Twitter has always, AFAIK, supported UTF (I guess UTF-8). The 140-char thing counts actual characters, not bytes.
I think you just have to be a bit more flexible in understanding what was intended by "double the amount of information in one character". In fact, as you point out, the shortest translation of あほ would be "fool", which has twice as many characters in English. That's the sense that's intended.
The CJK languages don't use spaces and many words are only 1 or 2 characters long.
(382 characters)
文字に就き情報の二倍と言う事を掴むため、余裕がもっと必要だと思うけど。実は、君の言う通り「あほ」の一番短い英訳が「fool」に成って、長さは日本語より二倍です。そんな解釈が出る。
日中韓は、間隔も無いし、単語の長さとして、1~2字も多いです。
(122字)
Not quite 2:1, but you can see the point.