Sorry to be so cold... but as they say, the road to hell is paved with good intentions. Also, good intentions (IMHO) don't count for shit if you're working to misuse something like the term 'Open Source' strictly for weaseling your way into a new market.
Microsoft's C compiler was bought from the company that produced Lattice C. IE was NOT purchased - it was SUPPOSED to be licensed, but M$ stabbed poor Spyglass in the back by then releasing the licensed browser for free, nearly killing off Spyglass entirely. TrueType was licensed from Apple, not bought. And BTW, their socket API borrows heavily from the Berkeley Sockets API (check the copyright info on the WinSock DLLs).
Hmm. You mean like X11Amp? (www.x11amp.org) It's not quite at the same level of some other players, but it is moving along fast (I've been hacking on it for the past month, roughly...). Instead of talking about how you don't like what's out there, why not start coding?
If you're using MpegTV, doon't run 'mtvp' directly, that's only the player engine. Run 'mtv' - that gives you an Xforms-based UI to control playback from. (Works great for VideoCDs in the recent releases.)
Read it yourself. If they have markings specifically for when these people are injured/killed, I think that says a LOT. Also, you say they're not doing anything wrong, but if it's not advocating violence against these doctors, then what other reason would there be to collect such minutiae about all these people? I can't think of a single one.
Obviously it doesn't SAY that. But please, enlighten me. WHY else would such a list exist? I can't think of a SINGLE logical reason for compiling this list, if not as a reference for those who would threaten/harm/kill the doctors or the family members named there.
Well, you don't see anything wrong with Microsoft shoving a lousy product down people's throats, even if they are dumb enough to accept it? So basically, we should just give up any hope that these people will ever acquire a clue, and just allow them to be swindled out of obscene amounts of money, and allow Microsoft to monopolize whatever markets it chooses? Brilliant. Just brilliant.
1: Why do people cite this so often? I mean, I don't see the difficulty. Each device needs a unique ID. The bus needs to be terminated. What's so hard about that? 2: That would be a limitation. You can only have so many devices sharing power on a bus like that before there's not enough voltage to drive them all. 3: Sounds dangerous to me... 4: Well, yes, but that's just cause lack of demand yields higher prices. If SCSI were in wider use, cables, terminators and all that would be a dime a dozen.
I think I'll wait and see what happens with the FireWire vs. SCSI debate. Personally, I think Apple trying to collect $1 per manufactured FireWire port could just be the death of it. But, we'll see, I suppose.
Umm, did we rea the same article? The one where Jon Katz says his wife reported seeing the UPS guy drop the box the computer was in? Have you ever seen the kind of damage UPS can do to a package? If if was dropped IN FRONT OF HIS WIFE, I don't care to GUESS how many other times it'd been dropped. It's UPS's fault. Don't blame the company that built the thing for the shipper's doing.
Aye, it's enough to make me wonder anyway. As many other people have said, no sane person would EVER accept an obviously-damaged product from a shipper! It shouldn't even be opened (any more than it already is on reciept of course - happens when things get dropped/squashed/etc), the carrier should immediately be told "This is damaged, return it NOW."
Amen. I've been saying it all along. Maybe if we did something like this, the Internet would a more clueful, less profiteer-and-newbie-filled thing. But the gov't won't do it - they're too busy prosecuting the two Bills. Bah.
Hell, there's still a fair amount of the code in MacOS that's 68K assembly. That's right, it still hasn't been converted over to native PPC code. Why? Who knows? You'd think after all this time, they'd have finally gotten it all converted.
It seems to lock up because most of Windows 95's GDI code is still 16 bit, so when the 32-bit subsystem's sucking CPU time like nuts, the 16-bit process gets no CPU time. (Yes I know, I even scare myself sometimes.)
Also, scanner drivers aren't that easy to write if you have no documentation for the scanner's control language (or even how to speak to its interface).
Slashdot Mirror
In my book, good intentions count for something.
Sorry to be so cold... but as they say, the road to hell is paved with good intentions. Also, good intentions (IMHO) don't count for shit if you're working to misuse something like the term 'Open Source' strictly for weaseling your way into a new market.
Microsoft's C compiler was bought from the company that produced Lattice C. IE was NOT purchased - it was SUPPOSED to be licensed, but M$ stabbed poor Spyglass in the back by then releasing the licensed browser for free, nearly killing off Spyglass entirely. TrueType was licensed from Apple, not bought. And BTW, their socket API borrows heavily from the Berkeley Sockets API (check the copyright info on the WinSock DLLs).
Hmm. You mean like X11Amp? (www.x11amp.org) It's not quite at the same level of some other players, but it is moving along fast (I've been hacking on it for the past month, roughly...). Instead of talking about how you don't like what's out there, why not start coding?
If you're using MpegTV, doon't run 'mtvp' directly, that's only the player engine. Run 'mtv' - that gives you an Xforms-based UI to control playback from. (Works great for VideoCDs in the recent releases.)
Yes, the first version of Windows 95 did have PPP dialup features. (It was the first Windows release to ship with it - unless NT did. Shrug.)
Read it yourself. If they have markings specifically for when these people are injured/killed, I think that says a LOT. Also, you say they're not doing anything wrong, but if it's not advocating violence against these doctors, then what other reason would there be to collect such minutiae about all these people? I can't think of a single one.
Obviously it doesn't SAY that. But please, enlighten me. WHY else would such a list exist? I can't think of a SINGLE logical reason for compiling this list, if not as a reference for those who would threaten/harm/kill the doctors or the family members named there.
Well, you don't see anything wrong with Microsoft shoving a lousy product down people's throats, even if they are dumb enough to accept it? So basically, we should just give up any hope that these people will ever acquire a clue, and just allow them to be swindled out of obscene amounts of money, and allow Microsoft to monopolize whatever markets it chooses? Brilliant. Just brilliant.
Well, here's what I think of your reasons...
1: Why do people cite this so often? I mean, I don't see the difficulty. Each device needs a unique ID. The bus needs to be terminated. What's so hard about that?
2: That would be a limitation. You can only have so many devices sharing power on a bus like that before there's not enough voltage to drive them all.
3: Sounds dangerous to me...
4: Well, yes, but that's just cause lack of demand yields higher prices. If SCSI were in wider use, cables, terminators and all that would be a dime a dozen.
I think I'll wait and see what happens with the FireWire vs. SCSI debate. Personally, I think Apple trying to collect $1 per manufactured FireWire port could just be the death of it. But, we'll see, I suppose.
Umm, did we rea the same article? The one where Jon Katz says his wife reported seeing the UPS guy drop the box the computer was in? Have you ever seen the kind of damage UPS can do to a package? If if was dropped IN FRONT OF HIS WIFE, I don't care to GUESS how many other times it'd been dropped. It's UPS's fault. Don't blame the company that built the thing for the shipper's doing.
Aye, it's enough to make me wonder anyway. As many other people have said, no sane person would EVER accept an obviously-damaged product from a shipper! It shouldn't even be opened (any more than it already is on reciept of course - happens when things get dropped/squashed/etc), the carrier should immediately be told "This is damaged, return it NOW."
Amen. I've been saying it all along. Maybe if we did something like this, the Internet would a more clueful, less profiteer-and-newbie-filled thing. But the gov't won't do it - they're too busy prosecuting the two Bills. Bah.
Hell, there's still a fair amount of the code in MacOS that's 68K assembly. That's right, it still hasn't been converted over to native PPC code. Why? Who knows? You'd think after all this time, they'd have finally gotten it all converted.
It seems to lock up because most of Windows 95's GDI code is still 16 bit, so when the 32-bit subsystem's sucking CPU time like nuts, the 16-bit process gets no CPU time. (Yes I know, I even scare myself sometimes.)
Also, scanner drivers aren't that easy to write if you have no documentation for the scanner's control language (or even how to speak to its interface).