The sad part about BetaMax is that it was actually a superior format to VHS and smaller form factor! But unfortunately the marketing behind VHS overwhelmed Beta.
But I didn't realize they still made the players... The digital age of video a-cometh.
Well there is one positive thing to this story, the fact that a private sector company got a hold of this software before the govt. did. At this in this case, NA will be somewhat hesitant to allow the government to use this technology (the FBI could even turn it against NA!) to invade the privacy of citizens, whereas as we saw with Carnivore, the FBI pretty much gave us the answer "we have this technology and we are going to use it, too bad!"
My bet is not. A large segment of the population fear other "modified" things like irradiated meat, what's to make them want actual animal tissue inside of them (and cloned tissue at that..) Though the prospect of life or death might be enough to persuade most. Of course this still has a long way to go, never mind the cross-species disease issues, etc.
Exactly. Dithering DOES NOT MEAN that the display is 16-bit. Of course Palm says "color combinations" not specifically colors, which is total marketing BS and is meant to mislead people.
I suggest people call up their Better Business Bureau.
The main problem with the AMD CPUs is that they are resigned to live on motherboards with sub-par memory throughput (if you look at the memory benchmarks, the AMDs always come out on the low end, even when the P4s also have DDR instead of RDR).
VIA needs to find out a way to increase their memory performance out of their NorthBridges so that these results won't show up.
It's quite ironic that this story was posted today, because I'm having the same problem and I was beating my head into the ground as to why it was so slow.
Basically I wanted the GPU to map some textures for me (cause its been designed to do that) and then I wanted to get those back and do some other operations on it.
What I found with my really cude benchmarking is that a call to glReadPixels() of 128x128 8-bit RGB data from a GeForce 2 Ti took around.25ms, which was totally unacceptable because I needed to do this as much as possible within a frame time (so ~30ms..)
It boggled my mind as to why this was so slow, and now I know.
As a person who has talked to IT and CEOs of companies, they both will tell you that upgrading the OS of the company is _not_ a trivial matter. Extensive testing must first be done to make sure all company software runs reliably on the new OS and is stable. Also, printer configurations, network configurations, etc... need to all be figured out in advance so that the migration takes as small a timeframe as possible. As you can see, this results in a lot of time and money (I haven't even factored in the cost of the new OS) already.
Yes, companies are reluctant to change OSs, and unfortunately, the few that have already upgraded to XP are going to be forced by Microsoft to upgrade. I suspect that the windows98 number will come down slowly as the win2000 number stays constant (reflecting companies who don't want to leap into XP/.NET/etc...)
I would say that Certifications are all about memorization, not creativity or innovation. In this kind of market, people want something new, not that you know what some obsure key in the MS Windows registry does.
Red Boxing used to be popular... Whenever you dropped coins into a pay phone the phone would emit 5 certain frequency tones. People figured out the frequency and amplitude of these tones and played them into the handset, and voila! free phone calls.
They have since upgraded pay phones so that these tones aren't used anymore.
I think the main concern with using OpenSSL is that it is too slow for real-time data. Just think of the amount of packets you have to crypt/decrypt per second. If we assume 44khz, 16-bit (depends on the ADC/DAC I guess) data, well that's a lot of packets. No one wants to have a 1-2 second delay in their phone conversation.
As the article briefly mentions, security is a lot easier to implement if the security measures you want are designed along with the system. Of course in this case, our hands are tied, since we want to integrate our Voice and Data networks and IP had no intrensic security to go with it.
But encryption is definitely feasible. They already use encryption on satellite phones and whatnot, so what is preventing them from adapting that technology to VoIP? The VPN idea that was mentioned was quite interesting. That would indeed work if the software can keep up with real time.
But really VoIP has the same concerns as normal phones and wireless phones. You can intercept calls in both of the other systems (gaining access to phone lines, intercepting cell transmissions, or stealing phone IDs).
So I don't think that security concerns should stand in the way of using VoIP. I wouldn't use it for your most secure of conversations, but soon enough the technology will get better, since now people realize there is a need for this kind of thing.
Looks like they were having some issues with the Byte Ordering on the machines with their in-house software: "Fundamental differences in how Intel and HP processors treat binary numbers meant that some software was very difficult to translate, leading to delays that kept newly purchased equipment idle."
Oops. Don't people think about portability issues??!!
Heh..Like to keep your job? Or are you just planning to be the sole maintainer for the life of the code? =)
Re:Breaking interoperability... again???
on
GCC 3.2 Released
·
· Score: 2
And how much stuff was actually compiled with GCC 3.11? They probably didn't want you using 3.11 for your critical apps anyways if they had all these bugs to fix =) But its nice they finally settled on a stable ABI, so all releases forward of this one will be compatible.
Heh I wonder if it compiles the Linux kernel
on
GCC 3.2 Released
·
· Score: 1
Come on..I know people dying to rush out and try to compile a kernel with this thing...I mean that's what it was released for "building OSes.."
Its amazing that the USPTO would grant this patent. But it would be perfectly valid in pretty much any other country since most of them (except the U.S.) are on a "first to file" basis, instead of "first to conceive/bring to practice" basis.
So if there is prior art, and it can be PROVED that there is prior art then the patent is moot. The key word here is "prove." A guy from another website who says he "remebers stuff like this going on way before they were a company" just isn't going to cut it. They need to find some documents, whitepapers, whatever (preferably not just electronic copies, that have been signed and dated by someone (perferably multiple people).
Believe it or not, prior art is a very difficult thing to prove.
Of course traveling at "faster than the speed of light" goes back to the whole explanation that those people who do the technical stuff for Star Trek propose...the ship is not moving faster than the speed of light actually, space is just contracting and expanding around it, etc. etc. etc...
Things like this remind me of the infamous papers that tried to prove that NP=P. Yes, its actually a good thing that this is being published in Nature. There it can be exposed to a forum of many other physicists who will try and prove the validity of the claim. We shall see what they come up with in 6 months or so.
Having access to the machine kills security anyway
on
Shattering Windows
·
· Score: 1
Since this requires access to the machine (sitting at the console) its not that surprising.
I mean you can get root on a linux box if you are sitting at the console and they are running lilo... 1) Reboot 2) at lilo prompt: [name of kernel] init=/bin/sh
Linux boots, and drops you to a root prompt. Remount the drive as read/write and away you go!
Case Western used to have an ATM network available to all of its students which was all super fast and had high bandwidth. However, they found that a pure network of ATM was too unstable (there were numerous random outages that got really annoying) and started switching back to ethernet. However it looks like they are not going to settle with 100mbps and just go straight to Gigabit. I guess they like to have their network be as fast as possible.
First of all, let me know if you are coming here (Caltech) -- drop me an email.
What I have noticed here is that there is much emphasis on theory, which makes sense since Caltech tends to be a more research oriented school. However, they have all but eliminated practical programming classes from the curriculum, and not to mention the fact that there is no official CS major yet (supposedly they are working on it..) When I was a freshman, there were intro courses in C, C++, and Java. Now, those courses have changed to more concept oriented using (this year) Scheme, Modula3, and Eiffel. The department's philosophy seems to be that if we teach you the "fundamental concepts" of programming, you can program in any language.
Separate from the Computer Science Theory side of things, the CS department has a large graphics component, which you could say is a more practical representation of research than pure theory.
So, for questions, I think you should ask ones along those lines. Whether they are taking a practical stance or a more theoretical one...
What got me a job was networking. I had some friends of mine who worked at a couple companies that I was interested in, which enabled me to get interviews there, and eventually an offer from one of them. In this kind of market, networking goes a long way. You should contact the people who you co-oped with and see if they know of anyone who is looking for help.
So Linus screwed up and instituted a bug into the kernel, but do you realize how fast it was fixed?
(about 2 days I think....)
You show me what other OS has that kind of turnaround on patches. (And don't say that other OSes wouldn't have released it with this kind of bug, because we all know it happens...)
So this whole Asynchronous thing has been going
on for a while. There has been extensive research
done here at Caltech (in fact they developed
the first Async processor here...).
Also, there is a Caltech startup that is
devoted to this sort of stuff,
Asynchronous Digital Design.
Its really cool stuff, and it can run ridiculously fast. Its just a bitch to design.
Slashdot Mirror
The sad part about BetaMax is that it was actually a superior format to VHS and smaller form factor! But unfortunately the marketing behind VHS overwhelmed Beta.
But I didn't realize they still made the players...
The digital age of video a-cometh.
Well there is one positive thing to this story, the fact that a private sector company got a hold of this software before the govt. did.
At this in this case, NA will be somewhat hesitant to allow the government to use this technology (the FBI could even turn it against NA!) to invade the privacy of citizens, whereas as we saw with Carnivore, the FBI pretty much gave us the answer "we have this technology and we are going to use it, too bad!"
My bet is not. A large segment of the population fear other "modified" things like irradiated meat, what's to make them want actual animal tissue inside of them (and cloned tissue at that..)
Though the prospect of life or death might be enough to persuade most. Of course this still has a long way to go, never mind the cross-species disease issues, etc.
Another ./ story, another down website =(
But back to the story (which I can't read), seems like an interesting idea, BBSes back in the old days were great...
Exactly.
Dithering DOES NOT MEAN that the display is 16-bit. Of course Palm says "color combinations" not specifically colors, which is total marketing BS and is meant to mislead people.
I suggest people call up their Better Business Bureau.
The main problem with the AMD CPUs is that they are resigned to live on motherboards with sub-par memory throughput (if you look at the memory benchmarks, the AMDs always come out on the low end, even when the P4s also have DDR instead of RDR).
VIA needs to find out a way to increase their memory performance out of their NorthBridges so that these results won't show up.
It's quite ironic that this story was posted today, because I'm having the same problem and I was beating my head into the ground as to why it was so slow.
.25ms, which was totally unacceptable because I needed to do this as much as possible within a frame time (so ~30ms..)
Basically I wanted the GPU to map some textures for me (cause its been designed to do that) and then I wanted to get those back and do some other operations on it.
What I found with my really cude benchmarking is that a call to glReadPixels() of 128x128 8-bit RGB data from a GeForce 2 Ti took around
It boggled my mind as to why this was so slow, and now I know.
As a person who has talked to IT and CEOs of companies, they both will tell you that upgrading the OS of the company is _not_ a trivial matter.
Extensive testing must first be done to make sure all company software runs reliably on the new OS and is stable. Also, printer configurations, network configurations, etc... need to all be figured out in advance so that the migration takes as small a timeframe as possible.
As you can see, this results in a lot of time and money (I haven't even factored in the cost of the new OS) already.
Yes, companies are reluctant to change OSs, and unfortunately, the few that have already upgraded to XP are going to be forced by Microsoft to upgrade. I suspect that the windows98 number will come down slowly as the win2000 number stays constant (reflecting companies who don't want to leap into XP/.NET/etc...)
I would say that Certifications are all about memorization, not creativity or innovation.
In this kind of market, people want something new, not that you know what some obsure key in the MS Windows registry does.
Red Boxing used to be popular...
Whenever you dropped coins into a pay phone the phone would emit 5 certain frequency tones. People figured out the frequency and amplitude of these tones and played them into the handset, and voila! free phone calls.
They have since upgraded pay phones so that these tones aren't used anymore.
I think the main concern with using OpenSSL is that it is too slow for real-time data.
Just think of the amount of packets you have to crypt/decrypt per second.
If we assume 44khz, 16-bit (depends on the ADC/DAC I guess) data, well that's a lot of packets.
No one wants to have a 1-2 second delay in their phone conversation.
As the article briefly mentions, security is a lot easier to implement if the security measures you want are designed along with the system. Of course in this case, our hands are tied, since we want to integrate our Voice and Data networks and IP had no intrensic security to go with it.
But encryption is definitely feasible. They already use encryption on satellite phones and whatnot, so what is preventing them from adapting that technology to VoIP?
The VPN idea that was mentioned was quite interesting. That would indeed work if the software can keep up with real time.
But really VoIP has the same concerns as normal phones and wireless phones. You can intercept calls in both of the other systems (gaining access to phone lines, intercepting cell transmissions, or stealing phone IDs).
So I don't think that security concerns should stand in the way of using VoIP. I wouldn't use it for your most secure of conversations, but soon enough the technology will get better, since now people realize there is a need for this kind of thing.
Looks like they were having some issues with the Byte Ordering on the machines with their in-house software:
"Fundamental differences in how Intel and HP processors treat binary numbers meant that some software was very difficult to translate, leading to delays that kept newly purchased equipment idle."
Oops. Don't people think about portability issues??!!
Real programmers don't comment!
Heh..Like to keep your job?
Or are you just planning to be the sole maintainer for the life of the code? =)
And how much stuff was actually compiled with GCC 3.11? They probably didn't want you using 3.11 for your critical apps anyways if they had all these bugs to fix =)
But its nice they finally settled on a stable ABI, so all releases forward of this one will be compatible.
Come on..I know people dying to rush out and try to compile a kernel with this thing...I mean that's what it was released for "building OSes.."
If I wasn't at work I'd try it...sigh.
But my guess is that it doesn't.
Its amazing that the USPTO would grant this patent. But it would be perfectly valid in pretty much any other country since most of them (except the U.S.) are on a "first to file" basis, instead of "first to conceive/bring to practice" basis.
So if there is prior art, and it can be PROVED that there is prior art then the patent is moot.
The key word here is "prove." A guy from another website who says he "remebers stuff like this going on way before they were a company" just isn't going to cut it. They need to find some documents, whitepapers, whatever (preferably not just electronic copies, that have been signed and dated by someone (perferably multiple people).
Believe it or not, prior art is a very difficult thing to prove.
Of course traveling at "faster than the speed of light" goes back to the whole explanation that those people who do the technical stuff for Star Trek propose...the ship is not moving faster than the speed of light actually, space is just contracting and expanding around it, etc. etc. etc...
Things like this remind me of the infamous papers that tried to prove that NP=P.
Yes, its actually a good thing that this is being published in Nature. There it can be exposed to a forum of many other physicists who will try and prove the validity of the claim.
We shall see what they come up with in 6 months or so.
Since this requires access to the machine (sitting at the console) its not that surprising.
I mean you can get root on a linux box if you are sitting at the console and they are running lilo...
1) Reboot
2) at lilo prompt: [name of kernel] init=/bin/sh
Linux boots, and drops you to a root prompt. Remount the drive as read/write and away you go!
Case Western used to have an ATM network available to all of its students which was all super fast and had high bandwidth. However, they found that a pure network of ATM was too unstable (there were numerous random outages that got really annoying) and started switching back to ethernet.
However it looks like they are not going to settle with 100mbps and just go straight to Gigabit.
I guess they like to have their network be as fast as possible.
First of all, let me know if you are coming here (Caltech) -- drop me an email.
What I have noticed here is that there is much emphasis on theory, which makes sense since Caltech tends to be a more research oriented school. However, they have all but eliminated practical programming classes from the curriculum, and not to mention the fact that there is no official CS major yet (supposedly they are working on it..)
When I was a freshman, there were intro courses in C, C++, and Java. Now, those courses have changed to more concept oriented using (this year) Scheme, Modula3, and Eiffel.
The department's philosophy seems to be that if we teach you the "fundamental concepts" of programming, you can program in any language.
Separate from the Computer Science Theory side of things, the CS department has a large graphics component, which you could say is a more practical representation of research than pure theory.
So, for questions, I think you should ask ones along those lines. Whether they are taking a practical stance or a more theoretical one...
What got me a job was networking.
I had some friends of mine who worked at a couple companies that I was interested in, which enabled me to get interviews there, and eventually an offer from one of them.
In this kind of market, networking goes a long way.
You should contact the people who you co-oped with and see if they know of anyone who is looking for help.
So Linus screwed up and instituted a bug into the kernel, but do you realize how fast it was fixed?
(about 2 days I think....)
You show me what other OS has that kind of turnaround on patches. (And don't say that other OSes wouldn't have released it with this kind of bug, because we all know it happens...)
So this whole Asynchronous thing has been going on for a while. There has been extensive research done here at Caltech (in fact they developed the first Async processor here...). Also, there is a Caltech startup that is devoted to this sort of stuff, Asynchronous Digital Design.
Its really cool stuff, and it can run ridiculously fast. Its just a bitch to design.