It's the Digital Rebel in the US, the Kiss Digital in Japan, and the 300D elsewhere. Hang around photography forums a bit, and you'll find people tend to use DR and 300D interchangably.
I tend to refer to mine by 300D in that type of a situation (easier to type, sounds better;-)) and as a Rebel when I'm talking to friends in person. It really just comes down to the person talking about it.
Actually, if I were spending $4000 on a computer, I'd be annoyed to see IDE cables. For that price, I'd *expect* Plextor SATA optical drives, but that's just me.:-P
It was actually by several weeks on the Mac Mini, not a day. Asteroid, on the other hand, is a *STILL* unannounced product, four months after the leak. I'd hardly call that 'ready to go, just waiting to be unveiled.'
Furthermore, Apple has C&D'd ThinkSecret on trade secret grounds numerous times in the past year and a half. It was apparent that ThinkSecret has/had sources inside of Apple, who were consistently violating their NDAs.
I honestly think this is about Apple trying to plug their holes before they cause any more damage. This isn't an isolated case, and at this point, I can't blame them for persuing the matter.
If you had a video camera at the scene of the crime and were filming, I'm fairly sure you could expect to be subpoenaed. I don't see a huge difference in that and the type of evidence Apple is seeking here.
Um, no. He didn't. He published very specific information that was only known internally to LIMITED numbers of people within Apple. There were also artist renditions and specifications involved (re: Asteroid), and they also published clear and specific information about the Mac mini.
In fact, if people could be bothered to read Judge Kleinberg's ruling, they'd find that at least one of the sites involved posted exact copies of presentation slides which were clearly watermarked "APPLE CONFIDENTIAL."
In other words, Apple had already made enough of a case regarding where this information had come from in order for the Judge to allow discovery to go forward.
Agreed. This is a great example of an industry taking on the 'adapt' side of 'adapt or die' that we often chastise the RIAA and MPAA for trying to ignore. It sounds like this lets users and the newspapers make out fairly well in the end, as long as they don't try to turn it into some sort of spyware-like system.
Yeah because apt doesn't resolve dependencies in the same manner as portage and the Debian software repositories are *clearly* so much smaller than Gentoo's. But I guess it doesn't count because it's binary and you don't waste time compiling, eh?
Gentoo was fun for about 3 months, and I did learn a lot from it. Portage is certainly neat, but it's nothing special. Fact is, 95%+ of any software I've wanted has been in the apt repositories, and just plain works. And I only have to wait for the package to download and untar, rather than however long it takes to compile.
So no, Ubuntu's not perfect, but essentially calling its package management crap while touting a very similar system with drawbacks of its own is just stupid.
Not only that, but try changing the dataset to the past 3 months or past month, and you'll see that Ubuntu has been averaging nearly 30% more hits per day than the next closest distribution.
It'd make sense that the 6 month number would be a bit off as Ubuntu is on a twice-a-year release schedule, with the first release having been 6 months ago now. (The version numbering scheme is Ubuntu Year.Month, hence Ubuntu 5.04).
So while Distrowatch may not be the best indicator of a distribution's popularity, it certainly seems to indicate that Canonical and crew are onto to something here.
You beat me to it. Direct linking to *two* 600+ MB isos on the front page of Slashdot? That's asking for disaster.
That said, I've got the torrent for both i386 and PPC going, can't wait to finally get this installed. I've run the dev builds of this on and off at different points, and it had definitely been shaping up to be a great, useful distribution.
What a load of BS, Try any recent kde or gnome based distro on anything slightly old and it you'll see its unusable, while linux itself runs fine i've yet to see a decent GUI, they're all obsessed with letting you configure your windows to look absolutely any way you want, when all anyone really wants is fast response time and a few reasonable config options.
Now *THAT* is a load of BS. My notebook uses a P3 1GHz, SDRAM, and i810 graphics, and runs Gnome perfectly acceptably. If a CPU that's going on 5 years old isn't 'slightly' old, I don't know what is.
And while I don't particularly care for KDE's interface, I have noticed that it's even snappier than Gnome is. If modern software running at a usable speed on a machine based of 5 year-old technology is 'unacceptably slow' I don't know what isn't.
It depends on the chipset, really. SiS and VIA still use a traditional two-chip design, while NVidia's NForce3 and NForce4 are single-chip designs, making the traditional north/southbridge terminology somewhat antiquated.
Intel *is* bringing the Pentium M to the desktop, they're just taking their time to phase it in slowly. The Pentium M's performance is really the reason Intel moved to a BMW-like model numbering system, after all.
The Pentium M does fair very well in most benchmarks (I truly feel it's a much better architechture than Netburst ever was), but it also has a relatively weak FPU, which hurts it in many multimedia content benchmarks, such as video encoding. Sort of amusing, as that's always been an Intel strongpoint over AMD in the past.
Fair enough. FWIW, I wasn't accusing you of playing a shill, if anything, it was meant to be a somewhat oblique compliment on your salesmanship.:-P
That said, I've bookmarked your site, and I'll be taking a look at it some time that's *not* 3:30 in the morning, and likely end up dropping you a line with a few questions.:-)
At any rate, yeah, we have strayed a bit off-topic here, but I think it's largely a matter of differing philosophies, and I enjoy the discussion of it as well. That's really the only reason I brought up the comparison to Photoshop's widget set, just pointing out another approach to it, since, as I understand it, Photoshop's codebase is still largely made up of very old C code at this point, which certainly contributes to bloat. I just didn't see it as a particularly solid example of OOP bloat.
Anyway, like I said, it's getting late here, and I'd likely continue on, but my brain's having none of that. I'll take a closer look at your documentation and get back to you with any questions I might have.
I actually own a Geo Metro as a daily driver. The MSP was just an easy example, and far from the best - I don't own one, I'm just familiar with them.
It's honestly more a matter of interests in this case. I'm slowly but surely getting more into autocross, and a Firebird, while quick, is a landboat in comparison to the MSP's handling.
Either way, my point was that a smaller car that's considerably faster than almost any SUV on the road and was tuned at the factory with very little regard for fuel efficiency will still trump the said SUV in fuel economy. If I wanted a more extreme example of this I could pick the Dodge SRT-4 in the same price range or a Subaru Impreza STi for a bit more. The STi is a potential Vette killer, and still makes better MPG than any H2 on the road. That was all the point there was to my post.:-)
Warty apparently had some dual boot issues. I ran it fine on its own on several PCs, but when I tried to set up dual boot on this Powerbook, it thrashed the partition map something unbelievably fierce. We tried 5 or 6 data recovery programs on it and nothing would find *any* files on the drive.
That said, I installed the Hoary preview on here and it seemed to take fine. I'm really looking forward to April 6.:-)
Ah you just had to go and invoke the Suzuki Sportbike, didn't you? I finally picked up a DSLR camera, the sport bike is next on my list of cool things to buy.:-P
Again, using our own app as an example, it is about 4 megs in size. It is considerably more powerful and featureful than Photoshop is. And it is just a fraction of the executable size, much, much faster running, and endures far fewer software failures than does Photoshop. This is in no small part due to a whole raft of stuff from the OS that we re-wrote and internalized into the application.
Hyperbole aside, Photoshop runs on both Windows and OS X and behaves in a very similar manner on both specifically because Adobe did implement much of the UI with their own code.
The fact that it runs on both Windows and Mac would also suggest that any problems Photoshop has are not related to MS' new-fangled OOP APIs. But you certainly do an impressive job of talking your product up against an 800lbs competitor.:-P
I don't understand this argument. If this were the case, why are big, heavy, and above all else *slow* SUVs selling so well? I'd say it's a 'bigger is better' syndrome more so than having anything to do with real power.
A MazdaSpeed Protege will sprint to 60 in 6.9 seconds, gets 30 miles to the gallon on the highway, and does this with a 2.0L engine. It's hard to say that's not relatively 'beefy.'
It's a bit of an extreme example, sure, but the H2 which seems to be selling like mad is just as extreme in the other direction - you'd be amazingly lucky to see 60 inside of 9 seconds, while burning up over twice as much fuel.
I think saying that Americans have an obsession with power is a bit of a cop out. It's an obsession with size, plain and simple.
Seriously, I'm going to be busy the next few weeks. Windows XP 64, OS 10.4 Tiger, and Ubuntu 5.04 all within a few weeks of each other. It's just about geek overload.:-)
Just curious as to what's not working in 16 bit mode in Photoshop?
I just bought an EOS 300D earlier this week while Dell was clearing them out and plan to be shooting primarilly in RAW so that I can edit in 16 bit. I'd just like to get an idea of what I should go ahead and expect to not be there.
It'd definitely be great, as it'll finally allow for running filters without bruising the original pixels, and personally, I think would give me a bit more wiggling room to work creatively with an image.
I also imagine it'll be pretty CPU intensive, and that could be a huge part of why it hasn't been done before - the fact that *ANY* change you make to an image will have to be run through the filter at the same time could cause things to really start to bog down, I'd imagine.
Coincidently, I installed GIMP 2.2 today to give it another try as I tend to do every few months. I honestly want to like the program, but again, I got frustrated with the interface within 15 minutes and gave up. Granted, I'm saavy with Photoshop, so I'm sure that's a factor, but I remember hating the interface since well before I learned to use Photoshop. I'll definitely be giving this a try in the morning.
Ars' video samples are really subpar for this type of device. Slashdot covered a story on a nearly identical setup here about a year ago and the results are *much* more impressive. As with anything, experience and practice make all the difference in the world. Ars is a great site, but film isn't exactly their focus.:-)
Slashdot Mirror
It's the Digital Rebel in the US, the Kiss Digital in Japan, and the 300D elsewhere. Hang around photography forums a bit, and you'll find people tend to use DR and 300D interchangably.
;-)) and as a Rebel when I'm talking to friends in person. It really just comes down to the person talking about it.
I tend to refer to mine by 300D in that type of a situation (easier to type, sounds better
Actually, if I were spending $4000 on a computer, I'd be annoyed to see IDE cables. For that price, I'd *expect* Plextor SATA optical drives, but that's just me. :-P
Please don't let Steve Gibson know about this, lest the web be subected to even more BRIGHT RED ALL CAPS TEXT.
It was actually by several weeks on the Mac Mini, not a day. Asteroid, on the other hand, is a *STILL* unannounced product, four months after the leak. I'd hardly call that 'ready to go, just waiting to be unveiled.'
Furthermore, Apple has C&D'd ThinkSecret on trade secret grounds numerous times in the past year and a half. It was apparent that ThinkSecret has/had sources inside of Apple, who were consistently violating their NDAs.
I honestly think this is about Apple trying to plug their holes before they cause any more damage. This isn't an isolated case, and at this point, I can't blame them for persuing the matter.
If you had a video camera at the scene of the crime and were filming, I'm fairly sure you could expect to be subpoenaed. I don't see a huge difference in that and the type of evidence Apple is seeking here.
In fact, if people could be bothered to read Judge Kleinberg's ruling, they'd find that at least one of the sites involved posted exact copies of presentation slides which were clearly watermarked "APPLE CONFIDENTIAL."
In other words, Apple had already made enough of a case regarding where this information had come from in order for the Judge to allow discovery to go forward.
Agreed. This is a great example of an industry taking on the 'adapt' side of 'adapt or die' that we often chastise the RIAA and MPAA for trying to ignore. It sounds like this lets users and the newspapers make out fairly well in the end, as long as they don't try to turn it into some sort of spyware-like system.
Yeah because apt doesn't resolve dependencies in the same manner as portage and the Debian software repositories are *clearly* so much smaller than Gentoo's. But I guess it doesn't count because it's binary and you don't waste time compiling, eh?
Gentoo was fun for about 3 months, and I did learn a lot from it. Portage is certainly neat, but it's nothing special. Fact is, 95%+ of any software I've wanted has been in the apt repositories, and just plain works. And I only have to wait for the package to download and untar, rather than however long it takes to compile.
So no, Ubuntu's not perfect, but essentially calling its package management crap while touting a very similar system with drawbacks of its own is just stupid.
Not only that, but try changing the dataset to the past 3 months or past month, and you'll see that Ubuntu has been averaging nearly 30% more hits per day than the next closest distribution.
It'd make sense that the 6 month number would be a bit off as Ubuntu is on a twice-a-year release schedule, with the first release having been 6 months ago now. (The version numbering scheme is Ubuntu Year.Month, hence Ubuntu 5.04).
So while Distrowatch may not be the best indicator of a distribution's popularity, it certainly seems to indicate that Canonical and crew are onto to something here.
You beat me to it. Direct linking to *two* 600+ MB isos on the front page of Slashdot? That's asking for disaster.
That said, I've got the torrent for both i386 and PPC going, can't wait to finally get this installed. I've run the dev builds of this on and off at different points, and it had definitely been shaping up to be a great, useful distribution.
Now *THAT* is a load of BS. My notebook uses a P3 1GHz, SDRAM, and i810 graphics, and runs Gnome perfectly acceptably. If a CPU that's going on 5 years old isn't 'slightly' old, I don't know what is.
And while I don't particularly care for KDE's interface, I have noticed that it's even snappier than Gnome is. If modern software running at a usable speed on a machine based of 5 year-old technology is 'unacceptably slow' I don't know what isn't.
There's a desktop version of the Pentium M core on Intel's roadmap, and has been for some time now. So the answer to that one is "yes".
It depends on the chipset, really. SiS and VIA still use a traditional two-chip design, while NVidia's NForce3 and NForce4 are single-chip designs, making the traditional north/southbridge terminology somewhat antiquated.
Intel *is* bringing the Pentium M to the desktop, they're just taking their time to phase it in slowly. The Pentium M's performance is really the reason Intel moved to a BMW-like model numbering system, after all.
The Pentium M does fair very well in most benchmarks (I truly feel it's a much better architechture than Netburst ever was), but it also has a relatively weak FPU, which hurts it in many multimedia content benchmarks, such as video encoding. Sort of amusing, as that's always been an Intel strongpoint over AMD in the past.
Fair enough. FWIW, I wasn't accusing you of playing a shill, if anything, it was meant to be a somewhat oblique compliment on your salesmanship. :-P
:-)
That said, I've bookmarked your site, and I'll be taking a look at it some time that's *not* 3:30 in the morning, and likely end up dropping you a line with a few questions.
At any rate, yeah, we have strayed a bit off-topic here, but I think it's largely a matter of differing philosophies, and I enjoy the discussion of it as well. That's really the only reason I brought up the comparison to Photoshop's widget set, just pointing out another approach to it, since, as I understand it, Photoshop's codebase is still largely made up of very old C code at this point, which certainly contributes to bloat. I just didn't see it as a particularly solid example of OOP bloat.
Anyway, like I said, it's getting late here, and I'd likely continue on, but my brain's having none of that. I'll take a closer look at your documentation and get back to you with any questions I might have.
I actually own a Geo Metro as a daily driver. The MSP was just an easy example, and far from the best - I don't own one, I'm just familiar with them.
:-)
It's honestly more a matter of interests in this case. I'm slowly but surely getting more into autocross, and a Firebird, while quick, is a landboat in comparison to the MSP's handling.
Either way, my point was that a smaller car that's considerably faster than almost any SUV on the road and was tuned at the factory with very little regard for fuel efficiency will still trump the said SUV in fuel economy. If I wanted a more extreme example of this I could pick the Dodge SRT-4 in the same price range or a Subaru Impreza STi for a bit more. The STi is a potential Vette killer, and still makes better MPG than any H2 on the road. That was all the point there was to my post.
Warty apparently had some dual boot issues. I ran it fine on its own on several PCs, but when I tried to set up dual boot on this Powerbook, it thrashed the partition map something unbelievably fierce. We tried 5 or 6 data recovery programs on it and nothing would find *any* files on the drive.
:-)
That said, I installed the Hoary preview on here and it seemed to take fine. I'm really looking forward to April 6.
Ah you just had to go and invoke the Suzuki Sportbike, didn't you? I finally picked up a DSLR camera, the sport bike is next on my list of cool things to buy. :-P
As another poster noted, I said on the highway. Around town, a MSP will get around 24MPG, which is *STILL* better than any SUV I know of.
Hyperbole aside, Photoshop runs on both Windows and OS X and behaves in a very similar manner on both specifically because Adobe did implement much of the UI with their own code.
The fact that it runs on both Windows and Mac would also suggest that any problems Photoshop has are not related to MS' new-fangled OOP APIs. But you certainly do an impressive job of talking your product up against an 800lbs competitor.
I don't understand this argument. If this were the case, why are big, heavy, and above all else *slow* SUVs selling so well? I'd say it's a 'bigger is better' syndrome more so than having anything to do with real power.
A MazdaSpeed Protege will sprint to 60 in 6.9 seconds, gets 30 miles to the gallon on the highway, and does this with a 2.0L engine. It's hard to say that's not relatively 'beefy.'
It's a bit of an extreme example, sure, but the H2 which seems to be selling like mad is just as extreme in the other direction - you'd be amazingly lucky to see 60 inside of 9 seconds, while burning up over twice as much fuel.
I think saying that Americans have an obsession with power is a bit of a cop out. It's an obsession with size, plain and simple.
Seriously, I'm going to be busy the next few weeks. Windows XP 64, OS 10.4 Tiger, and Ubuntu 5.04 all within a few weeks of each other. It's just about geek overload. :-)
Just curious as to what's not working in 16 bit mode in Photoshop?
I just bought an EOS 300D earlier this week while Dell was clearing them out and plan to be shooting primarilly in RAW so that I can edit in 16 bit. I'd just like to get an idea of what I should go ahead and expect to not be there.
It'd definitely be great, as it'll finally allow for running filters without bruising the original pixels, and personally, I think would give me a bit more wiggling room to work creatively with an image.
I also imagine it'll be pretty CPU intensive, and that could be a huge part of why it hasn't been done before - the fact that *ANY* change you make to an image will have to be run through the filter at the same time could cause things to really start to bog down, I'd imagine.
Coincidently, I installed GIMP 2.2 today to give it another try as I tend to do every few months. I honestly want to like the program, but again, I got frustrated with the interface within 15 minutes and gave up. Granted, I'm saavy with Photoshop, so I'm sure that's a factor, but I remember hating the interface since well before I learned to use Photoshop. I'll definitely be giving this a try in the morning.
Ars' video samples are really subpar for this type of device. Slashdot covered a story on a nearly identical setup here about a year ago and the results are *much* more impressive. As with anything, experience and practice make all the difference in the world. Ars is a great site, but film isn't exactly their focus. :-)