Yeah even Microsoft's compiler aligns values on appropriate boundaries for performance reasons. DWORDs on DWORD boundaries etc. And if you want to pack the data structure to avoid the gaps in structures there are methods to do so via #pragma options. I think their complaining about what was done for performance reasons shows a great lack of overall understanding. More time researching and less time griping would have served them better.
You can also use TheC64 (Max) as a USB keyboard to the PC to use in Vice if you decide you want the keyboard and want to take advantage of some of the functionality of the emulators. I found a page that shows how to add a USB connector to the Max to allow this.
It's taught me to worry about people who happily volunteer for difficult tasks. I used to think they were troopers, now I see more and more of them as having a high pain tolerance, and I don't mean that as a compliment.
Pain in information and they throw away a lot. It's a form of job security, and not a particularly benign kind.
Our job is to replace painful processes with code. If you can't do that you aren't fulfilling the basic premise of your profession.
I miss the documentation that was part of Microsoft MSDN subscription. I now work in a sandboxed environment and cannot access help for the APIs from within that environment so something that I can download in it's entirety and get into that environment would be ideal.
I have asked it to write code. The code looked reasonable but did not work (using a non-existent API or library). I said the library XXX doesn't exist. And it would respond with an apology and a new solution that maybe worked maybe didn't. Sometimes it could pull off a save eventually.
i keep getting it to write code that works but then its example usage makes no sense. i point out the code is write but the example it gives is wrong and it can almost never fix it. version 4.
When I was at Microsoft during the time I had X86, Alpha, MIPS, PPC (for a short time) and Itanium. We only did the builds for Itanium once in a while because the developers and the testers shared the expensive hardware. I believe the only versions of the product (Systems Management Server) were for the X86, Alpha and MIPS.
Those bad boys (9-track tapes) could easily hold 40MB which was a few hundred times bigger than floppy discs of the 8-bit age and would add up to quite a few compact cassettes. (As expensive as it was, I was so happy to switch to floppy disk for my TRS-80 Color Computer because restoring stuff I saved on a cassette was always hit or miss.)
Mainframes in 1968 were handling much bigger data sets than you could handle with a micro until 1990 or so.
There is no way you could fit 40MB into an audio tape, even when using the fastest fast loader [1]. 40MB is 3.2e8 bits, which means you'd need a transfer rate of ~60kbps even with a 90-minute tape. 8 bit computers could do 1-2kbps at best.
The idea was better than the execution sadly. I had one of those mice and it never really felt like you gained much with the vibrations etc. I'm sure had it been more widely adopted it might have become much closer to the promise.
