3 ms·
Add a few examples of known / easy-to-grasp algorithms: sorting, processing of a stream / tree / graph, a concurrent interaction, some easy parsing, etc. A few
by nine_k 9y ago
Add a few examples of known / easy-to-grasp algorithms: sorting, processing of a stream / tree / graph, a concurrent interaction, some easy parsing, etc. A few examples on which your language shines, shows some of the key features that make it different and worth learning.
Also, aesthetics do play a role: if your language is excessively hard to parse, or your examples contain a lot of copy-paste, etc, it might be a legitimate turn-off. It may be worth tolerating if other features are great. E.g. something like computing a convex hull of 2D points in APL or J may look terrible for an untrained eye, but you can nevertheless notice that it's like 40-50 characters total.
- setr 9y agoJ has an almost explicit goal of being concise; it is specifically a feature they're reaching for, and thus makes sense to promote in such a fashion. But its absurd to judge the language on its syntax, if the language is uninterested in the syntax, until its almost unnacceptably noisy or confounding. Looking into a language should ideally be first based on structural and semantic differences, and then syntactic. And a sufficiently semantically different language will offer little with its code snippets, as it wont make sense without understanding the paradigm. Even J; there's not much to take away other than that its dense from just the snippet. If anything, it mostly serves to scare people away as it approaches line noise, particularly when you don't yet know why it can be successful in such a fashion