Editing Talk:Emulation accuracy
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 4: | Line 4: | ||
: As the author of CLK, I agree entirely. Being a cycle-timed emulator just means that your implementation has avoided a particular pitfall, not that it necessarily has worth. The meaning of accuracy promoted by this page seems to be more about establishing genotypes than creating appropriate user expectations. It's also troubling as an author as you want to be able to say 'my emulator seeks to be cycle accurate' to explain that you are being properly conscientious, but you often end up sounding like you're making promises you can't keep because the meaning gets conflated. — [[User:Tommy|Tommy]] ([[User talk:Tommy|talk]]) 10:11, 6 March 2018 (EST) | : As the author of CLK, I agree entirely. Being a cycle-timed emulator just means that your implementation has avoided a particular pitfall, not that it necessarily has worth. The meaning of accuracy promoted by this page seems to be more about establishing genotypes than creating appropriate user expectations. It's also troubling as an author as you want to be able to say 'my emulator seeks to be cycle accurate' to explain that you are being properly conscientious, but you often end up sounding like you're making promises you can't keep because the meaning gets conflated. — [[User:Tommy|Tommy]] ([[User talk:Tommy|talk]]) 10:11, 6 March 2018 (EST) | ||
− | |||
− | |||
− | |||
− |