4 ms·
The "Why" section in the Readme doesn't quite explain the need for this. Can someone shed light on how and why this is useful Thanks
by mankash666 10y ago
The "Why" section in the Readme doesn't quite explain the need for this. Can someone shed light on how and why this is useful
Thanks
- kelvin0 10y agoWhen you have to ask "Why", you usually are not part of 'target audience' for this type of thing :) All jokes aside,this is a pretty big achievement for a given programmer to complete and denotes quite a bit of technical chops on many level (hardware, systems, OS, and web dev).
- mankash666 10y agoAh ok - "if you're not the target customer, no need to explain the product to you". Great mantra to live life by! You don't happen to work in marketing, do you?
- jlappi 10y ago>customer You see, that's where you're way off base. Not everything shown here is going to be a 'product'; people often like to learn by doing, and showing what they create.
- khedoros 10y agoWhy is everything a "product"? Why does everything have to be marketed? Why does there have to be a need for something, for it to be built and to be noteworthy? This looks like a cool personal project, built by the author as a learning experience, with a convenient API to manipulate the machine that's being simulated. If that doesn't tell you enough about why it exists, then I don't know what to tell you besides "nothing to see here".
- omegaham 10y agoMost of this kind of stuff is done for intellectual gratification. It's playing; the tools are just more sophisticated, and it takes more brainpower than usual.
- ghshephard 10y agoI thought they were pretty explicit: "I decided to work on this as a fun project and learn something about the x86 architecture." That seems to be more than enough reason to me.