Three inch CDs are popular in Japan. They never took off in the US, but I've never seen a CD player incapable of playing them, including slot-loading CD players.
Yeah, this is offtopic. But why are we letting Adobe off the hook? Katz doesn't even mention Adobe in the context of the agressor. The FBI/DOJ/CIA conspiracy is just obeying its charter. Adobe corporation put the man in jail. They've said they wouldn't press charges, and recommended he be released. So fucking what? Adobe hasn't apologized, and they are not paying Dmitry's legal expenses. Their hands are not clean, why shouldn't they be punished?
Someone wanna tell me why anyone should care?.NET sounds like a lot of Microsoft hot air designed solely to remove Java from the marketplace.
For instance: What compelling features does it offer the customer? Why would I want those features, as a customer?
Miguel seems to think it's a way to escape the GTK/GNOME/Bonobo architectural limitations, from what I've read -- but so what? Why not fix GTK/GNOME/Bonobo instead?
Seriously, please clue me in, cause I don't understand the fuss.
Maybe it's just a poor remastering job (my perception is based on the DVD), but I think the soundtrack is the worst part of Tron. It actively detracts from the visuals.
The best thing they could do would be to hand the movie to Vince Clarke to rescore.
Or was the original soundtrack significantly better than what appears on the current DVD?
When you have minimal responsibilities and minimal money, you both can afford to answer the phone yourself, and can't afford to hire someone to do it for you.
The real question is whether, when the Kompany is rather larger, the guy will still ocassionally be answering the phones to keep in touch with his customers.
Not necessarily. All modern CD-ROM drives also allow you to extract digital audio data directly. Not only that, but the information extracted has already been through the error-correction circuitry of the CD-ROM drive (if you provided the right parameters to the command, which can vary per-drive).
This is how software equalizers work (they extract the digital data, modify it, and send it to your sound card in digital form), which is why many audio CD players use digital data extraction.
As Guy Kawasaki (ceo Garage.com) said, "Don't Worry, Be Crappy." You have to ship to make money. You have to get Revision One out there so you can see HOW to make it better, instead of noodling around in the workshop forever.
Guy's point is that you have to ship, not that you have to ship crap. His standard of crap is different: there's a major difference between "crappy" and "unusable/untenable." You still have to ship within acceptable parameters for the market and time period.
For example, Guy means that the original Macintosh was crappy because it was short on memory short on storage space, and offered no expansion slots, or that the RCA VideoDisc was crappy because it had no stereo sound and no "searching" features. The Mac shipped too early, but was still within acceptable parameters of crappiness and was a relative success; the VideoDisc shipped too late, was not acceptable in the light of VCRs (with recording features!) and the videophile LaserDisc, and was a major failure.
because you are ignorant?
on
Why not Ruby?
·
· Score: 1
How exactly does Python suddenly qualify as a language for pragmatists? The supposed elegance of Python was/is a barrier to its being favored over Perl.
One thing that no one has mentioned in this discussion is that Ruby implements Perl to a significant degree -- (very) trivial scripts can be compatible with both Perl and Ruby.
Another important thing to keep in mind is that no one is forcing you to use iterators in Ruby, just as no one will force you to use them in Python 2.2. You can write a for-loop if you want. It's significantly easier to write an iterator, however, in terms of time and resulting code complexity.
It's not that I don't understand it. I do completely understand the idea of an iterator (with a name like that, who couldn't?)
No, you don't. Really. You perhaps understand the concept of iteration, but not the concept of an "iterator" as implemented by languages such as Sather, Ruby, and (if I recall correctly), a forthcoming version of Python.
I mean, you must be joking:
as beautiful as "pure" languages like Java and Haskell and Ruby are,
multiple programming paradigms well, like O'Caml, and Lisp, and Python.
GMO food, such as modified corn, is bad, at least until proven otherwise. We don't know what the long term effects are, but we do suspect, and we do know that it is "viral." We must treat any plant that behaves like an extremely healthy weed with suspicion.
Biotech, such as electronic muscle replacements embedded in the human body, is good. Think the blind dude from ST:TNG.
The mainstream press can't seem to get the difference straight.
Re:WxWindows is the de facto cross platform Standa
on
Qt for Mac
·
· Score: 1
The choices actually aren't all that clear, my friend, unless you consider "Windows 98", "Windows 2000", and "Linux" to be the only platforms worth crossing (fair enough).
Ignoring Tk (as we all should:), a supported version of Qt may be the first real cross-platform framework to successfully cross to the Mac. gtk+ and wxWindows aren't useful on the Mac yet. That will give some developers a powerful incentive to use Qt.
My money is ultimately on gtk+ due to inertia, GIMP and free-as-in-speech-dom, but I definitely prefer Qt's (and, for that matter, wxWindows's) API.
A hard drive was hardly an essential component in 1984. The 400k drive of the original Macintosh was adequate and compared favorably to other home/small office computers at the time.
The original Mac's 128k of RAM was the truly inadequate part. And Sculley's unnecessary increase of the base price of the Mac ($2599, IIRC) didn't help at all.
NeXT, on the other hand, was a different story. They very much hung themselves with the slow-optical-drive-and-no-floppy NeXTCube.
1988 was too early to pull the floppy drive.
The key in advancing your hardware is detecting when the state of the art is advanced enough to support your desires. The floppyless, USB-promoting iMac arrived at the right time (or maybe even a little late).
My HO is that it's a year too early to be selling CRT-less Macs (although I'm using a PowerBook G4...), but, unlike Apple, I don't hold any Samsung stock, so what do I necessarily know?
Rather than modding that comment up, could we have a corroborating link? Facts that "I remember reading somewhere" are likely reliable enough to be considered worthy of a Slashdot front-page story...
Slashdot Mirror
Three inch CDs are popular in Japan. They never took off in the US, but I've never seen a CD player incapable of playing them, including slot-loading CD players.
Yeah, this is offtopic. But why are we letting Adobe off the hook? Katz doesn't even mention Adobe in the context of the agressor. The FBI/DOJ/CIA conspiracy is just obeying its charter. Adobe corporation put the man in jail. They've said they wouldn't press charges, and recommended he be released. So fucking what? Adobe hasn't apologized, and they are not paying Dmitry's legal expenses. Their hands are not clean, why shouldn't they be punished?
For instance: What compelling features does it offer the customer? Why would I want those features, as a customer?
Miguel seems to think it's a way to escape the GTK/GNOME/Bonobo architectural limitations, from what I've read -- but so what? Why not fix GTK/GNOME/Bonobo instead?
Seriously, please clue me in, cause I don't understand the fuss.
The best thing they could do would be to hand the movie to Vince Clarke to rescore.
Or was the original soundtrack significantly better than what appears on the current DVD?
Id did get (IMHO, unwarranted) criticism for releasing old source. Check the archives.
The real question is whether, when the Kompany is rather larger, the guy will still ocassionally be answering the phones to keep in touch with his customers.
This is how software equalizers work (they extract the digital data, modify it, and send it to your sound card in digital form), which is why many audio CD players use digital data extraction.
Guy's point is that you have to ship, not that you have to ship crap. His standard of crap is different: there's a major difference between "crappy" and "unusable/untenable." You still have to ship within acceptable parameters for the market and time period.
For example, Guy means that the original Macintosh was crappy because it was short on memory short on storage space, and offered no expansion slots, or that the RCA VideoDisc was crappy because it had no stereo sound and no "searching" features. The Mac shipped too early, but was still within acceptable parameters of crappiness and was a relative success; the VideoDisc shipped too late, was not acceptable in the light of VCRs (with recording features!) and the videophile LaserDisc, and was a major failure.
One thing that no one has mentioned in this discussion is that Ruby implements Perl to a significant degree -- (very) trivial scripts can be compatible with both Perl and Ruby.
Another important thing to keep in mind is that no one is forcing you to use iterators in Ruby, just as no one will force you to use them in Python 2.2. You can write a for-loop if you want. It's significantly easier to write an iterator, however, in terms of time and resulting code complexity.
It's not that I don't understand it. I do completely understand the idea of an iterator (with a name like that, who couldn't?)
No, you don't. Really. You perhaps understand the concept of iteration, but not the concept of an "iterator" as implemented by languages such as Sather, Ruby, and (if I recall correctly), a forthcoming version of Python.
I mean, you must be joking:
as beautiful as "pure" languages like Java and Haskell and Ruby are,
multiple programming paradigms well, like O'Caml, and Lisp, and Python.
Biotech, such as electronic muscle replacements embedded in the human body, is good. Think the blind dude from ST:TNG.
The mainstream press can't seem to get the difference straight.
Ignoring Tk (as we all should :), a supported version of Qt may be the first real cross-platform framework to successfully cross to the Mac. gtk+ and wxWindows aren't useful on the Mac yet. That will give some developers a powerful incentive to use Qt.
My money is ultimately on gtk+ due to inertia, GIMP and free-as-in-speech-dom, but I definitely prefer Qt's (and, for that matter, wxWindows's) API.
The original Mac's 128k of RAM was the truly inadequate part. And Sculley's unnecessary increase of the base price of the Mac ($2599, IIRC) didn't help at all.
NeXT, on the other hand, was a different story. They very much hung themselves with the slow-optical-drive-and-no-floppy NeXTCube. 1988 was too early to pull the floppy drive.
The key in advancing your hardware is detecting when the state of the art is advanced enough to support your desires. The floppyless, USB-promoting iMac arrived at the right time (or maybe even a little late).
My HO is that it's a year too early to be selling CRT-less Macs (although I'm using a PowerBook G4...), but, unlike Apple, I don't hold any Samsung stock, so what do I necessarily know?
Rather than modding that comment up, could we have a corroborating link? Facts that "I remember reading somewhere" are likely reliable enough to be considered worthy of a Slashdot front-page story...