26 ms·
I think the problems with your argument boil down to a few thigs: 1) You seem to be making an argument for some future language. That it would drop many of th
by kbenson 12y ago
I think the problems with your argument boil down to a few thigs:
1) You seem to be making an argument for some future language. That it would drop many of the things the make Perl Perlish is presupposed as what "people" would want. It would keep the name, as you state, because it would be the same community of people. The community of people that would keep the Perl name are not the same "people" you refer to that after their complaints are fixed would result in a Perl that is not Perlish.
2) If you are just talking about some abstract future language not actually related to Perl, don't use the Perl name. All you are doing is getting people riled up because you are attributing views to them (as the actual Perl community) that they disagree with. Again, I think this can be attributed to you taking a more abstract approach to what you are saying, but choosing to use concrete names, such as Perl, and doing so in the comments of an article about a new Perl release. People here would likely engage you gladly if it was obvious it's just a thought experiment about some futuristic language with nothing to do with Perl, including the name (although there would be challenges as to what you believe are the best features for this new language).
3) You presuppose it's a solved question of what's "best" for specific language features. For example, longer more explicit keywords, very simple to explain, very easy to read by a someone who doesn't know it. These are all good things when you try to maximize learning by novices. One could argue that at the same time, they don't really even allow experts. We have domain languages because they allow us to be more concise and accurate in our definitions. This necessitates learning the domain language, but I think few would argue that the hassle outweighs the future benefit to chemists, physicists, lawyers, engineers and architects to learn the specifics of the domain languages and representations they've developed. As a simple example, look at Ten Hundred Words of Science[1]. I admit it's probably useful to get laymen to understand a topic in general, but is it always sufficient to explain the specifics of that topic in the precise way it requires? Should experts in the field converse with each other this way? Should new bodies of work attempt to use this in the future instead of the domain languages they have developed? It's important to see these for what they are, tools used to shift focus towards or away from specific attributes. It's all a matter of perspective and what the goal is.
[1]: http://tenhundredwordsofscience.tumblr.com/ http://tenhundredwordsofscience.tumblr.com/
- logicallee 12y agoThis is very good, though this thread is a bit old and deep. Your italicized part ("Again, I think this can be attributed to you taking a more abstract approach to what you are saying, but choosing to use concrete names, such as Perl, and doing so in the comments of an article about a new Perl release.") made me laugh :) You are possibly right, though I was just making an off-hand remark and only just clarified when prompted explicitly. I think the 90 words / 4 lines I wrote originally were fine, and if someone asks for clarification no reason not to include it. In general I don't think an article on a new version of Perl is a bad place for such thoughts. I like your comments, especially, on domain specific languages, though as mentioned the thread is a bit old and deep to continue here. I couldn't find an email but if you reply with one I'm happy to discuss. Your tenhundredwordsofscience is a really good example of how it gets awkward not to use specialist vocabulary. I like your analogy with chemists, physicists, lawyers, engineers, and architects. The former two especially use specialist symbols that are impenetrable to total laypersons. anyway if you have an email I'll respond to your good points.
- kbenson 12y agoI updated my about with a slightly encoded version of my email, if you want to continue.
- logicallee 12y agoHi, tried to email you. You'd written "k e n t r a k # google's mail" but kentrak@google.com (the only way I could think of interpreting that) bounced. (I don't mind including it here as Google's server says that mailbox doesn't exist). Kind of ironic given our conversation :-) Could you bit a bit more explicit ;-)
- kbenson 12y ago@google.com is for people who work at google, @gmail.com is what I meant, as "google's email service". I agree, it wasn't very clear, but I don't particularly want harvesters having an easy time.