{'fraction_non_alphanumeric': 0.01020408163265306, 'fraction_numerical': 0.0011337868480725624, 'mean_word_length': 4.733766233766234, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
On the fate of software enhancements

One of the most serious problems for vendors of software is pressure from users to enhance and extend their products. 1 One important type of enhancement is the change in language form aimed at improving user productivity by making the system easier to learn and use. Ideas for this sort of enhancement appear regularly in such publications as Sigplan Notices . As evidenced by the correspondence in that publication, there are many opinions on the quality of these proposals. However, little is known about the actual fate of enhancements that have been added to existing software systems and released to users. When a new feature is released with the best of intentions and the usual fanfare of documentation and instruction, its acceptance by programmers may have little to do with the sincerity of the request or the quality of the feature.