3 ms·
Like the sibling comment mentioned, it seems verbosity hinders reading comprehension rather than writing. Many IDEs understand this and hide some of the boilerp
by the_af 7y ago
Like the sibling comment mentioned, it seems verbosity hinders reading comprehension rather than writing. Many IDEs understand this and hide some of the boilerplate.
This raises the question: if the IDE autocompletes the boilerplate for you, and also hides it, why is it needed in the first place?
- usrusr 7y agoIn an autocomplete + simplify situation you usually type a little more than the simplified version before autocompleting and then allow the hiding to apply a lossy simplification. E.g. when the simplification is substituting a localization ID with the English text there might be multiple IDs mapped to identical texts and then the difference between the IDs is lost in the simplified representation. Differences which might be important, for example if the IDs are for different semantic concepts that map to separate texts in other languages. These simplifications are valuable because they are allowed to be "leaky", they can make the easy case even more easy by leaving the tough ones to the underlying raw, unsimplified truth.
- liability 7y agoConsider the verbosity of XML compared to s-expressions. <html>...</html> vs (html ...) The latter can trivially be used to output the former. The conclusion is obvious; some of these formats are objectively more verbose that others while having equivalent expressive power.
- saagarjha 7y agoInterestingly, depending on the context I find one or the other to be more readable. XML is great when you're got a lot of content, because it provides additional context of where you are in the closing tag, but it's not as great when you don't have a lot of data since the closing tag is just visual clutter.