Dave, others:
This is a collection of notes, lightly edited, compiled over the last
two days, so the voice and time line move around a bit. Apologies.
OK, first impressions:
1. The earthquake was by far the biggest I've ever been in (or hope to
be in), but the building we are in is brand new and very well built,
so it swayed a lot but never felt dangerous.
2. Being a refugee is both stressful and boring at the same time, even
when you're with friends in a place you know is safe. The biggest
thing, of course, is the lack of reliable information; several
people around me have 1seg keitai which give a *very* poor TV image,
enough to be scary but not provide a lot of detail.
Observations:
1. It's a rule of mine not to leave the house without clothing warm
enough for the possiblity of being stuck outside for hours; I think
I'll keep that rule.
2. I carry millions of transistors in my pocket, billions in my
backpack. One would be enough for an AM radio, but no one around me
seemed to have one.
Rolling back to 14:45 Friday...
"Earthquake," I said quietly. Nobody noticed, Kei-san kept on
talking. Even I wasn't completely sure at first, and I'm pretty quick
to pick up on them.
"Earthquake, we're having an earthquake," I said, a little louder.
Kei-san said, "Earthquake?...You're right..."
Osamu-san said, "Earthquake? Really?"
By this time, it had already been swaying for several seconds.
"It's getting bigger," someone said.
Kusumoto-san got up and walked across the room and peeked through the
blinds. "Electric poles are swaying," he said. I got up and walked
across the room to join him.
"It's getting even worse," someone said. "Better get away from the
windows."
"Wow, it's big...this is far away and big..."
Comments like that continued for what seemed like two minutes, before
it calmed down. The electricity went out.
Shortly, the announcement came to evacuate the building, so we grabbed
our jackets and went out. Several of us helped a man in an electric
wheelchair, lifting him down the stairs.
This building includes a gym and pool; dozens of kids in speedos and
googles were forced out into the cold. I handed out a shirt and
fleece I was carrying (which haven't come back, but if that's my
biggest loss, I'm fine).
While we were outside, I got email on my cell phone (DoCoMo mail)
from my wife, letting me know that she was okay, had one of our
daughters, and was getting the other. It would be fifteen hours
before we would be able to connect via voice or SMS, but DoCoMo mail
and their 3G packet service operated sporadically from the beginning.
I was able to access Gmail, Facebook and Twitter, enough to get a
message to friends who relayed it to my parents.
Eventually, they announced that they would inspect the building top to
bottom, starting on the 7th floor, before we were allowed back in the
building. A few minutes later, it started to rain, and a stream of
people went back into the building -- with permission or without, I
don't know.
With power out, we had some emergency lights; our local blackout
continued until 11pm, eight hours after the first shock (but when it
got dark, we could tell that surrounding areas still had power). We
grabbed our stuff, and were herded into a few rooms on the lower
floors, where sat on classroom chairs or stretched out on the floor.
Decks of cards and various drinks, including Dad's Root Beer (which
some student literally mistook for a type of beer -- to her disgust
and my delight) and some sort of avowedly foul Korean liquor, and
snacks materialized, and the students and younger folks quickly
settled into a social mood. I'm fighting either allergies or a bit of
a cold, so I stretched out on the floor to rest.
About a half a dozen faculty were in the early part of an overnight
retreat, here on Keio's Hiyoshi Campus rather than at SFC, so I had
extra shirts and some bread and cheese on hand.
Most of the other faculty that I came with have gone home to check on
their own families, moving via car, but none were going in my
direction, so I elected to stay here. Some of the faculty and staff
and a fair number of students from this campus remain; some live close
enough to walk, but have no power or simply prefer to be with friends
here.
Fighting a cold and stress, and with nothing but emergency lights,
didn't feel like reading. Little information coming in; we were safe,
with nothing particular to do. No one around needed immediate help,
and simply adding people to the streets and stations was clearly a bad
idea. I now understand the empty look on the faces you see in refugee
camps.
Eventually, the campus security and general affairs folks came around
and handed out canned water, crackers, and rather musty blankets.
Some people had keitai (cell phones) with one-seg (1seg) receivers,
very low-bandwidth digital TV. The images we could see were
appalling, with fires burning across broad areas, in the dark.
About 10pm, the Toyoko Line reopened to Shibuya, and people began
filtering out. I stuck with my resolution to stay put until morning,
or JR began running again. (I later heard that some faculty took more
than ten hours to get home; those of us who stayed warm, fed and
comfortable certainly didn't regret that decision the next morning.)
Overnight there were a number of aftershocks, and the second major
quake in Nagano, which they asserted was not related.
I was beside myself with worry about the possibility of tsunami coming
to Kamakura. Our house sits 800 meters from the beach. A couple of
years ago, they handed out a community disaster handbook that included
a tsunami map, which suggested that 7m is a high enough altitude.
Friday's events clearly show that to be false. Our house sits right
on the isoline at 7m, but clearly would have been swept away.
The lights came back on at 11pm. About 1am, I laid down to sleep for
a while; when I woke up at 2:30, many of the students had gone.
More earthquakes, more worries, watching NHK on a big projector screen
until 430am, then slept until 6.
When they announced the reopening of some of the JR lines at 700, I
left. Getting to Yokohama was easy, from there was slow as they kept
trains running at 35km/hr and stopping at every intersection. The
platforms and trains were crowded, but not intolerably so.
From Kamakura Station, it's a ten-minute walk home. I detoured
through the area I think my family should use as an escape route in
the event of a tsunami. The official map recommends that we make our
way to one of the nearby junior high schools, on higher ground, but
their recommended route passes through a stretch of very low ground
several hundred meters long, and crosses the river. I'm revising ours
to what I think is a less-exposed route, though we have to cross a
branch of the river somewhere and there's still one low stretch in
it.
That takes us up to the start of the nuclear reactor concerns, which
will have to be a separate post. I'm struggling with the technical
explanations in Japanese, anyway, so those reading the
English-language press may be better informed.
Over time, as the information flow peaks, my posts will probably lack
originality and insight, but I hope this gives you some idea of what
it's like here on the ground, for a typical family in the Kanto area,
well away from the most seriously hit areas.
Will mine my FB posts and tweets for further material at some point.
Comments and reassurances always welcome; if I seem abrupt via email,
it's just trying to handle the flood of check-in emails from both
people here locally and those from outside asking about us.
We *definitely* appreciate the concerns! Keep us in mind not just
today but over the coming months; recovery here is going to take time.
Sunday, March 13, 2011
Wednesday, April 07, 2010
New Paper Dance
Austin G. Fowler, David S. Wang, Thaddeus D. Ladd, Rodney Van Meter, and Lloyd C. Hollenberg,
Surface code quantum communication, arXiv:0910.4074 [quant-ph], accepted to Phys. Rev. Letters! Congrats to Austin and the rest of the team. We are gradually illuminating some of the possible corners in the space of quantum repeater system design.
Surface code quantum communication, arXiv:0910.4074 [quant-ph], accepted to Phys. Rev. Letters! Congrats to Austin and the rest of the team. We are gradually illuminating some of the possible corners in the space of quantum repeater system design.
Friday, April 02, 2010
The New GIGA Program at SFC
The web site for Keio's new undergraduate program, Global Information and Communication Technology and Governance Academic Program (GIGA), is now up and running.
Starting in fall 2011, we'll be accepting freshmen into GIGA to study networking, novel computing systems, international relations, and all of the other fun things we do (including computer architecture and quantum computing, two of the things I teach), with the language of instruction to be English.
Starting in fall 2011, we'll be accepting freshmen into GIGA to study networking, novel computing systems, international relations, and all of the other fun things we do (including computer architecture and quantum computing, two of the things I teach), with the language of instruction to be English.
Thursday, April 01, 2010
Friday, January 08, 2010
New Factoring Record
New factoring record: 768 bits, about 1500 CPU-years on 2.2GHz AMD CPUs, 10^20 operations, 2^67 instructions (for some definition of "operation" and "instruction". Claims a 1024-bit number would only be about 1,000 times as hard.
Brought to you by Kleinjung, Aoki, Franke, Lenstra, Thome', Bos, Gaudry, Kruppa, Montgomery, Osvik, te Riele, Timofeev, and Zimmerman.
http://bit.ly/8xXSgy
Just FYI.
Brought to you by Kleinjung, Aoki, Franke, Lenstra, Thome', Bos, Gaudry, Kruppa, Montgomery, Osvik, te Riele, Timofeev, and Zimmerman.
http://bit.ly/8xXSgy
Just FYI.
Thursday, December 17, 2009
Lecture on Systems for Distributed Quantum Computing
Systems for Distributed Quantum Computing on Keio's YouTube Channel, where you will find other videos from the Spintronics group at Keio, as well.
Introduction of my research, targeted at physicists, primarily at a qualitative level, no equations but no stopping to explain vocabulary.
Introduction of my research, targeted at physicists, primarily at a qualitative level, no equations but no stopping to explain vocabulary.
Thursday, October 15, 2009
IJQI Acceptance
Our paper Distributed Quantum Computation Architecture Using Semiconductor Nanophotonics has been accepted for the International Journal of Quantum Information special issue on Distributed Quantum Computation. Huzzah!
This paper was very collaboratively written, thanks to Skype. Thaddeus and Austin both deserve full measures of credit for this one. Thanks, guys!
This paper was very collaboratively written, thanks to Skype. Thaddeus and Austin both deserve full measures of credit for this one. Thanks, guys!
Wednesday, July 29, 2009
Help Me With My Summer Reading
I'm feeling the need to recharge my store of ideas, and I have the
nagging feeling that my lack of currency in a bunch of fields is
causing me to miss some connections I could use in my own research.
So, I'm looking for a reading list of, say, the one hundred most
important papers of the decade. It doesn't have to be an even
hundred, but I'm looking for a good summer's reading. (Given that
it's mid-2009, now would be a good time to start composing such a list
anyway, depending on where you want to place the "decade" boundary.)
I want these papers to cover *ALL* fields of computer science and
engineering; I am by nature catholic in my reading.
You probably know that my current field is quantum computing, but prior to
that I did network-attached storage. The 1990s were a very creative,
ambitious decade in that area; I admit I read much less there now than
I used to, but I haven't seen anything really earthshaking in storage
in the last few years. (Friends still in the area will no doubt
correct me.)
If such a list already exists, I'm happy to use it as-is, otherwise
I'm willing to manage a conversation and create such a list.
Since this list will be very broad, I want only a few "MUST READ"
papers in each field. What are the new ideas in your field? If you
had a short meeting with, say, an NSF god descended from Olympus, what
ideas would you cite to convince him/her that your *field* (not your
pet idea) is a vibrant field with real-world impact, worthy of
large-scale support? What papers or ideas have changed the way you
think?
So, if your field is:
Theory:
* complexity theory
* algorithms
* data structures
* automata/Turing machines/FSMs, etc.
Systems:
* hardware technology (Moore's Law, etc.)
* processor architecture
* systems architecture
* operating systems
* storage systems
Programming languages
Software engineering
Networking
Artificial Intelligence
Search
Databases
Security
Human-computer interaction
Network or systems operations
Ubiquitous systems/sensor networks
Computer Science education (please help me learn to teach!)
etc.
please send me your suggestions.
I'm even willing to go as far afield as robotics and bioinformatics,
if you can convince me it's worth my time to go read. I'm also
willing to accept old ideas that are finding new urgency;
transactional memory would be a good example, virtualization another.
I will leave it to you to balance newness of idea with real-world
impact, and to decide whether to recommend the key original paper(s)
or a survey paper, if one exists already.
(I'm doing this a tad ad hoc; I really should reconcile against, say,
the ACM computing curricula or a journal keyword list, but I probably
won't bother. Some may also object to the categorizations above;
don't worry about it, just send me the papers/ideas you think are
critical, and we will work on the categorization and balance of the
list later.)
(Yes, the choice to limit this to the last decade is arbitrary; there
are plenty of old ideas I'm not familiar with, too -- I recently ran
across R-trees for the first time, for example -- but, generally
speaking, I'm after ideas too new to have made it into textbooks,
otherwise I'd just pick up a recent text.)
(And on these grounds let me say that I'm enjoying the revitalized
CACM, which seems to be helpful in focusing on new, important ideas,
with more timely and accessible review articles than Computing
Surveys.)
A few thoughts to get started:
* The hierarchy of limits in computing technology:
An outstanding synthesis of Moore's Law, Landauer's principle, etc.
Dense, but well-written and worth the effort to understand. I don't
care if the ideas are old, this one is critical.
@Article{meindl01:_terascale-si,
author = {James D. Meindl and Qiang Chen and Jeffrey A. Davis},
title = {Limits on Silicon Nanoelectronics for Terascale
Integration},
journal = {Science},
year = 2001,
volume = 293,
pages = {2044--2049}
}
* proper network topology analysis:
A clear-eyed look at mathematical analysis of and understanding of the
Internet.
@article{JohnCDoyle10112005,
author = {Doyle, John C. and Alderson, David L. and Li, Lun and Low, Steven and Roughan, Matthew and Shalunov, Stanislav and Tanaka, Reiko and Willinger, Walter},
title = {{The "robust yet fragile" nature of the Internet}},
journal = {Proceedings of the National Academy of Sciences},
volume = {102},
number = {41},
pages = {14497-14502},
doi = {10.1073/pnas.0501426102},
year = {2005}
}
* distributed hash tables (DHTs):
Just barely makes my "decade" cutoff, but one of the most influential
ideas of recent years; fault-tolerant, truly distributed,
loosely-coherent key-value pairs, useful for managing e.g. a lookup
system for P2P networks. (You can argue for another choice of
paper.)
@inproceedings{stoica2001chord,
title={{Chord: A scalable peer-to-peer lookup service for internet applications}},
author={Stoica, I. and Morris, R. and Karger, D. and Kaashoek, M.F. and Balakrishnan, H.},
booktitle={Proceedings of the 2001 conference on Applications, technologies, architectures, and protocols for computer communications},
pages={149--160},
year={2001},
organization={ACM New York, NY, USA}
}
* Peer-to-peer (P2P) networks:
No recommended paper here yet. I've read a few, but none really stand
out in my mind. Suggestions?
* Delay-tolerant networks (DTNs):
No recommended paper here yet. Might not make the decade cutoff.
* Network coding:
Just barely makes the decade cutoff. This is the seminal paper,
AFAIK, but the writing in it is poor; recommendations for an easier
read gladly accepted. A highly theoretical idea that seems to be
gaining surprising traction in real-world systems.
@article{ahlswede2000nif,
title={Network information flow},
author={Ahlswede, R. and Cai, N. and Li, S.Y.R. and Yeung, R.W.},
journal={Information Theory, IEEE Transactions on},
volume={46},
number={4},
pages={1204--1216},
year={2000}
}
* Ajax:
I haven't seen any good papers on it, and it's a philosophy rather
than a technology, but surely it's important enough to rate
here...suggestions?
* Transactional memory:
One possible route to effective parallel programming. The right one?
Good question!
@Article{larus07:_trans_mem,
author = {James Larus and Christos Kozyrakis},
title = {Transactional Memory},
journal = cacm,
year = 2008,
volume = 51,
number = 7,
pages = {80--89},
doi = {10.1145/1364782.1364800}
}
* MapReduce:
One of a set of very good ideas to come out of Google in the last few
years. The right way to get to real parallel programming on very
large datasets? Good question! The database community seems to think
not. But having done a little MPI programming, I can assure you that
MPI is not for the masses, at least not in its current form.
@article{dean:mapreduce-cacm,
author = {Jeffrey Dean and Sanjay Ghemawat},
title = {{MapReduce}: simplified data processing on large clusters},
journal = {Commun. ACM},
volume = {51},
number = {1},
year = {2008},
issn = {0001-0782},
pages = {107--113},
doi = {http://doi.acm.org/10.1145/1327452.1327492},
publisher = {ACM},
address = {New York, NY, USA},
}
* Rethink the Sync:
Recommended by a friend, who called it his favorite paper of the
decade.
@inproceedings{nightingale2006rethink,
title={Rethink the sync},
author={Nightingale, E.B. and Veeraraghavan, K. and Chen, P.M. and Flinn, J.},
booktitle={Proceedings of the 7th symposium on Operating systems design and implementation},
pages={1--14},
year={2006},
comment ={Best paper; Honey's favorite paper of the last decade.}
}
* Disk MTTF:
An analysis rather than idea paper, but important for anyone who does
large-scale systems or cares when their laptop disk is likely to
fail.
@article{schroeder2007dfr,
title={{Disk failures in the real world: What does an MTTF of 1,000,000 hours mean to you}},
author={Schroeder, B. and Gibson, G.A.},
journal={Proceedings of the 5th USENIX Conference on File and Storage Technologies (FAST)},
year={2007}
}
That's eight papers on eleven ideas that have changed the way I think
about computing systems in the last few years, mostly in the
networking area (a couple may have to get deleted to hold the final
list to 100 papers). There are many other topics, of course (chip
multiprocessors and radical new architectures such as TRIPS;
hypervisors and virtualization of systems and networks is another
old/new idea), but I'll leave them to others to promote. I've read
hundreds of papers in the last decade, but I'm interested in what
*you* consider important, not my own biases here. And while IP is a
heavily network-oriented list and will no doubt expand on that set of
ideas above, please look as far abroad as you comfortably can -- or
forward on to colleagues in other areas who might be interested in
such a list.
Please help educate me!
nagging feeling that my lack of currency in a bunch of fields is
causing me to miss some connections I could use in my own research.
So, I'm looking for a reading list of, say, the one hundred most
important papers of the decade. It doesn't have to be an even
hundred, but I'm looking for a good summer's reading. (Given that
it's mid-2009, now would be a good time to start composing such a list
anyway, depending on where you want to place the "decade" boundary.)
I want these papers to cover *ALL* fields of computer science and
engineering; I am by nature catholic in my reading.
You probably know that my current field is quantum computing, but prior to
that I did network-attached storage. The 1990s were a very creative,
ambitious decade in that area; I admit I read much less there now than
I used to, but I haven't seen anything really earthshaking in storage
in the last few years. (Friends still in the area will no doubt
correct me.)
If such a list already exists, I'm happy to use it as-is, otherwise
I'm willing to manage a conversation and create such a list.
Since this list will be very broad, I want only a few "MUST READ"
papers in each field. What are the new ideas in your field? If you
had a short meeting with, say, an NSF god descended from Olympus, what
ideas would you cite to convince him/her that your *field* (not your
pet idea) is a vibrant field with real-world impact, worthy of
large-scale support? What papers or ideas have changed the way you
think?
So, if your field is:
Theory:
* complexity theory
* algorithms
* data structures
* automata/Turing machines/FSMs, etc.
Systems:
* hardware technology (Moore's Law, etc.)
* processor architecture
* systems architecture
* operating systems
* storage systems
Programming languages
Software engineering
Networking
Artificial Intelligence
Search
Databases
Security
Human-computer interaction
Network or systems operations
Ubiquitous systems/sensor networks
Computer Science education (please help me learn to teach!)
etc.
please send me your suggestions.
I'm even willing to go as far afield as robotics and bioinformatics,
if you can convince me it's worth my time to go read. I'm also
willing to accept old ideas that are finding new urgency;
transactional memory would be a good example, virtualization another.
I will leave it to you to balance newness of idea with real-world
impact, and to decide whether to recommend the key original paper(s)
or a survey paper, if one exists already.
(I'm doing this a tad ad hoc; I really should reconcile against, say,
the ACM computing curricula or a journal keyword list, but I probably
won't bother. Some may also object to the categorizations above;
don't worry about it, just send me the papers/ideas you think are
critical, and we will work on the categorization and balance of the
list later.)
(Yes, the choice to limit this to the last decade is arbitrary; there
are plenty of old ideas I'm not familiar with, too -- I recently ran
across R-trees for the first time, for example -- but, generally
speaking, I'm after ideas too new to have made it into textbooks,
otherwise I'd just pick up a recent text.)
(And on these grounds let me say that I'm enjoying the revitalized
CACM, which seems to be helpful in focusing on new, important ideas,
with more timely and accessible review articles than Computing
Surveys.)
A few thoughts to get started:
* The hierarchy of limits in computing technology:
An outstanding synthesis of Moore's Law, Landauer's principle, etc.
Dense, but well-written and worth the effort to understand. I don't
care if the ideas are old, this one is critical.
@Article{meindl01:_terascale-si,
author = {James D. Meindl and Qiang Chen and Jeffrey A. Davis},
title = {Limits on Silicon Nanoelectronics for Terascale
Integration},
journal = {Science},
year = 2001,
volume = 293,
pages = {2044--2049}
}
* proper network topology analysis:
A clear-eyed look at mathematical analysis of and understanding of the
Internet.
@article{JohnCDoyle10112005,
author = {Doyle, John C. and Alderson, David L. and Li, Lun and Low, Steven and Roughan, Matthew and Shalunov, Stanislav and Tanaka, Reiko and Willinger, Walter},
title = {{The "robust yet fragile" nature of the Internet}},
journal = {Proceedings of the National Academy of Sciences},
volume = {102},
number = {41},
pages = {14497-14502},
doi = {10.1073/pnas.0501426102},
year = {2005}
}
* distributed hash tables (DHTs):
Just barely makes my "decade" cutoff, but one of the most influential
ideas of recent years; fault-tolerant, truly distributed,
loosely-coherent key-value pairs, useful for managing e.g. a lookup
system for P2P networks. (You can argue for another choice of
paper.)
@inproceedings{stoica2001chord,
title={{Chord: A scalable peer-to-peer lookup service for internet applications}},
author={Stoica, I. and Morris, R. and Karger, D. and Kaashoek, M.F. and Balakrishnan, H.},
booktitle={Proceedings of the 2001 conference on Applications, technologies, architectures, and protocols for computer communications},
pages={149--160},
year={2001},
organization={ACM New York, NY, USA}
}
* Peer-to-peer (P2P) networks:
No recommended paper here yet. I've read a few, but none really stand
out in my mind. Suggestions?
* Delay-tolerant networks (DTNs):
No recommended paper here yet. Might not make the decade cutoff.
* Network coding:
Just barely makes the decade cutoff. This is the seminal paper,
AFAIK, but the writing in it is poor; recommendations for an easier
read gladly accepted. A highly theoretical idea that seems to be
gaining surprising traction in real-world systems.
@article{ahlswede2000nif,
title={Network information flow},
author={Ahlswede, R. and Cai, N. and Li, S.Y.R. and Yeung, R.W.},
journal={Information Theory, IEEE Transactions on},
volume={46},
number={4},
pages={1204--1216},
year={2000}
}
* Ajax:
I haven't seen any good papers on it, and it's a philosophy rather
than a technology, but surely it's important enough to rate
here...suggestions?
* Transactional memory:
One possible route to effective parallel programming. The right one?
Good question!
@Article{larus07:_trans_mem,
author = {James Larus and Christos Kozyrakis},
title = {Transactional Memory},
journal = cacm,
year = 2008,
volume = 51,
number = 7,
pages = {80--89},
doi = {10.1145/1364782.1364800}
}
* MapReduce:
One of a set of very good ideas to come out of Google in the last few
years. The right way to get to real parallel programming on very
large datasets? Good question! The database community seems to think
not. But having done a little MPI programming, I can assure you that
MPI is not for the masses, at least not in its current form.
@article{dean:mapreduce-cacm,
author = {Jeffrey Dean and Sanjay Ghemawat},
title = {{MapReduce}: simplified data processing on large clusters},
journal = {Commun. ACM},
volume = {51},
number = {1},
year = {2008},
issn = {0001-0782},
pages = {107--113},
doi = {http://doi.acm.org/10.1145/1327452.1327492},
publisher = {ACM},
address = {New York, NY, USA},
}
* Rethink the Sync:
Recommended by a friend, who called it his favorite paper of the
decade.
@inproceedings{nightingale2006rethink,
title={Rethink the sync},
author={Nightingale, E.B. and Veeraraghavan, K. and Chen, P.M. and Flinn, J.},
booktitle={Proceedings of the 7th symposium on Operating systems design and implementation},
pages={1--14},
year={2006},
comment ={Best paper; Honey's favorite paper of the last decade.}
}
* Disk MTTF:
An analysis rather than idea paper, but important for anyone who does
large-scale systems or cares when their laptop disk is likely to
fail.
@article{schroeder2007dfr,
title={{Disk failures in the real world: What does an MTTF of 1,000,000 hours mean to you}},
author={Schroeder, B. and Gibson, G.A.},
journal={Proceedings of the 5th USENIX Conference on File and Storage Technologies (FAST)},
year={2007}
}
That's eight papers on eleven ideas that have changed the way I think
about computing systems in the last few years, mostly in the
networking area (a couple may have to get deleted to hold the final
list to 100 papers). There are many other topics, of course (chip
multiprocessors and radical new architectures such as TRIPS;
hypervisors and virtualization of systems and networks is another
old/new idea), but I'll leave them to others to promote. I've read
hundreds of papers in the last decade, but I'm interested in what
*you* consider important, not my own biases here. And while IP is a
heavily network-oriented list and will no doubt expand on that set of
ideas above, please look as far abroad as you comfortably can -- or
forward on to colleagues in other areas who might be interested in
such a list.
Please help educate me!
Friday, May 15, 2009
Mountain Music
I do like mountain music, though I wouldn't qualify myself as a "big" fan.
Today's discovery:
WMMT, broadcasting from Whitesburg, KY (about an hour from my parents' place), using 15,000 watts, a decent Internet service, and an all-volunteer staff.
The mountain version of "All My Loving" was nice, though I'm actually partial to instrumentals. I like the traditional mountain music, with dulcimer, fiddle, banjo, including the gospels. Bluegrass is okay, but I'm not a big fan of modern country. I'm not wild about steel guitar and, despite (because of?) being a drummer, I don't like the heavy drums and simple 4/4 beat of a lot of commercial country.
Just to blow my mind, after three hours of "Bluegrass Express", they wedged some Latin jazz in between "I Need You Like a Train Needs a Track" and "He Got You, I Got the Dog" (how can you go wrong with a song that starts, "He's sleeping in my double-wide, hunting on my land" and proceeds to conclude that getting the dog was the better end of the deal?).
I commented recently that the problem with a lot of Internet music services is that they are predictable, and hence have no personality. This one - and my favorite, KCSM - definitely have personality.
And every WMMT announcer I've heard so far sounds like someone I went to high school with. Ah, the sounds of home...
Today's discovery:
WMMT, broadcasting from Whitesburg, KY (about an hour from my parents' place), using 15,000 watts, a decent Internet service, and an all-volunteer staff.
The mountain version of "All My Loving" was nice, though I'm actually partial to instrumentals. I like the traditional mountain music, with dulcimer, fiddle, banjo, including the gospels. Bluegrass is okay, but I'm not a big fan of modern country. I'm not wild about steel guitar and, despite (because of?) being a drummer, I don't like the heavy drums and simple 4/4 beat of a lot of commercial country.
Just to blow my mind, after three hours of "Bluegrass Express", they wedged some Latin jazz in between "I Need You Like a Train Needs a Track" and "He Got You, I Got the Dog" (how can you go wrong with a song that starts, "He's sleeping in my double-wide, hunting on my land" and proceeds to conclude that getting the dog was the better end of the deal?).
I commented recently that the problem with a lot of Internet music services is that they are predictable, and hence have no personality. This one - and my favorite, KCSM - definitely have personality.
And every WMMT announcer I've heard so far sounds like someone I went to high school with. Ah, the sounds of home...
Saturday, April 11, 2009
Kabuki Driving
After more than five years of living here in Japan, and with the expiration of my California driver's license looming (now only days away), I finally decided to get a Japanese driver's license.
Six weeks, six trips to the testing center (more than an hour away), innumerable, insufferable hours spent in plastic chairs crammed too close together to be comfortable, three actual chances sitting in the driver's seat with an inspector, and more than three hundred bucks later...
I still don't have a license.
In fact, given that the effort and expense have already exceeded the license's value to me, I'm thinking about just giving up. For Japan, this is more of an inconvenience to Mayumi than to me; once a year or so, we rent a car and go somewhere, and since I don't have a license, she does all the driving, while I look out the window, fiddle with the radio, read or nap. For most business trips, I'm actually *forbidden* from renting a car (regardless of how realistic a restriction that is for the city I'm travelling to), so it's not a big deal there, either. The only time I *really* need a license is when we're in West Virginia, visiting family, or the far-too-rare occasions when we get to California for pleasure.
(I am told by friends that I *can* renew my California driver's license, even though I no longer live there, but you have to appear in person and get a retinal scan -- and the CA DMV has cut hours and closed offices as a result of the financial crisis.)
There would be a certain satisfaction in taking the moral stand that we actively oppose the use of private cars. But I'm really not in that camp. I think the world would be a better place -- and Americans healthier -- if Americans drove less, used less oil, and ate less beef, and Japanese actually attempted to manage ocean fish stocks rather than simply exterminate them, but I'm not advocating the complete banishment of cars, beef, and sushi. We choose not to have a car here, since we think it's healthier and better for the environment, but don't press that choice on others. (I admit, we still eat sushi, though I'm talking about the fish more, and slowly working toward lowering the catch limit on our take at a sushi restaurant.) And I'd be lying if I said that economics didn't figure into it -- we couldn't afford to buy a car right now if we tried (we have a house and annual trips to the U.S. instead).
Anyway, I've been driving for more than a quarter of a century now. How could I possibly flunk a driving test, you ask? Ah, naive one, let me instruct you in the ways of this country...
First off, flunking is not unusual, it's the norm. The pass rate, I am told, is less than 30%, even among Japanese, and most of those who pass are clearly on their second or third (or fourth or fifth) attempt. In three attempts, in which I sat with groups of foreigners and Japanese returning from living overseas attempting to transfer their license to Japan, I have not yet seen a SINGLE person actually pass the driving test. One Japanese woman drove for years in California, and had driven more than 5,000 kilometers back in Japan using an international license that was about to expire, flunked it three times.
So, if each test were a random, independent variable (they're not) with a failure rate of 70%, about 35% of the people would flunk at least three tests.
The thing you have to understand is that it's not actual driving, it's Kabuki Driving: it involves exaggerated motions, long pauses for dramatic effect, an obscure vocabulary, and improbable sub-plots, and has only the most oblique relationship to everyday life. There's even an audience (they stick another testee in the back seat while you drive). The only thing it doesn't have is exotic costumes. (In fact, if I read the sign right, along with flip-flops, wooden "geta" sandals, and excessively high heels, you are not allowed to take the test while wearing a kimono. Go figure.)
The rules for getting a license differ depending on how you're going about it. Most Europeans can simply take a written test and be issued a license on the spot. Americans and most other Asians have to take the written test *and* a driving one. America is not a signatory to some international treaty (the Geneva Convention on treatment of prisoners of war, I believe), and even if it were, there is no central authority in the U.S. Japan would have to decide whether or not to accept licenses from at least fifty-one different jurisdictions.
But still, for Americans with a license, the process is much easier than starting without any license at all. The written test is ridiculously easy -- ten true/false questions (in both English and Japanese) with 70% being a pass. Close your eyes and guess, and you've got a 17% percent chance of passing -- almost as good as passing the driving part with your eyes open. And the driving test is difficult, but easier than the one Japanese people go through.
For Japanese people with no license, the first thing they do is sort you based on whether or not you have a certificate from a driving school. Without one, they give you a harder driving test, which apparently no one ever passes, so in effect, you have to attend driving school first.
Driving schools here are a HUGE business. (I'm convinced that the schools themselves are run by ex-inspectors, making out like bandits after decades of civil servant penury.) There is no learner's permit here, so the only way you get enough experience to pass the test is by going to a driving school. At a cost of three thousand dollars, and sixty (yes, sixty!) hours of instruction.
And they wonder why the number of young Japanese people getting driver's licenses is declining.
The Japanese taking the regular route are herded through the system like cattle, and given a registration number, made to wait, made to drive, made to wait (okay, that part is the same for foreigners). After finishing the test, they are NOT TOLD whether or not they passed. After another round of waiting, the registration numbers of the people who passed are posted on a giant LED signboard. A cheer goes up from the hundred or so people who passed, and groans from the other hundreds who didn't.
Once you get to the actual driving part (which is run on a closed course about the size of two American football fields), the kabuki starts. They tell you that you start with 100 points, and as long as the penalties are less than 30 points, you'll pass. But at the end they won't tell you how many points you have, just whether or not you passed; modulo a few major fauxes pas, ultimately I'm sure it's up to the judgment of the inspector. Most of the tests I have seen actually ended before the course was completed, with an "Okay, you're done, you flunked, please return to the start." But getting all the way through the course doesn't mean you passed; I didn't this last time. For the foreigners, at least, they do have some pity, and the inspector will usually give you an oral summary of what you did wrong.
There are minus points for failing to adjust the position of the driver's seat and mirror. There are minus points for holding the steering wheel wrong, including turning your hand palm up and sticking it through the wheel, turning it from the inside. The easiest one for the inspector to use is, "You didn't do enough safety checking," by which he means that your head stopped swiveling on its neck for several seconds at some point.
The one that got me twice is turning too wide. It's a fair cop, as Monty Python would say: I'm not accustomed to driving on the wrong side of the road, so I pull too far out into the road as I turn, in order to avoid hitting the curb. That was the first and third tries. On the second, I was careful about that -- and wound up hitting a curb, which is an automatic fail. There is a tight spot called the "Crank", with two right-angle turns and tight walls, that the car just barely fits through. I cleared that easily -- then clipped the curb on the corner as I turned out of it into the wider street. Dang. That experience pushed me too far back the other way for the third try, apparently.
Before trying the first time, I read up on the process on the web. That taught me that you need to stop at stop signs for three full seconds, which is an eternity. In California, you could watch a stop sign all day, and the *total* amount of time cars spent stopped at the sign might not be three seconds.
But just reading someone's advice on the web will give you a false confidence that you can pass the test. The course is really not that difficult in terms of where you're asked to drive, but there are many small points the inspector is looking for and they grade quite harshly. After flunking the first time, I did a one-hour practice session with one of the inspectors, one Saturday morning.
It was a revelation. Before doing that, I had NO IDEA that they want you to take turns at 10km/hour -- about six miles an hour! That's the speed at which you pull into a parking spot, fer cryin' out loud! Likewise, there is one place on the course with a "caution" sign, and caution means 10km/h. The one "high speed" part of the course is 40km/hour, about 25mph. After learning this, I laughingly told my lead-footed sister that she could never pass the test, since you have to drive slow. It's probably true.
So, I am contemplating whether or not to give this one last shot. They gave me a test slot for the afternoon of my birthday, which is when my CA license expires. I may simply not go.
I no longer have any ego bound up in my driving abilities, though I certainly used to take pleasure in a sunset cruise on an open road. Now I feel that if I was told that I could never drive again, my reaction would probably be to simply shrug. My father's midlife crisis was a red Toyota Supra. My mom joked that the car was fine, as long as he didn't get the blonde to go with it. My midlife crisis arrived earlier, and has resulted so far in a Ph.D. and a faculty position.
Flunking is something of an embarrassment for me in the lab, though. Murai Lab hosts the "iCar" project, which has been working since the early 1990s on connecting cars to the Internet. We have a lot of car enthusiasts, including one student who reportedly used to race professionally, and several others who own sports cars (Beemers, Alfas, a Lotus, an RX-8) and take them out to Mount Fuji Speedway on weekends.
Speaking of which, one of our faculty members (late forties, has an Alfa and two Beemers, one of which was brand new...) lost his license last year. 55km/h OVER the speed limit. License yanked (not suspended, canceled outright), forbidden to reapply for a year. His year is almost up, so he is now back in driving school, spending sixty hours and three thousand bucks to enjoy the company of eighteen-year-olds hearing for the first time that a car usually has four tires and a steering wheel, so he can get back in the brand new Beemer two-seater. He and the others spend a fair amount of energy discussing "license tourism", taking the three grand and going to Europe and getting a license instead (European ones translate more easily than American ones). Sounds like a win to me.
No one I know will defend the system. It's clearly ridiculous. But in a larger social engineering context, maybe it makes sense. If it's not in Japan's interest to have too many people on the roads, maybe it *should* be hard to get a license, and it doesn't really matter whether it's difficult for a good reason or if it's the equivalent of reading Shakespeare while standing on your head. As a liberal with a belief that government should actively work toward creating the society we would like to have, this could be exhibit A. Hmm. Let me think about that.
Six weeks, six trips to the testing center (more than an hour away), innumerable, insufferable hours spent in plastic chairs crammed too close together to be comfortable, three actual chances sitting in the driver's seat with an inspector, and more than three hundred bucks later...
I still don't have a license.
In fact, given that the effort and expense have already exceeded the license's value to me, I'm thinking about just giving up. For Japan, this is more of an inconvenience to Mayumi than to me; once a year or so, we rent a car and go somewhere, and since I don't have a license, she does all the driving, while I look out the window, fiddle with the radio, read or nap. For most business trips, I'm actually *forbidden* from renting a car (regardless of how realistic a restriction that is for the city I'm travelling to), so it's not a big deal there, either. The only time I *really* need a license is when we're in West Virginia, visiting family, or the far-too-rare occasions when we get to California for pleasure.
(I am told by friends that I *can* renew my California driver's license, even though I no longer live there, but you have to appear in person and get a retinal scan -- and the CA DMV has cut hours and closed offices as a result of the financial crisis.)
There would be a certain satisfaction in taking the moral stand that we actively oppose the use of private cars. But I'm really not in that camp. I think the world would be a better place -- and Americans healthier -- if Americans drove less, used less oil, and ate less beef, and Japanese actually attempted to manage ocean fish stocks rather than simply exterminate them, but I'm not advocating the complete banishment of cars, beef, and sushi. We choose not to have a car here, since we think it's healthier and better for the environment, but don't press that choice on others. (I admit, we still eat sushi, though I'm talking about the fish more, and slowly working toward lowering the catch limit on our take at a sushi restaurant.) And I'd be lying if I said that economics didn't figure into it -- we couldn't afford to buy a car right now if we tried (we have a house and annual trips to the U.S. instead).
Anyway, I've been driving for more than a quarter of a century now. How could I possibly flunk a driving test, you ask? Ah, naive one, let me instruct you in the ways of this country...
First off, flunking is not unusual, it's the norm. The pass rate, I am told, is less than 30%, even among Japanese, and most of those who pass are clearly on their second or third (or fourth or fifth) attempt. In three attempts, in which I sat with groups of foreigners and Japanese returning from living overseas attempting to transfer their license to Japan, I have not yet seen a SINGLE person actually pass the driving test. One Japanese woman drove for years in California, and had driven more than 5,000 kilometers back in Japan using an international license that was about to expire, flunked it three times.
So, if each test were a random, independent variable (they're not) with a failure rate of 70%, about 35% of the people would flunk at least three tests.
The thing you have to understand is that it's not actual driving, it's Kabuki Driving: it involves exaggerated motions, long pauses for dramatic effect, an obscure vocabulary, and improbable sub-plots, and has only the most oblique relationship to everyday life. There's even an audience (they stick another testee in the back seat while you drive). The only thing it doesn't have is exotic costumes. (In fact, if I read the sign right, along with flip-flops, wooden "geta" sandals, and excessively high heels, you are not allowed to take the test while wearing a kimono. Go figure.)
The rules for getting a license differ depending on how you're going about it. Most Europeans can simply take a written test and be issued a license on the spot. Americans and most other Asians have to take the written test *and* a driving one. America is not a signatory to some international treaty (the Geneva Convention on treatment of prisoners of war, I believe), and even if it were, there is no central authority in the U.S. Japan would have to decide whether or not to accept licenses from at least fifty-one different jurisdictions.
But still, for Americans with a license, the process is much easier than starting without any license at all. The written test is ridiculously easy -- ten true/false questions (in both English and Japanese) with 70% being a pass. Close your eyes and guess, and you've got a 17% percent chance of passing -- almost as good as passing the driving part with your eyes open. And the driving test is difficult, but easier than the one Japanese people go through.
For Japanese people with no license, the first thing they do is sort you based on whether or not you have a certificate from a driving school. Without one, they give you a harder driving test, which apparently no one ever passes, so in effect, you have to attend driving school first.
Driving schools here are a HUGE business. (I'm convinced that the schools themselves are run by ex-inspectors, making out like bandits after decades of civil servant penury.) There is no learner's permit here, so the only way you get enough experience to pass the test is by going to a driving school. At a cost of three thousand dollars, and sixty (yes, sixty!) hours of instruction.
And they wonder why the number of young Japanese people getting driver's licenses is declining.
The Japanese taking the regular route are herded through the system like cattle, and given a registration number, made to wait, made to drive, made to wait (okay, that part is the same for foreigners). After finishing the test, they are NOT TOLD whether or not they passed. After another round of waiting, the registration numbers of the people who passed are posted on a giant LED signboard. A cheer goes up from the hundred or so people who passed, and groans from the other hundreds who didn't.
Once you get to the actual driving part (which is run on a closed course about the size of two American football fields), the kabuki starts. They tell you that you start with 100 points, and as long as the penalties are less than 30 points, you'll pass. But at the end they won't tell you how many points you have, just whether or not you passed; modulo a few major fauxes pas, ultimately I'm sure it's up to the judgment of the inspector. Most of the tests I have seen actually ended before the course was completed, with an "Okay, you're done, you flunked, please return to the start." But getting all the way through the course doesn't mean you passed; I didn't this last time. For the foreigners, at least, they do have some pity, and the inspector will usually give you an oral summary of what you did wrong.
There are minus points for failing to adjust the position of the driver's seat and mirror. There are minus points for holding the steering wheel wrong, including turning your hand palm up and sticking it through the wheel, turning it from the inside. The easiest one for the inspector to use is, "You didn't do enough safety checking," by which he means that your head stopped swiveling on its neck for several seconds at some point.
The one that got me twice is turning too wide. It's a fair cop, as Monty Python would say: I'm not accustomed to driving on the wrong side of the road, so I pull too far out into the road as I turn, in order to avoid hitting the curb. That was the first and third tries. On the second, I was careful about that -- and wound up hitting a curb, which is an automatic fail. There is a tight spot called the "Crank", with two right-angle turns and tight walls, that the car just barely fits through. I cleared that easily -- then clipped the curb on the corner as I turned out of it into the wider street. Dang. That experience pushed me too far back the other way for the third try, apparently.
Before trying the first time, I read up on the process on the web. That taught me that you need to stop at stop signs for three full seconds, which is an eternity. In California, you could watch a stop sign all day, and the *total* amount of time cars spent stopped at the sign might not be three seconds.
But just reading someone's advice on the web will give you a false confidence that you can pass the test. The course is really not that difficult in terms of where you're asked to drive, but there are many small points the inspector is looking for and they grade quite harshly. After flunking the first time, I did a one-hour practice session with one of the inspectors, one Saturday morning.
It was a revelation. Before doing that, I had NO IDEA that they want you to take turns at 10km/hour -- about six miles an hour! That's the speed at which you pull into a parking spot, fer cryin' out loud! Likewise, there is one place on the course with a "caution" sign, and caution means 10km/h. The one "high speed" part of the course is 40km/hour, about 25mph. After learning this, I laughingly told my lead-footed sister that she could never pass the test, since you have to drive slow. It's probably true.
So, I am contemplating whether or not to give this one last shot. They gave me a test slot for the afternoon of my birthday, which is when my CA license expires. I may simply not go.
I no longer have any ego bound up in my driving abilities, though I certainly used to take pleasure in a sunset cruise on an open road. Now I feel that if I was told that I could never drive again, my reaction would probably be to simply shrug. My father's midlife crisis was a red Toyota Supra. My mom joked that the car was fine, as long as he didn't get the blonde to go with it. My midlife crisis arrived earlier, and has resulted so far in a Ph.D. and a faculty position.
Flunking is something of an embarrassment for me in the lab, though. Murai Lab hosts the "iCar" project, which has been working since the early 1990s on connecting cars to the Internet. We have a lot of car enthusiasts, including one student who reportedly used to race professionally, and several others who own sports cars (Beemers, Alfas, a Lotus, an RX-8) and take them out to Mount Fuji Speedway on weekends.
Speaking of which, one of our faculty members (late forties, has an Alfa and two Beemers, one of which was brand new...) lost his license last year. 55km/h OVER the speed limit. License yanked (not suspended, canceled outright), forbidden to reapply for a year. His year is almost up, so he is now back in driving school, spending sixty hours and three thousand bucks to enjoy the company of eighteen-year-olds hearing for the first time that a car usually has four tires and a steering wheel, so he can get back in the brand new Beemer two-seater. He and the others spend a fair amount of energy discussing "license tourism", taking the three grand and going to Europe and getting a license instead (European ones translate more easily than American ones). Sounds like a win to me.
No one I know will defend the system. It's clearly ridiculous. But in a larger social engineering context, maybe it makes sense. If it's not in Japan's interest to have too many people on the roads, maybe it *should* be hard to get a license, and it doesn't really matter whether it's difficult for a good reason or if it's the equivalent of reading Shakespeare while standing on your head. As a liberal with a belief that government should actively work toward creating the society we would like to have, this could be exhibit A. Hmm. Let me think about that.
Tuesday, January 20, 2009
Happy Birthday!
A day late, but yesterday was Edgar Allan Poe's two hundredth birthday! Happy birthday to one of my favorite writers.
Tonight's midnight (well, two a.m., Tokyo time) promises to be anything but dreary, as I ponder (perhaps weak and weary due to a cold I've contracted) the inauguration. Obama's TODO list is infinitely long, but hope dawns across the land. Hmm, there are lots of comparisons to Lincoln, King, and Kennedy; I wonder if there's an appropriate Poe quote?
Tonight's midnight (well, two a.m., Tokyo time) promises to be anything but dreary, as I ponder (perhaps weak and weary due to a cold I've contracted) the inauguration. Obama's TODO list is infinitely long, but hope dawns across the land. Hmm, there are lots of comparisons to Lincoln, King, and Kennedy; I wonder if there's an appropriate Poe quote?
Wednesday, January 14, 2009
Monday, January 12, 2009
Anniversary of Two Eras
This past week was the anniversary of two important eras in Japanese history, one symbolic and high profile, the other of enormous practical impact but much lower profile.
January 7th was the twentieth anniversary of the death of Emperor Hirohito, the end of the Showa Era, and the start of the Heisei Era with the ascension of the current occupant to the throne.
That same day, Jun Murai was at Narita Airport, on his way to Washington, D.C., for some rather obscure technical work. On about January 11th, he got it running: Japan was connected to the Internet, via IP over X.25, for the first time.
Several years later, when I left Japan for the first time, I gave my email address to many Japanese (and foreign) friends. Most said, "What's this?" I replied, "Hang onto it, in a few years you'll know." And indeed, I occasionally am contacted by friends from that time, though I suspect they come upon my address now via Google, Facebook, LinkedIn, or another, mutual friend.
January 7th was the twentieth anniversary of the death of Emperor Hirohito, the end of the Showa Era, and the start of the Heisei Era with the ascension of the current occupant to the throne.
That same day, Jun Murai was at Narita Airport, on his way to Washington, D.C., for some rather obscure technical work. On about January 11th, he got it running: Japan was connected to the Internet, via IP over X.25, for the first time.
Several years later, when I left Japan for the first time, I gave my email address to many Japanese (and foreign) friends. Most said, "What's this?" I replied, "Hang onto it, in a few years you'll know." And indeed, I occasionally am contacted by friends from that time, though I suspect they come upon my address now via Google, Facebook, LinkedIn, or another, mutual friend.
Wednesday, December 24, 2008
ToN Quantum Paper Online
Our Transactions on Networking paper, "System Design for a Long-Line Quantum Repeater," is now available in final form in the IEEE's Digital Library. Print edition is not due until August 2009. Thanks as always to Thaddeus, Bill and Kae for their hard work on it.
Tuesday, December 23, 2008
MARA in Infocom!
Congratulations to Yasu Ohara and Shinji Imahori! Yasu's paper (on which Imahori-san and I are coauthors), "MARA: Maximum Alternative Routing Algorithm", was accepted to INFOCOM 2009, one of 282 acceptances out of 1,435 submissions. This work is follow-through on Yasu's Ph.D. thesis, completed and defended in our lab last academic year. It's good work on how to do route calculations to support multipath forwarding in a network.
A trip to Rio for Yasu next April!
A trip to Rio for Yasu next April!
Monday, December 22, 2008
New Campus Web Site
For those who aren't allergic to Flash, our campus has a new website for faculty & research profiles. Check it out, let me know what you think.
Saturday, December 20, 2008
Tell Me a Story
What he said. Robert Krulwich, you da man.
Now, if only I could write like that...I can't, but sign me up, I'm willing to give it a shot.
Now, if only I could write like that...I can't, but sign me up, I'm willing to give it a shot.
Tuesday, December 16, 2008
Sustainable Sushi
...is largely a hopeless prospect in this country (let alone the rising appetite for it world-wide, especially in China) for the foreseeable future, but: the Monterey Bay Aquarium's sustainable sushi guide is a win.
A translation to both Japanese language and Japanese market availability would be a plus...
FWIW, a sushi bar here is actually a reasonable place to take a non-squeamish vegan. At a good place, there are a number of pure vegetable rolls. Not clear how much goodwill you earn with the sushi chef that way, but it's a much better menu bet than a tonkatsu (deep-fried pork) restaurant.
I can't promise perfection, but I can promise to do my best to follow the guide.
Now, how to popularize the ideas here?
A translation to both Japanese language and Japanese market availability would be a plus...
FWIW, a sushi bar here is actually a reasonable place to take a non-squeamish vegan. At a good place, there are a number of pure vegetable rolls. Not clear how much goodwill you earn with the sushi chef that way, but it's a much better menu bet than a tonkatsu (deep-fried pork) restaurant.
I can't promise perfection, but I can promise to do my best to follow the guide.
Now, how to popularize the ideas here?
Friday, November 28, 2008
Give Us This Day Our Daily Banana
In English, "bread" can be a synonym for "meal" or "food" (and for "money", though that's a later innovation), as evidenced by the line from the Lord's Prayer, "Give us this day our daily bread."
In Japanese, "gohan" is both (cooked) "rice" and "meal": "Gohan wo tabeta?" "[Have you] eaten a meal?" (Transliterated; a more natural rendering would be "Have you eaten?")
An article in a recent issue of Science, talking about bananas, informs me that in Uganda the word for "banana" is the same as the word for "food". Sadly, the article didn't give the word for it, or even name the language (presumably Swahili).
I read the article on the train on the way home yesterday, and when I got home I was dying for a banana. Fortunately, Mayumi had bought bananas. Unfortunately, my girls managed eat all of them before I got home :-).
That's perhaps an allegory for what's happening worldwide: the Cavendish banana, the most common around the world, is under attack by a fungus all over the planet. The plant can be grown only by cloning (it's sterile) and since all the plants are genetically identical, they are all equally susceptible.
Other strains of bananas might be less vulnerable, but are suffering from neglect. (The most fragrant bananas I've ever had were in Nepal, some small variety that smelled of cinnamon.) Let's not let the world's fourth-most-important staple crop (behind rice, wheat and corn) get away from us, people!
In Japanese, "gohan" is both (cooked) "rice" and "meal": "Gohan wo tabeta?" "[Have you] eaten a meal?" (Transliterated; a more natural rendering would be "Have you eaten?")
An article in a recent issue of Science, talking about bananas, informs me that in Uganda the word for "banana" is the same as the word for "food". Sadly, the article didn't give the word for it, or even name the language (presumably Swahili).
I read the article on the train on the way home yesterday, and when I got home I was dying for a banana. Fortunately, Mayumi had bought bananas. Unfortunately, my girls managed eat all of them before I got home :-).
That's perhaps an allegory for what's happening worldwide: the Cavendish banana, the most common around the world, is under attack by a fungus all over the planet. The plant can be grown only by cloning (it's sterile) and since all the plants are genetically identical, they are all equally susceptible.
Other strains of bananas might be less vulnerable, but are suffering from neglect. (The most fragrant bananas I've ever had were in Nepal, some small variety that smelled of cinnamon.) Let's not let the world's fourth-most-important staple crop (behind rice, wheat and corn) get away from us, people!
guGUttara?
"To google" is now a verb in English (at least, the American (correct) form of the language, not sure about other parts of the diaspora). "He googled it," "I'm googling it now...," "Why don't you google it?" and more.
The same thing is true in Japanese. "Google" in Japanese is "GUUguru" (or "GU-guru"), written in katakana, the syllabary used for "loan" (imported) words, with a long "uu" and the unfortunate but necessary mangling of the pronunciation. (Not that Americans can come close to pronouncing Chinese or even French correctly, but that's not the point here.)
By fortunate coincidence, "-ru" is the common ending for verbs in Japanese, so conjugating it is natural and trivial, but the emphasized syllable changes: "guGUrimasu", "guGUrimashita". You almost never hear the formal form of it, though, you usually hear the informal form "guGUtta" ("googled") or "guGUtte iru" ("am googling/is googling"). Japanese has a verb form (not sure of the technical name in either Japanese or English) for "why don't you..." or "if you...", which usually ends in "-ttara".
And if you don't believe me, guguttara?
The same thing is true in Japanese. "Google" in Japanese is "GUUguru" (or "GU-guru"), written in katakana, the syllabary used for "loan" (imported) words, with a long "uu" and the unfortunate but necessary mangling of the pronunciation. (Not that Americans can come close to pronouncing Chinese or even French correctly, but that's not the point here.)
By fortunate coincidence, "-ru" is the common ending for verbs in Japanese, so conjugating it is natural and trivial, but the emphasized syllable changes: "guGUrimasu", "guGUrimashita". You almost never hear the formal form of it, though, you usually hear the informal form "guGUtta" ("googled") or "guGUtte iru" ("am googling/is googling"). Japanese has a verb form (not sure of the technical name in either Japanese or English) for "why don't you..." or "if you...", which usually ends in "-ttara".
And if you don't believe me, guguttara?
Subscribe to:
Posts (Atom)