You know, I would help out with all this distributed computing stuff, but my spare CPU cycles are all taken up running multiple instances of Progress Quest.
I was wondering about this very issue. I will certainly be writing my senators about the CBDTPA, but it seems like there might be a risk of having my comments pushed to the back corner of some desk if they arrive too far in advance of the vote. Does anyone have any thoughts on the best time to submit a letter?
Okay, "there's" -> "there was" clarifies things for me.
Sorry if my previous post came off a bit flamish--that wasn't my intention. I am simply curious why Qt continues to have a bad reputation amongst many slashdotters. I guess I was asking the wrong person.
What exactly is the "thingy" about Qt? Some of us happen to think that Qt is a very professional, elegantly designed toolkit. It's been GPL'd for something like 1.5 years, so FSF zealotry shouldn't be an issue either...
Seriously, I have a hard time figuring out why so many people bash Qt. Maybe someone can enlighten me.
Come on now, how about "Redundant"? It appears that FOX News is perfectly capable of handling a little slashdotting. Aside from the copyright issues, no need to screw them out of ad revenue.
There has got to be a better comment to blow some modpoints on...
Careful--they're not just changing the bitrate, they're also changing the codec. MPEG-4 yields much lower distortion for a given bitrate than MPEG-2. The tradeoff is in the increased CPU requirements.
Corel Draw and others were practically emulated through the Wine libraries. If they mean business they should have made native Linux apps.
Um, wasn't WordPerfect Suite simply recompiled against WineLib? If I'm correct on that, it's not really fair to call it emulation (even though the suite was built off the Win32 API). Using WineLib undoubtedly saved Corel a hell of a lot of development time, and hardly means they weren't serious about Linux apps.
I should probably also make some nitpicky remark like "Wine Is Not an Emulator"...
Yeah, I think we all want FOTR to do well. I feel the same way about ABM, although RH's vision may differ substantially from what SN had in mind. IIRC, GL overcame similar obstacles in TPM...
</sarcasm>
Dude, I'm sure your post was really insightful and all. It's just that I am not sure how to read it.:-)
What a pain in the ass. I click the box to filter out "Ask Slashdot" posts, then Cliff goes ahead and files this under "Developers". Thanks a lot, Cliff.
$250 always seemed a touch high to me. I think there's a Linux PDA niche somewhere below the iPaqs, competing directly with low-end Palm devices.
I always thought the (monochrome) iPaq H31xx models were a good bet to fill this niche. They are significantly more powerful than the VR3, with a better price tag.
Linux development has lagged behind the color iPaqs for some time, but it looks as if the H31xx is finally supported "out of the box".
Re:electrocution? I don't think so.
on
A Beautiful Mind
·
· Score: 1
Point taken.:-)
Re:electrocution? I don't think so.
on
A Beautiful Mind
·
· Score: 1
Ah, but the current threshold for killing a person is somewhere between 70 and 100 mA. Under the right circumstances, a plain old wall socket has enough juice to toast your ass.:-)
Re:electrocution? I don't think so.
on
A Beautiful Mind
·
· Score: 1
Plus, a 120V house-current is unlikely to electrocute most people.
That all depends on the contact resistance where the wire meets the skin, and that resistance becomes awfully low when the skin is wet. It's not the voltage that kills you, it's the current generated by that voltage.
Of course, the original poster is most likely correct that there is little danger of electrocution in the "water-in-the-fixture" situation. You do need a path for current to follow, after all...
The original signal is not "required" to be band-limited. Rather, it is accepted that frequencies outside of your design bandwidth will not be captured.
Well, that's not entirely accurate either. The presence of frequencies outside of the design bandwidth will lead to aliasing. The reconstructed signal will have additional low-frequency energy that should not be there.
In practice, we often use analog "anti-aliasing" lowpass filters to band-limit the signal before sampling.
Oh, settle down. If you actually read your own link you would notice that SourceForge disabled the download because the file size was unreasonable. Would you sacrifice d/l rates for all of sf.net just so people can transfer 200GB/day worth of Simply GNUStep?
Besides, one of the SF guys posted a solution that would allow them to distribute the load.
You say so. I always thought the '92 resembled a large brick. The TI-89 looks to have the same functionality, but in a form factor that actually makes sense for working side-by-side with a piece of paper.
Of course, I'm an HP user, so what the hell do I know...
Sure, you laugh. But have you ever written down a column of numbers, then drawn a horizontal line underneath, then added them all up? Sounds rather like postfix to me.
Of course, the real power of postfix is unlocked only when you have a nifty stack to play with...
The only complaint I have about it is the inability to record two shows at once.
I'm with you on this one. I love TiVo, and I preach its benefits to anyone who will listen. But anyone who looks closely will notice that I have a nasty hack going on: the cable signal is piped through the VCR, then to the TiVo, allowing me to record two shows at once. The funny thing is, I can't sacrifice the TiVo functionality when I watch the show recorded on VCR, so I start the show playing about 20 minutes early. That way I can build up the Live TV buffer enough to skip commercials.:-)
The only problem with this arrangement is that programming the VCR (with on-screen programming) is difficult when the visuals are slightly delayed by the TiVo buffering scheme.
I still think that if I was using a Linux desktop for work rather than experimentation and games (ksame here I come!), Windowmaker would plain let me get more work done - KDE has too much kruft.
I hear you. My window manager nirvana has come in the form of Blackbox, which is even more minimalistic than Windowmaker. It replaces icons with blazing quick dynamic menus--an elegant solution once you get used to it. It also supports WM dock apps.
One thing I don't know is how QT works in terms of different GUI threads, but I neither know for GTK.
The Qt docs have a note on threading here. From the page: In Qt, one thread is always the event thread - that is, the thread that pulls events from the window system and dispatches them to widgets. The static method QThread::postEvent posts events from threads other than the event thread. The event thread is woken up and the event delivered from within the event thread just as a normal window system event is.
Personally, I have found that the QThread implementation is a piece of cake to work with. It's a very nice abstraction away from the syntactic ugliness of pthreads.
Slashdot Mirror
You know, I would help out with all this distributed computing stuff, but my spare CPU cycles are all taken up running multiple instances of Progress Quest.
This isn't on everyone's radar yet.
I was wondering about this very issue. I will certainly be writing my senators about the CBDTPA, but it seems like there might be a risk of having my comments pushed to the back corner of some desk if they arrive too far in advance of the vote. Does anyone have any thoughts on the best time to submit a letter?
Not to nitpick, but as long as you're asking for help:
"you have fallen pray" --> "you have fallen prey"
Thanks for the post, you've given me some ideas for the letter that I will be writing.
Okay, "there's" -> "there was" clarifies things for me.
Sorry if my previous post came off a bit flamish--that wasn't my intention. I am simply curious why Qt continues to have a bad reputation amongst many slashdotters. I guess I was asking the wrong person.
Also there's that whole QT thingy.
What exactly is the "thingy" about Qt? Some of us happen to think that Qt is a very professional, elegantly designed toolkit. It's been GPL'd for something like 1.5 years, so FSF zealotry shouldn't be an issue either...
Seriously, I have a hard time figuring out why so many people bash Qt. Maybe someone can enlighten me.
Come on now, how about "Redundant"? It appears that FOX News is perfectly capable of handling a little slashdotting. Aside from the copyright issues, no need to screw them out of ad revenue.
There has got to be a better comment to blow some modpoints on...
Careful--they're not just changing the bitrate, they're also changing the codec. MPEG-4 yields much lower distortion for a given bitrate than MPEG-2. The tradeoff is in the increased CPU requirements.
Okay, thanks for the correction. In that case I guess Corel does suck. Or something. :-)
Um, wasn't WordPerfect Suite simply recompiled against WineLib? If I'm correct on that, it's not really fair to call it emulation (even though the suite was built off the Win32 API). Using WineLib undoubtedly saved Corel a hell of a lot of development time, and hardly means they weren't serious about Linux apps.
I should probably also make some nitpicky remark like "Wine Is Not an Emulator"...
Yeah, I think we all want FOTR to do well. I feel the same way about ABM, although RH's vision may differ substantially from what SN had in mind. IIRC, GL overcame similar obstacles in TPM...
:-)
</sarcasm>
Dude, I'm sure your post was really insightful and all. It's just that I am not sure how to read it.
What a pain in the ass. I click the box to filter out "Ask Slashdot" posts, then Cliff goes ahead and files this under "Developers". Thanks a lot, Cliff.
$250 always seemed a touch high to me. I think there's a Linux PDA niche somewhere below the iPaqs, competing directly with low-end Palm devices.
I always thought the (monochrome) iPaq H31xx models were a good bet to fill this niche. They are significantly more powerful than the VR3, with a better price tag.
Linux development has lagged behind the color iPaqs for some time, but it looks as if the H31xx is finally supported "out of the box".
Point taken. :-)
Ah, but the current threshold for killing a person is somewhere between 70 and 100 mA. Under the right circumstances, a plain old wall socket has enough juice to toast your ass. :-)
Plus, a 120V house-current is unlikely to electrocute most people.
That all depends on the contact resistance where the wire meets the skin, and that resistance becomes awfully low when the skin is wet. It's not the voltage that kills you, it's the current generated by that voltage.
Of course, the original poster is most likely correct that there is little danger of electrocution in the "water-in-the-fixture" situation. You do need a path for current to follow, after all...
The original signal is not "required" to be band-limited. Rather, it is accepted that frequencies outside of your design bandwidth will not be captured.
Well, that's not entirely accurate either. The presence of frequencies outside of the design bandwidth will lead to aliasing. The reconstructed signal will have additional low-frequency energy that should not be there.
In practice, we often use analog "anti-aliasing" lowpass filters to band-limit the signal before sampling.
Maybe we can convince NVidia to whip out the old Glide API. Woo-hoo! The return of 3dfx!
*shakes head*
Shouldn't there be some sort of requirement that the submitter of an article at least sort of understand what it says?
Oh, settle down. If you actually read your own link you would notice that SourceForge disabled the download because the file size was unreasonable. Would you sacrifice d/l rates for all of sf.net just so people can transfer 200GB/day worth of Simply GNUStep?
Besides, one of the SF guys posted a solution that would allow them to distribute the load.
the TI-92+ is a thing of shear beauty
You say so. I always thought the '92 resembled a large brick. The TI-89 looks to have the same functionality, but in a form factor that actually makes sense for working side-by-side with a piece of paper.
Of course, I'm an HP user, so what the hell do I know...
Sure, you laugh. But have you ever written down a column of numbers, then drawn a horizontal line underneath, then added them all up? Sounds rather like postfix to me.
Of course, the real power of postfix is unlocked only when you have a nifty stack to play with...
The only complaint I have about it is the inability to record two shows at once.
I'm with you on this one. I love TiVo, and I preach its benefits to anyone who will listen. But anyone who looks closely will notice that I have a nasty hack going on: the cable signal is piped through the VCR, then to the TiVo, allowing me to record two shows at once. The funny thing is, I can't sacrifice the TiVo functionality when I watch the show recorded on VCR, so I start the show playing about 20 minutes early. That way I can build up the Live TV buffer enough to skip commercials. :-)
The only problem with this arrangement is that programming the VCR (with on-screen programming) is difficult when the visuals are slightly delayed by the TiVo buffering scheme.
I still think that if I was using a Linux desktop for work rather than experimentation and games (ksame here I come!), Windowmaker would plain let me get more work done - KDE has too much kruft.
I hear you. My window manager nirvana has come in the form of Blackbox, which is even more minimalistic than Windowmaker. It replaces icons with blazing quick dynamic menus--an elegant solution once you get used to it. It also supports WM dock apps.
(read the manufacture date through the hole in the back to make sure it was made before Sept. 2000)
What's wrong with more recent models? Do they include some sort of "anti-hacking" firmware or something?
One thing I don't know is how QT works in terms of different GUI threads, but I neither know for GTK.
The Qt docs have a note on threading here. From the page: In Qt, one thread is always the event thread - that is, the thread that pulls events from the window system and dispatches them to widgets. The static method QThread::postEvent posts events from threads other than the event thread. The event thread is woken up and the event delivered from within the event thread just as a normal window system event is.
Personally, I have found that the QThread implementation is a piece of cake to work with. It's a very nice abstraction away from the syntactic ugliness of pthreads.