• 129 Posts
  • 818 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle






  • That sounds good, but when you start thinking about how to implement this practically, it seems like it would either be unfeasible or would fail to really address the problem.

    Maybe the rule would be: Unicode is allowed only in resource files. It would make code comments awkward for many non-English-speaking programmers. But suppose you did it, then since URLs can include Unicode, it would become normal to put URLs in resource files. If the VCS flagged up Unicode commits in source code, it would have to give resource files a pass. So in any case where you’re not hardcoding a URL it wouldn’t flag up Unicode URL abuses like the one illustrated here. You wouldn’t really have fixed the problem, just hidden it in a different way. You’d still need to flag up ambiguous Unicode characters in resource files.


















  • The focus on Microsoft is odd. I remember most people using WordPerfect for DOS and other non-WYSIWYG word processors up until around 1993. These were much better for focusing on writing. MS Word came from behind and started to take over as Windows 3.1 and then Windows 95 became standard. Word wasn’t the best word processor back then and was very buggy, but Microsoft succeeded in marketing it as a natural companion for Windows and bundling it with Excel and PowerPoint, and WordPerfect was slower to move to WYSIWYG.

    The rise of the web was also happening at that time, and this article doesn’t give it enough attention as a major influence on document format and a motivation behind markdown.