nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq6u7alxzkjugh6535altqqk5gx7g0a63x6m300l898nenys0rsjuqz43src You know it's got to be a nightmare piece of code when a hardware vendor goes to the t...
@nprofile1q... The reason for this specific mess, ultimately, is DRM. RMSDK was only used because publishers demanded DRM and now vendors can't fully remove it because they have users, clients, and partners whose libraries and catalogues would be turned into opaque binary blobs.
But I have no doubt the code for RMSDK is a complete nightmare as well.
But I have no doubt the code for RMSDK is a complete nightmare as well.