2 ms·
Different domains will be optimally served by different features,[1] and any language that aspires to be usable in every domain must assimilate all of those fea
by kibwen 12y ago
Different domains will be optimally served by different features,[1] and any language that aspires to be usable in every domain must assimilate all of those features somehow. This is especially pernicious when considering how similar features can overlap and interact in unexpected ways, creating a labyrinth of corner cases with which a user must familiarize themselves. To maintain sanity, people will start carving out bits of the language to create "dialects" and restrict themselves to only those dialects, at which point you have effectively created multiple languages, each with their own idioms and learning curves.
Consider as well that as long as there exist languages that are so heavily-laden with features, there will continue to crop up "minimalist" languages like Go which will appeal to people by virtue of sheer simplicity and eat the lunch of the maximalist languages.
[1] An example: you know one thing that's great about using bash instead of Python for quick scripts? I don't need to put quotes around strings! Imagine how much time you'd waste in your terminal if you had to type `git grep foo -- bar.txt` as `git "grep" "foo" "--" "bar.txt"` all the time (which is valid bash, btw), or worse, `git("grep", "foo", "--", "bar.txt")`. TCL adopted this barewords-as-strings behavior as well, and though I hear mixed things about the rest of TCL this feature has always intrigued me. But this feature would be awful for any language where text input or string manipulation were not the predominant activity, so how would you go about turning it on and off? And even if you provide tools to automatically convert source files between barewords-as-strings and barewords-as-keywords, is that even the same language anymore?
- lmm 12y ago> To maintain sanity, people will start carving out bits of the language to create "dialects" and restrict themselves to only those dialects, at which point you have effectively created multiple languages, each with their own idioms and learning curves. Sure, scripting Scala looks rather different from high-performance Scala. But there's a continuity between them, which allows you to customize the appropriate "dialect" for a particular project, and avoids the overheads of using multiple languages in a project that straddles one of the lines. > how would you go about turning it on and off There's already a certain level of syntax customizability in most languages, e.g. I can use an import that will make symbols ('grep) treatable as strings. Whether this is a single language or a suite of languages designed to work closely together is an academic question, but I certainly think it would be possible to write something that allowed you to write (say) C-like code and Python-like code with a much smoother interface between them than there currently is when calling C from Python.