
Re: "amid growing adoption of competing architectures"
not sure if sarcasm or not.....
17 publicly visible posts • joined 18 Feb 2008
>>I started to read Simon's stories during my formative years.
If I had discovered BOFH during my college years (when I worked as a computer lab assistant, teaching Word 6(66) to students who barely knew how to type and had waited 'til the eleventh hour to start writing their reports) I'd be in prison.
>>Or they may do a repeat and have "Five Level Cell (FLC)" and do the +1 bit on the six-banger, as otherwise it will have a collision with Single Level Cell.
HLC (Hex Level Cell).
Seven is the real challenge. Best I can come up with is ZLC (Yiddish's "zibn"). But we probably have plenty of time to come up with something better before such things actually get to market.
>>When I watch medical things, I've no idea what they're talking about most of the time, but it sounds 'about right' and fits in with the flow of things...
My sister works for a medical test collection company-- they take the test tubes from the hospitals and clinics, process them and send them out to the appropriate labs. She loved 'House MD', but would scream stuff like "No, you can't do that test in 15 minutes! There's exactly one lab that does that test and they're in Minnesota! You'd be lucky to get it back in 15 DAYS!"
>>Didn't BOFH do this many years back? Except with a Laptop full of batteries?
From "The Bastard Goes to the Trade Show":
"The 31 hefty nicad batteries that make up almost the entire inside of my 'laptop' pour grunt into a tripling inverter which in turn supplies RICH, CHUNKY VOLTS to alternate pins on the 'SCSI' bus, whilst emitting a dull 'uuurk' sound."
I'm still waiting for the opportunity to use the phrase "RICH, CHUNKY VOLTS" somewhere in my life. This doesn't count.
re: (* Seriously. Been there, done that. 6809 circa 1980.)
I've done something like that. 6809 on a Tandy CoCo3, early 1990s. I had bought an assembly-language tutorial book at Radio Shack, but was unable to get EDTASM, which it was written for. Luckily, the book had a table of opcodes, as well as object code printouts in all its code examples, so I taught myself how to hand-assemble.
I did all that to try to get some resemblance of speed out of the CoCo3's "hi-res" graphics modes (a whopping 320x200 in 16 colors). The stock HGET and HPUT blitter commands were way too slow (which is what happens when the original programmers' properly "structured" program calls 3 subroutines for each byte it's copying to the frame buffer). I also added transparency and horizontal & vertical flipping. And tile-based backgrounds. And double-buffering. I never actually did built the game I wanted to make; I had more fun building the tools. (for certain definitions of "fun".)
I like XKCD's tribute: a spinning beach ball. "There's always the hope that if you sit and watch for long enough, the beachball will vanish and the thing it interrupted will return."
Another interpretation I've read: "Steve Jobs is no longer responding to external events."
Pfft-- I had a CoCo 2 and 3, and while the 6809 was a superior 8-bit CPU (it was able to do some 16-bit ops), it was entirely on its own. No sprite chip-- I taught myself assembly to create a screaming fast (compared to the stock CoCo3 BASIC HGET/HPUT ) blitter. It could do transparency, even. "Audio" meant plugging values into a particular address (linked to a 6-bit DAC) at regular intervals (no DMA here), so forget about playing any sound more complex than blips and clicks if you want to do anything else at the same time.
Although there is some political wrangling and corporate pissing-matches going on here, I think the lack of Flash on the iPhone and iPad is mostly due to the fact that Flash is so CPU-intensive, it kills battery life:
http://adobegripes.tumblr.com/post/231806385/adobe-gets-bitchy-over-the-iphone-and-flash-bit
http://www.reddit.com/r/apple/comments/a0cqa/fight_for_flash_on_the_iphone_gets_dirty/
"The [Flash] prototype allowed the iPhone to have less than half an hour of battery life using flash."
A version of Flash that uses the GPU might be easier on the battery, but that would require actual effort on Adobe's part.
Not that I have any need for an iPad at the moment (I had hoped for a full-fledged Tablet PC that could run OS X and Photoshop, but I'll just have to limp along with my XP tablet for a bit longer).