1,767 karma · joined September 29, 2015
I'm always a little frustrated whenever I see this aphorism perpetuated since I think it gives the impression that a static type system is doing more than it is actually doing. In type systems that are used outside of academia, the main thing your static types are doing is checking whether the shapes of your data and functions all line up. With some small exceptions, that's it: the compiler will tell you if your LEGOs fit together, but not if you've built a knife instead of a fork.
I know what this aphorism is getting at, which is that in some domains and circumstances a lot of your bugs are "shape" errors, and it's gratifying when you're writing OCaml or Java and you can, say, refactor without hesitation, knowing the compiler will find even the most unused paths where you need to modify an invocation of your function. But it's been my and others' experience that there are many times where this isn't your most pressing concern, and could in fact be a pretty boring concern that you don't even want to pay the type annotation tax for. (I also think there's something to the idea that a static type system can instill too much confidence and encourage the pursuit of bad abstractions like 18-arg functions that can no longer be effectively reasoned about by an unaided human mind, but that's another topic.)
> People create languages to communicate on an as-needed basis.
So there's an assumption that languages exist only because they are "needed". Maybe this is true for pidgins, but where's the necessity in e.g. speakers of Proto-Polynesian moving to different islands, losing contact with each other, and having their languages diverge into Hawaiian, Samoan, Tuvaluan, etc.? For the most part, the creation of something we recognize as a distinct language is an unconscious process and is guided by incidental facts like physical location and resulting contact patterns with other language-communities.
> And languages that aren't needed anymore [...] fall away.
I think this is a strange way to put things, and that it could distort some facts about why people lose their ancestral languages. Often languages _do_ cease to be spoken because of, say, economic and bureaucratic reasons, but when this happens it'd be simplistic to look on and say that this is the natural order of things. Many American Indian languages ceased to be spoken in the 19th century because the United States tore Indian children from their parents and put them many miles away in English-only Christian boarding schools where they were physically punished if they ever spoke a word of their mother tongue[1]. It is an odd kind of necessity here that drove American Indians from their languages.
> I'll be thrilled if every language in the world disappears except for one, and we all communicate in it. I don't care which one, although ideally it'll be a simple or logical one, like Indonesian/Malay, with a writing system like Hangul.
Even if we snapped our fingers and everyone in the world suddenly spoke Malay written in a perfectly regular writing system, there's a lot of reason to think that the global language would quickly fragment into many languages again. This would be due to many forces, but two big ones among them would be plain old isolation from the rest of the world (e.g. in the highlands of Papua New Guinea) and the fact that changing the way you speak is a very powerful way of signaling your identity and ideological alignments[2].
More generally, as others have pointed out, people who believe in the value of documenting endangered languages do so most commonly because they believe in the general anthropological value of such data, the specific linguistic value of the data as another data point we can use to investigate the nature of language in general, and last but not least, the value of giving the communities who speak these languages the ability to draw on these records should they ever desire to develop their language.
[0]: https://www.jstor.org/stable/416854
[1]: https://en.wikipedia.org/wiki/American_Indian_boarding_schoo...
It's that the user needs to learn not just Scala but also Java whenever they want to do anything "real". You might say this is a minor hangup, but for learners having to context switch back and forth between Java and Scala and dealing with interop issues can make for much more cognitive load than using a non-hosted language like Python or Go.
> The fact that Williams students are so consistently strong (with very few exceptions) have some implications: Most or all students can be expected to pass a given examination, whereas at KTH a course which everyone passes is looked upon with suspicion (this is particularly true for intro courses). Unless the admission procedure at KTH is changed to involve some kind of aptitude test, it is unavoidable, I think, that the intro courses at KTH will act as that filter instead (even if it seems a wasteful system both on a individual and a societal level). Moreover, at Williams lots of individually adapted help can be given to the few students who experience problems in a class. At KTH, fewer such resources exist (although there is some help to be had in basic math and computer programming). The Williams students always have the option of contacting their professors directly, and visiting them during office hours. Very few KTH teachers have office hours to my knowledge. A female master's student of mine described the situation: "At KTH one reads a number of very difficult courses at a very high pace, and there is really nobody there to help you. Unless you're able to find or create a good study group among your peers, you're unlikely to graduate".
You're right that the critical period hypothesis is still not settled, but let's go back to your proposal, that anyone who's immersed and motivated enough will be able to acquire nativelike proficiency. While we're in the realm of anecdotes (since you make reference to your own experience), I witnessed several peers of mine in a months-long language immersion program fall behind others in the program by quite a margin, with (IMO) little hope of nativelike proficiency even with months more of intensive classes, despite apparent motivation (sometimes much more than the better performers) and 24/7 immersion in the target language.
Going beyond anecdotes now, let's consider results from the literature against the assumption that if only adults could not be so easily discouraged they would be able to attain more nativelike proficiency. In that case, we'd expect at least a few places in time and space to have second language learners who do a phenomenal job of acquiring the target language, yet as far as I know that's never been found in the literature. Birdsong[0] reports that the range of attested rates of nativelike proficiency in L2 learners is between 5% and 25%. Moreover, there's a wealth of literature that documents in detail the specific ways in which language acquisition mechanisms falter beginning around age 6[1], which is in line with the suggestion that nativelike proficiency becomes progressively harder with age.
Neither of these results pushes your suggestion beyond plausibility, of course, but it does seem to me like the preponderance of evidence is on one side. If you know of any studies with findings that support the idea that motivation can be a decisive factor in acquiring nativelike proficiency in a second language I'd be really interested to see them.
[0]: https://web.stanford.edu/~hakuta/www/research/publications/(...
[1]: https://www.jstor.org/stable/pdf/44488300.pdf?casa_token=YS2...
> The REST API also provides an experimental endpoint for SPARQL 1.1 Protocol queries under /sparql/, rewriting the query into the Crux Datalog dialect. Only a small subset of SPARQL is supported and no other RDF features are available.
That's not to say that using the SQL API is a bad idea, but if you're using Crux from Clojure, you'd be missing out on some stuff.
Perhaps it's hard to say much more without knowing who these transliterations are supposed to serve. If it's a general Japanese-speaking population with limited knowledge of English, I'm not sure whether they'd prefer romaji or the original spelling.
Worthy of mention, of course, is Spacemacs[1], which made Emacs approachable to me, someone who hadn't used much beyond Notepad++ and Eclipse before then.