In a FL learning environment (learning Chinese in Boston), where your students all speak the same L1 (as NS or NNS), you can address issues in learning the target language specific to particular L1 speakers. In a SL learning environment (English in Boston), your students might come from many different first language backgrounds, making bilingual instruction or support unavailable or at least impractical (in addition to being undesirable in a direct-approach inspired intensive language immersion environment).

American school children, compared to, say, the French, do not, by and large, get much overt grammar instruction, in the form of grammar and syntax. They might be introduced to some vocabulary expansion techniques via morphology, but otherwise not a lot of meta language instruction.

So the same program may be more appropriate for or implemented very differently in a FL environment than a SL one. Moreover, multilingual resources in software, which not all users in a SL environment may benefit from--depending on their first language and whether it's represented in the software--may be problematic to use. In addition to some students feeling left out, software with bilingual features also presents less of a linguistic challenge to other students, whose L1 is represented, because they can lean on their L1 for instruction.

From EuroTalk's Talk More American English, multilingual help.
This all gets back to a previous discussion of evaluating software, where we saw that one must be familiar with the local environment—where the software will be used, how it will be implemented, and who will use it—in order to make the most relevant determination of its utility.
No comments:
Post a Comment