os2museum.com

xyzzy , to retrocomputing in How Not To Release Historic Source Code | OS/2 Museum

tl;dr for article and comments:

Microsoft mangled arrays and code comments with ASCII extended characters into UTF-8 encoding, which makes building many of these files impossible without a lot of extra work. This was mistakenly attributed to Git.

The timestamps for each file are also not preserved, which is debatably a valid criticism of Git (original file timestamps can technically be preserved on an archive like this, but it requires a large amount of work to line up those times and the correct commit times programmatically).

Several Microsoft employees involved in this project appeared in the comments and offered to work directly with the author to correct the character encoding issues. One Microsoft employee indicated that historical timestamps could likely not be included due to Microsoft corporate policy around personally identifiable information.

sik0fewl , to retrocomputing in How Not To Release Historic Source Code | OS/2 Museum

Other than the timestamps, it doesn't seem like any of the issues are related to Git.

jadero , to Programming in This Code Smells of Desperation | OS/2 Museum

It certainly does, but sometimes desperate circumstances call for desperate actions. Or at least that’s how I justify my desperation code. :)

bignavy , to Programming in This Code Smells of Desperation | OS/2 Museum
@bignavy@programming.dev avatar

For a second I thought my github was going viral. ;)

This is a hilarious (and interesting!) read.

As a young(er) and slightly shittier web developer, before I really understood or could implement promises effectively (or when my code would ‘race’ and fail to recognize that the DOM hadn’t been loaded yet, so I couldn’t attach event listeners yet), I was known to implement a 2 second timeout.

It wasn’t pretty, but it worked!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • All magazines