Readit NewsExternally it had 16 bits for databus and 24 bits for addresses. That is why we later got the 32 bit clean ROMs as Apple used the upper unused 8 address bits for flags.
And for more evidence, the Z80 is referred to as an 8-bit processor but has a 4-bit ALU.
Soon after all that we got to use CD's, which made life a lot better.
Preshift-Table Graphics on your Apple by Bill Budge, with Gregg Williams and Rob Moore. A23 Move blocks of pixels across the screen with only 3K bytes of overhead
It's kind of hard to find, it's in the December 1984 Byte magazine, but an additional magazine at the end of the PDF, Bytes Guide to Apple.
At the time this was huge, Bill Budge was probably the most well known game programmer, so getting a look inside how he wrote code was a big thing.
Of course, as mentioned elsewhere, graphics is hard on the Apple II because of the complex memory layout due to Woz wanting to save a few chips. This can be contrasted with the Atari and Commodore computers that had custom chips that made graphics a lot easier.
https://archive.org/details/byte-magazine-1984-12/page/n397/...
"stole"?
They consumed publicly available material on the Internet
I am no fan of these billionaire capitalists and their henchpersons but condem them for their multitude of sins.
Consuming publicly available Internet resources is not one of them. IMO
The key technical change that broke Sonos was abandoning their reliable UPnP (Universal Plug and Play) system for device discovery in favor of mDNS, while also shifting from direct device communication to a cloud-based API approach. This new architecture made all network traffic encrypted and routed through Sonos cloud servers (even for local operations), adding significant overhead and latency, especially for older Sonos devices with limited processing power. They also switched from native platform-specific UX frameworks to a JavaScript-based interface while moving music service interactions through their cloud instead of direct SMAPI calls, resulting in slower performance and reduced functionality.
For a more extended discussion, see this excellent LinkedIn post from Andy Pennell, a principal engineer at Microsoft with a deep technical understanding of Sonos systems. He created one of the most successful third-party Sonos apps for Windows Phone and worked directly with Sonos on their official Windows Phone 8 app.
https://www.linkedin.com/pulse/what-happened-sonos-app-techn...
You only live once and you want to do it, so why not?
Because there might be some malware that’ll screw things up? Unlikely on a Mac.
Because there might be a lawsuit where your personal computer ends up as evidence? Almost certainly not going to happen.
Be cause it’s good evidence for a vindictive boss to use to fire you? Yeah whatever if somebody wants to fire you they’re going to do it anyway.
If you can accept that this is a weird thing to do and might have some risk associated with it, go nuts.
But in my new job I'm doing work on my personal laptop. It started because, I travel by plane to work regularly. I was carrying three laptops, my personal one, my work one, and one provided by my current client. It was just so much easier to combine everything into one laptop and just carry that. It's working out really well. Before I was constantly moving from one laptop to another just to check messages.
I think doing work on your personal computer is less bad than having personal stuff on your work computer, I wouldn't do that.
These things would be important if they made products that actually work. My T14s Gen 3 AMD simply doesn’t work. Half the time I go to wake it from sleep, the firmware has crashed and I have to hard-reset it. I spent months trying to get Lenovo to fix this. They did replace the motherboard twice (once on-site, once shipped to them) and eventually replaced the entire laptop with a new one. None of this is useful when they can’t make a laptop that doesn’t crash while it sleeps.