Actually, you could easily connect this implicit Intel threat to the (rather lame) chinese attempt to independently develop x86 CPUs. I believe they have a PII-400 equivalent right now.
Errr.... last time I checked, Linux 2.4 drivers didn't work with 2.6 kernel. Same goes for 2.2. I am not an MS fan either, but still, let's not bash 'em just because it's fun.
I do not believe this is the right way to approach the issue. Let them work this ugly legalese - in courts. How are we any different from Microsoft, if we happen to "exclude" some support from projects because we do not like the receipient? I do not say "let's all develop code for SCO support", but please do not remove any *existing* code.
Ohhhh.... This is soooo much more than just keeping one of them busy. In fact, you screw up their ENTIRE operation, even if they have 100's of telemarketers. Why? Explanation below:
In order to raise the productivity of their employees, they save them the time dialing, recognizing answering machine, ringing-and-ringing, busy signals, tone waiting etc.
How? The use these machines which are called predictive dialers. Why predictive, you ask? because they predict when the next agent will end her call, and based upon lots of parameters (call duration, busy signal rate by time of day, time to recognize voicemails etc.) - will place a call BEFORE that agent hangs up, so the moment she hangs up - she has the next call ready for her, with an actual person on the line.
Now, it is rather clear that if you hold just one agent on the line for a LONG time, then you screw every statistics the predictive dialer has, and so the agents lose sync with the dialer, and as a result - their productivity dives....
Which is what we wanted.
been there, done that
on
Searching Sound
·
· Score: 2, Informative
I work for a CT (Computer Telephony) company (see comment on story from half an hour ago). My company does soundex, phonex, and some proprietary stuff too, to convert recorded phone calls into the text of the call, regardless of noise, tone, etc. Useful for your friendly government to spy on you. This is really old news.
Disclaimer: I work for a computer telephony company.
That said, their product is very very poor. Almost no documentation in code (which is a MUST when you go open source), very buggy, doesn't work with most middleware (like Genesys, CT-Connect, TSAPI, Symposium etc.).
I wonder if they tell the kids the artists are starving since the RIAA gives them $0.00000083 for every CD sold.
Actually, you could easily connect this implicit Intel threat to the (rather lame) chinese attempt to independently develop x86 CPUs. I believe they have a PII-400 equivalent right now.
I wonder how long it will take to DDOS Verisign to oblivion.... everybody, click after me Do not attempt to own us
Errr.... last time I checked, Linux 2.4 drivers didn't work with 2.6 kernel. Same goes for 2.2. I am not an MS fan either, but still, let's not bash 'em just because it's fun.
I do not believe that no one has submitted this yet, but this should definitely be mentioned. Check Item #3 under "SOME MORE ALSO RAN".
I hope you realize that by removing SCO support you are spending effort better off spent elsewhere in open-source projects?
Why do you not wish to support SCO's unfortunate customers?
I do not believe this is the right way to approach the issue. Let them work this ugly legalese - in courts. How are we any different from Microsoft, if we happen to "exclude" some support from projects because we do not like the receipient? I do not say "let's all develop code for SCO support", but please do not remove any *existing* code.
Finally the Penguin will submerge at sea... :)
Thanks, I think I shall "rent" Quake 4 at Kazaa, they have great prices....
It doesn't do that in Israel. A camel may obscure the sun now and then, though.
Automatic transparent operation encrypts entire hard drive bit-by-bit, including Boot Sector and OS
Can anyone spell "4GB-of-candidates-for-known-plaintext-attack", boys and girls?
Who moderated this as 2, interesting? I'd give it either "4, funny" or "-1, troll", but definitely not "2, interesting"!
that's what the french military always did, since WWI, isn't it? Oh... you ment it as joke...
how sad.
check this out. it's NASA's space protocol suite....
Ohhhh.... This is soooo much more than just keeping one of them busy. In fact, you screw up their ENTIRE operation, even if they have 100's of telemarketers. Why? Explanation below:
In order to raise the productivity of their employees, they save them the time dialing, recognizing answering machine, ringing-and-ringing, busy signals, tone waiting etc.
How? The use these machines which are called predictive dialers. Why predictive, you ask? because they predict when the next agent will end her call, and based upon lots of parameters (call duration, busy signal rate by time of day, time to recognize voicemails etc.) - will place a call BEFORE that agent hangs up, so the moment she hangs up - she has the next call ready for her, with an actual person on the line.
Now, it is rather clear that if you hold just one agent on the line for a LONG time, then you screw every statistics the predictive dialer has, and so the agents lose sync with the dialer, and as a result - their productivity dives....
Which is what we wanted.
I work for a CT (Computer Telephony) company (see comment on story from half an hour ago). My company does soundex, phonex, and some proprietary stuff too, to convert recorded phone calls into the text of the call, regardless of noise, tone, etc. Useful for your friendly government to spy on you. This is really old news.
Disclaimer: I work for a computer telephony company.
That said, their product is very very poor. Almost no documentation in code (which is a MUST when you go open source), very buggy, doesn't work with most middleware (like Genesys, CT-Connect, TSAPI, Symposium etc.).