Seriously now. Apart for "production values" is there really any difference between two fat old man pretending to be in a Sci-Fi movie and a little kid pretending to be in a Sci-Fi?
The one lesson to be learned, perhaps, is that nerd never disappear, they just grow older.
I can just imagine the reprucussions of trying to use this laser to vaporize . On the ground it will look as if he has risen to heaven on a pillar of searing light. How better to create yet another true prophet and ensuing religion?
Experience as a developer using Bluetooth
on
Is Bluetooth Dead?
·
· Score: 1
At the time writing anything for Bluetooth was a nightmare. Contrary to what the article says, their network stack, if you can call it that, was a complex and obtuse disaster that made no sense. Why couldn't they just adopt a socket style interface?!? There were also very basic technical problems that were happily overlooked: 1. If you remove the wire from your headset, the classic (and only?) Bluetooth application example, you lose your source of power, forcing you to put a big battery in. Big so it could power the Bluetooth chip. This made the headsets huge and uncomfortable heavy. 2. There was no reliable way for a Bluetooth device to identify the correct peer in an enviornment with many other Bluetooth devices. As in example, you are sitting at the airport lounge waiting for you flight and doodling with your Bluetooth devices next to another person with his own gadgets. There was a very good chance that all your devices would start talking to each other in one cozy little network!
This was 3 years ago, maybe things have improved since.
Is there any reason telemarketers won't move their operations to Canada and place their calls from there? It would be ironic as it would fulfill the prophecies of lost American jobs without anything being gained for the American public.
There can be another "legal" approach. Instead of sharing complete files on your system, you only share small parts of them. For instance, if you have a 5MB file on your drive, you only share 100K bytes of it. Someone downloading the file would have to find 50 peers in order to reconstruct the entire file.
This appears to be legal since you are sharing only a small portion of the file (http://www.theregister.co.uk/content/6/32004.html ).
It is kind of peculiar that all of their demos have a rather quick and abrupt hit/fall/tie/don't move much animation sequence. At first it is amusing but it appears all the animations are like that. Thought I'd point that out.
Isn't this what the broadband industry always wanted? They are constantly searching for the killer app to migrate the masses onto broadband. It comes along and all they do is moan and complain about how it is hogging their network. Duh! Unforunately, they seem to be too busy trying to shove unwanted "content" down consumers' throats in order to see *the* killer app right under their noses.
Ever hear anything good said about MFC? What about ATL? How about their OLE implementation? Have you ever heard what the Samba people have to say about Window's file and printer sharing protocol? Here are my favorite quotes by Jeremy Allison (Samba Team) about the Windows network printing protocol: "The implementation is APPALING", "The implementers did not understand network protocols. At All." and, "The print subsystem looks like it was cobbled together by sophomore (1st year) CS students" What about their buggy Kerberos implementation where they sometimes publish bogus OIDs?
What is to prevent this from turning into another CDDB? What is to prevent MusicBrainz from deciding to close their DB and start charging for use after they've milked the community to build the DB? The DB implementation may be open source but without the information in it, the implementation is useless.
You might want to add execution history to the list. A stack trace gives you the current calls but what were the previous 5 calls made? An execution history would tell you what the last N calls were and in what order they occured. It would be easy to implement as a series of stack snapshots.
The obstacle to micropayments' acceptance is not technical, it is phsycological. Spending money requires involved mental cost/benefit balancing. Essentially, am I getting something for my money? That a micropayment is micro does not mitigate that this mental balancing still needs to be done for each micropayment made - there is a definite fixed cost that is not dependent on the amount of money being spent. As it turns out, it appears to be easier to pay one, bigger, lump sum ahead of time and then not need to think about it again.
Micropayments are doomed because they cause too much mental stress.
Linux is matching Windoze feature for feature till they are identical. It must do this to be a viable alternative to Windoze, which is what Linux's developers appear to want. Once the two are equal, Linux will begin the second stage of Extending... Linux just might beat Windoze at Microsoft's favorite game.
A now defunct company, First Access, did "Vicinity Authentication" in 1998. The product used a proprietary RF/IR card and sensor combination. The card could be worn anywhere and the sensor would hook up to RS-232. It was cryptographically secure and worked well. Several untis were sold to German and Australian companies. Unfortunately, First Access' management didn't know what to do with themselves and the company died a slow painful death.
so all it takes to shut down the U.S. military is a couple Wi-Fi transmitters? I would hope the military would be able to cope with substantially more intereference than a lowly Wi-Fi access point. Otherwise, they might as well turn out the lights.
From reading through some of the posts it appears the RIAA is already winning the war. No one appears to find the implied illegality of copying a file in your possession an incongruous proposition anymore. This is the core of the issue, not "pirates" or "artists" or other fictions. The problem with the RIAA and its discordant crusade is the fact that it runs against a widely accepted social norm - I have the right to copy my files. This is where the RIAA is weakest and is the only avenue for its defeat. If this idea is forgotten, the RIAA wins. Everyone else loses.
This guy should flat out admit that MS products are not engineered at all. Some choice quotes by Jeremy Allison (Samba Team) about the Windows network printing protocol: "The implementation is APPALING", "The implementers did not understand network protocols. At All." and, my favorite, "The print subsystem looks like it was cobbled together by sophomore (1st year) CS students"
Aren't hotmail accounts now part of the passport world? If so, has anyone noticed the little fact that passport passwords are case insensitive? Great security...
How would they decide what is loggable and what is not? By looking at ports 80 and 25? The solution to that is simple, switch all your "sensitive" browsing to port 666. Use PGP for your email or perhaps use something as mundane as ICQ, or FTP drop points. In addition you can have a script generating spurious emails and web browsing requests all day long so that you quickly overwhelm anyone's ability to actually log anything of substance (if you are really dedicated, you could probably generate 1GB of trash data a day). Whoever is thinking about these moronic ideas appears to be technically ignorant.
I have never heard of a computer course where additional paper was refused a student. If this has occured, then you have a much bigger problem with the course staff. They are out to get you to begin with so you might as well opt out of the course and wait for better people.
Your Hitler invocation is gratuitous and as such merits no response.
"One proposed remedy being debated by record label executives is federal legislation requiring used-CD retailers to pay royalties on secondary sales of albums."
It's interesting how the federal government is seen as a convenient tool for furthering the music industry's profits. The article makes it appear that the moment a decision is made, the government will heel. No one bothers to point out how chilling this idea is.
"... Asking about fundamental principles is fine; asking for pieces of code or specific API details is IMO rediculous"
Unless this is a language course, or an introduction to computing...
"The few times I was subjected to these tests, I sure felt primitive erasing entire chunks of code after having realized I needed to insert something in the beginning... I don't think any reasonably experienced programmer writes code entirely from top to bottom"
True, but any reasonably savvy college student (or, now that I think of it, anyone who has programmed BASIC with line numbers) would know to put nice large spaces between his lines of code to accomodate the occasional insert. That and the uncanny ability to write in ever smaller hand writing...
Quit whining about why you can't do tests and just slog through them like the millions who did it before you
Of course, performance doesn't suffer when you upgrade from a 5 y/o processor to a new top-of-the-line processor. Most of the descriptions about speed up seem to be directly attributable to Intel, not Linux...
Slashdot Mirror
Seriously now. Apart for "production values" is there really any difference between two fat old man pretending to be in a Sci-Fi movie and a little kid pretending to be in a Sci-Fi? The one lesson to be learned, perhaps, is that nerd never disappear, they just grow older.
I can just imagine the reprucussions of trying to use this laser to vaporize . On the ground it will look as if he has risen to heaven on a pillar of searing light. How better to create yet another true prophet and ensuing religion?
At the time writing anything for Bluetooth was a nightmare. Contrary to what the article says, their network stack, if you can call it that, was a complex and obtuse disaster that made no sense. Why couldn't they just adopt a socket style interface?!?
There were also very basic technical problems that were happily overlooked:
1. If you remove the wire from your headset, the classic (and only?) Bluetooth application example, you lose your source of power, forcing you to put a big battery in. Big so it could power the Bluetooth chip. This made the headsets huge and uncomfortable heavy.
2. There was no reliable way for a Bluetooth device to identify the correct peer in an enviornment with many other Bluetooth devices. As in example, you are sitting at the airport lounge waiting for you flight and doodling with your Bluetooth devices next to another person with his own gadgets. There was a very good chance that all your devices would start talking to each other in one cozy little network!
This was 3 years ago, maybe things have improved since.
Is there any reason telemarketers won't move their operations to Canada and place their calls from there?
It would be ironic as it would fulfill the prophecies of lost American jobs without anything being gained for the American public.
There can be another "legal" approach. Instead of sharing complete files on your system, you only share small parts of them. For instance, if you have a 5MB file on your drive, you only share 100K bytes of it.
l ).
Someone downloading the file would have to find 50 peers in order to reconstruct the entire file.
This appears to be legal since you are sharing only a small portion of the file (http://www.theregister.co.uk/content/6/32004.htm
It is kind of peculiar that all of their demos have a rather quick and abrupt hit/fall/tie/don't move much animation sequence. At first it is amusing but it appears all the animations are like that. Thought I'd point that out.
Isn't this what the broadband industry always wanted?
They are constantly searching for the killer app to migrate the masses onto broadband. It comes along and all they do is moan and complain about how it is hogging their network. Duh!
Unforunately, they seem to be too busy trying to shove unwanted "content" down consumers' throats in order to see *the* killer app right under their noses.
Mediocre code, let me count the ways...
Ever hear anything good said about MFC? What about ATL? How about their OLE implementation?
Have you ever heard what the Samba people have to say about Window's file and printer sharing protocol?
Here are my favorite quotes by Jeremy Allison (Samba Team) about the Windows network printing protocol:
"The implementation is APPALING",
"The implementers did not understand network protocols. At All."
and, "The print subsystem looks like it was cobbled together by sophomore (1st year) CS students"
What about their buggy Kerberos implementation where they sometimes publish bogus OIDs?
There are many more such examples...
What is to prevent this from turning into another CDDB? What is to prevent MusicBrainz from deciding to close their DB and start charging for use after they've milked the community to build the DB?
The DB implementation may be open source but without the information in it, the implementation is useless.
You might want to add execution history to the list.
A stack trace gives you the current calls but what were the previous 5 calls made?
An execution history would tell you what the last N calls were and in what order they occured.
It would be easy to implement as a series of stack snapshots.
The obstacle to micropayments' acceptance is not technical, it is phsycological.
Spending money requires involved mental cost/benefit balancing. Essentially, am I getting something for my money?
That a micropayment is micro does not mitigate that this mental balancing still needs to be done for each micropayment made - there is a definite fixed cost that is not dependent on the amount of money being spent.
As it turns out, it appears to be easier to pay one, bigger, lump sum ahead of time and then not need to think about it again.
Micropayments are doomed because they cause too much mental stress.
Linux is matching Windoze feature for feature till they are identical. It must do this to be a viable alternative to Windoze, which is what Linux's developers appear to want.
Once the two are equal, Linux will begin the second stage of Extending...
Linux just might beat Windoze at Microsoft's favorite game.
A now defunct company, First Access, did "Vicinity Authentication" in 1998. The product used a proprietary RF/IR card and sensor combination. The card could be worn anywhere and the sensor would hook up to RS-232. It was cryptographically secure and worked well. Several untis were sold to German and Australian companies. Unfortunately, First Access' management didn't know what to do with themselves and the company died a slow painful death.
so all it takes to shut down the U.S. military is a couple Wi-Fi transmitters?
I would hope the military would be able to cope with substantially more intereference than a lowly Wi-Fi access point. Otherwise, they might as well turn out the lights.
And the fundementals of the Internet are all open source.
Some that I can think of off the back of my hand:
bind, sendmail, telnet, ftp, ssh, apache, mozilla.
From reading through some of the posts it appears the RIAA is already winning the war. No one appears to find the implied illegality of copying a file in your possession an incongruous proposition anymore.
This is the core of the issue, not "pirates" or "artists" or other fictions. The problem with the RIAA and its discordant crusade is the fact that it runs against a widely accepted social norm - I have the right to copy my files. This is where the RIAA is weakest and is the only avenue for its defeat. If this idea is forgotten, the RIAA wins. Everyone else loses.
This guy should flat out admit that MS products are not engineered at all.
Some choice quotes by Jeremy Allison (Samba Team) about the Windows network printing protocol:
"The implementation is APPALING",
"The implementers did not understand network protocols. At All."
and, my favorite, "The print subsystem looks like it was cobbled together by sophomore (1st year) CS students"
Aren't hotmail accounts now part of the passport world?
If so, has anyone noticed the little fact that passport passwords are case insensitive?
Great security...
Maybe it is about time Microsoft engineers read the Software Engineering Code of Ethics. Specifically, their duty to the public at large.
How would they decide what is loggable and what is not? By looking at ports 80 and 25? The solution to that is simple, switch all your "sensitive" browsing to port 666. Use PGP for your email or perhaps use something as mundane as ICQ, or FTP drop points.
In addition you can have a script generating spurious emails and web browsing requests all day long so that you quickly overwhelm anyone's ability to actually log anything of substance (if you are really dedicated, you could probably generate 1GB of trash data a day).
Whoever is thinking about these moronic ideas appears to be technically ignorant.
I have never heard of a computer course where additional paper was refused a student. If this has occured, then you have a much bigger problem with the course staff. They are out to get you to begin with so you might as well opt out of the course and wait for better people.
Your Hitler invocation is gratuitous and as such merits no response.
"One proposed remedy being debated by record label executives is federal legislation requiring used-CD retailers to pay royalties on secondary sales of albums."
It's interesting how the federal government is seen as a convenient tool for furthering the music industry's profits. The article makes it appear that the moment a decision is made, the government will heel. No one bothers to point out how chilling this idea is.
"... Asking about fundamental principles is fine; asking for pieces of code or specific API details is IMO rediculous"
Unless this is a language course, or an introduction to computing...
"The few times I was subjected to these tests, I sure felt primitive erasing entire chunks of code after having realized I needed to insert something in the beginning ... I don't think any reasonably experienced programmer writes code entirely from top to bottom"
True, but any reasonably savvy college student (or, now that I think of it, anyone who has programmed BASIC with line numbers) would know to put nice large spaces between his lines of code to accomodate the occasional insert. That and the uncanny ability to write in ever smaller hand writing...
Quit whining about why you can't do tests and just slog through them like the millions who did it before you
Of course, performance doesn't suffer when you upgrade from a 5 y/o processor to a new top-of-the-line processor.
Most of the descriptions about speed up seem to be directly attributable to Intel, not Linux...
except there is no such thing as an open source Umm Kalthoum