Not only that, there are additions to the Carbon API set that are only available in Mac OS X and not Mac OS 9 via CarbonLib. An app developer who wants to take advantage of these features will have a hard time keeping their app running on 9 at the same time. And since Apple is no longer updating CarbonLib, this discrepancy between CarbonLib on 9 and Carbon on OS X is only going to get wider. Adobe has already pretty much decided the next major revisions of their apps will be for Mac OS X only, despite the fact that they will still be Carbon.
While I'm sure most programmers believe this, it simply isn't true.
Another poster pointed out that early Macs did pretty much everything people wanted computers to do at the time. They were far more capable than their PC counterparts. Yet they were very easy to use -- far easier than anything else available at the time.
The sad thing is that I have to go all the way back to the original Macintosh just to find something that disproves this strange notion that power and ease of use are incompatible. There has been very little effort since then to find the same kind of elegant solutions. People have actually fooled themselves into thinking that it's impossible! They acutally believe this false dichotomy of "power or ease, can't have both".
Certainly, it's hard coming up with ideas as good the original Mac. It takes a lot of work. It's much easier to simply say "it's impossible" than to search for new ways of dealing with problems that are powerful, elegant, and simple. But history shows it can be done.
You think your pathetic handwaving counts as "proof"? Wow, you're even more delusional than I thought. Well, you just keep on telling yourself that DeCSS isn't primarily used for stealing shit. You might as well still believe in Santa Claus.
People who download rips count, too. There would be no rips if it weren't for DeCSS.
And since you're making silly demands about things like VCR analogies (one notch below car analogies on the all-time stupidest computer argument fallacies list), how about you prove there is even one person who uses Linux to watch DVDs.
Are you actually convinced there are more people engaging in Fair Use than there are kiddiez downloading unauthorized rips? Wow, welcome to the land of make believe!
No matter how many times "the man" says DeCSS is for piracy, it just isn't true.
HAHAHA! Okay, whatever.
The primary use of DeCSS was, is, and will continue to be -- to gain access to the video and audio data so people can make and share DivX;-) rips. It most certainly is for piracy, and everybody knows it.
If you think Safari "beats the pants off" the Mac version of IE in "correctness", you haven't been paying attention. IE for Mac OS X is fully CSS compliant, while Safari is not.
PropCycle was more than just fun, it was brilliant! I would hog that game for at least 15-20 minutes every time I went to Dave and Buster's until they took it out. It was really immersive, too. The last level gave me a bit of vertigo the first time I got to it.
I don't understand why there hasn't been a sequel. That was one of the most ingenious arcade games ever made. I'd love to have a home version of it.
Thank you. I agree completely about the Borg in First Contact. The whole "queen" bit was the biggest cop-out ever.
I sometimes think the only reason people say they liked First Contact is because they want to keep talking about the "even/odd ST movies are good/bad" thing, regardless of whether it actually continues to prove true or not.
Look in the appendix of this book and you'll find lots of info about various rarely used units of measure, such as Emprical Galleons, Nautical Smiles, hogsnouts, and ratsasses.
PDF is a subset of Postscript all right, but while Postscript contains the actual character values, PDFs only store glyphIDs.
Glyphs, not characters.
There is a difference. A big difference. Trying to turn glyphIDs back into characters may work sometimes, but it's certainly not guaranteed to work. Any glyphs that do not have cmap entries in the font will come out as garbage.
Adobe should certainly never have put the text selection tool into Acrobat Reader. It does not work half the time, and it has fooled people into thinking that PDFs contain text. They don't. They only contain the vector image data necessary to render the text.
It is a valid comparison, because all Mach-based OSes have to have servers sitting on top of the microkernel. It's not like MkLinux had some disadvantage that no other Mach-based OS has. The way it worked was the way Mach is supposed to be used.
Ever compare MkLinux and PPCLinux? Then you'll know that the slowdown is almost entirely Mach's fault. It's a piece of crap. The only reason Apple uses it is because it was written by one of their VPs. Anyone with any objectivity would have chosen a different kernel.
You bet it's trivial. Any font features, ligatures, or special glyphs will show up as pure garbage if you try to turn the glyphIDs back into characters.
PDF is an image description format, nothing more. It does not contain text. The glyphs->characters conversion works most of the time for most existing documents, but it would be quite easy to generate a PDF that could not be converted back into text, except through OCR.
Actually, rules against cell phones on planes have plenty to do with safety. Read this post for more info.
Re:LCDs work fine, with some small issues...
on
LCD Round-up
·
· Score: 1
I can't explain why you aren't seeing the blurring, other than to say you may not be looking hard enough. Try live scrolling white-on-black text. Even high-end LCDs show smearing.
I can assure you that no LCD currently on the market has a pixel response time anywhere near fast enough to display the high frame rates you mentioned. This is an undisputable fact, both on paper and in practice.
Slashdot Mirror
Not only that, there are additions to the Carbon API set that are only available in Mac OS X and not Mac OS 9 via CarbonLib. An app developer who wants to take advantage of these features will have a hard time keeping their app running on 9 at the same time. And since Apple is no longer updating CarbonLib, this discrepancy between CarbonLib on 9 and Carbon on OS X is only going to get wider. Adobe has already pretty much decided the next major revisions of their apps will be for Mac OS X only, despite the fact that they will still be Carbon.
Actually, he never says he wouldn't use Mac OS X.
While I'm sure most programmers believe this, it simply isn't true.
Another poster pointed out that early Macs did pretty much everything people wanted computers to do at the time. They were far more capable than their PC counterparts. Yet they were very easy to use -- far easier than anything else available at the time.
The sad thing is that I have to go all the way back to the original Macintosh just to find something that disproves this strange notion that power and ease of use are incompatible. There has been very little effort since then to find the same kind of elegant solutions. People have actually fooled themselves into thinking that it's impossible! They acutally believe this false dichotomy of "power or ease, can't have both".
Certainly, it's hard coming up with ideas as good the original Mac. It takes a lot of work. It's much easier to simply say "it's impossible" than to search for new ways of dealing with problems that are powerful, elegant, and simple. But history shows it can be done.
Even more sad are the people who I'm sure are reading the above comment, thinking it is serious, and agreeing with it.
You think your pathetic handwaving counts as "proof"? Wow, you're even more delusional than I thought. Well, you just keep on telling yourself that DeCSS isn't primarily used for stealing shit. You might as well still believe in Santa Claus.
And since you're making silly demands about things like VCR analogies (one notch below car analogies on the all-time stupidest computer argument fallacies list), how about you prove there is even one person who uses Linux to watch DVDs.
Are you actually convinced there are more people engaging in Fair Use than there are kiddiez downloading unauthorized rips? Wow, welcome to the land of make believe!
You've never heard of a "screener", have you?
Proven.
HAHAHA! Okay, whatever.
The primary use of DeCSS was, is, and will continue to be -- to gain access to the video and audio data so people can make and share DivX ;-) rips. It most certainly is for piracy, and everybody knows it.
If you think Safari "beats the pants off" the Mac version of IE in "correctness", you haven't been paying attention. IE for Mac OS X is fully CSS compliant, while Safari is not.
I don't understand why there hasn't been a sequel. That was one of the most ingenious arcade games ever made. I'd love to have a home version of it.
I sometimes think the only reason people say they liked First Contact is because they want to keep talking about the "even/odd ST movies are good/bad" thing, regardless of whether it actually continues to prove true or not.
Look in the appendix of this book and you'll find lots of info about various rarely used units of measure, such as Emprical Galleons, Nautical Smiles, hogsnouts, and ratsasses.
But he can't be the evil Picard, he doesn't have a goatee!
How about this?
When programmers are starving because it's no longer economically viable to write software for a living, I'm sure you'll have another excuse ready.
Unlike GeekPAC, this organization (AOTC) actually has a name you can say out loud without snickering. That's at least one thing they're doing right.
He didn't say it is, he just said 52 bytes was "normal", which it is.
PDF is a subset of Postscript all right, but while Postscript contains the actual character values, PDFs only store glyphIDs.
Glyphs, not characters.
There is a difference. A big difference. Trying to turn glyphIDs back into characters may work sometimes, but it's certainly not guaranteed to work. Any glyphs that do not have cmap entries in the font will come out as garbage.
Adobe should certainly never have put the text selection tool into Acrobat Reader. It does not work half the time, and it has fooled people into thinking that PDFs contain text. They don't. They only contain the vector image data necessary to render the text.
It is a valid comparison, because all Mach-based OSes have to have servers sitting on top of the microkernel. It's not like MkLinux had some disadvantage that no other Mach-based OS has. The way it worked was the way Mach is supposed to be used.
Ever compare MkLinux and PPCLinux? Then you'll know that the slowdown is almost entirely Mach's fault. It's a piece of crap. The only reason Apple uses it is because it was written by one of their VPs. Anyone with any objectivity would have chosen a different kernel.
You bet it's trivial. Any font features, ligatures, or special glyphs will show up as pure garbage if you try to turn the glyphIDs back into characters.
PDF is an image description format, nothing more. It does not contain text. The glyphs->characters conversion works most of the time for most existing documents, but it would be quite easy to generate a PDF that could not be converted back into text, except through OCR.
Actually, rules against cell phones on planes have plenty to do with safety. Read this post for more info.
I can assure you that no LCD currently on the market has a pixel response time anywhere near fast enough to display the high frame rates you mentioned. This is an undisputable fact, both on paper and in practice.