...so eager to take Hubble down, when it's still contributing so much to astrophysics? The new space telescope isn't even ready for launch yet, and who knows if it will work at first go? I'd rather have Hubble as backup until the new one is working smoothly and flawlessly before even thinking about bringing it down. Capitalism and politics just don't mix well with science.
I really like this book. The internals of the CIFS protocol is not a subject for the faint hearted, but Chris has really tackled it well. This is just the right book for people like me who want to understand what is going on on their network at the bits and bytes level.
In the Samba Team we have been working on implementing the protocols that Chris describes in this book for the last 12 years or so, but we've always been doing this from sniffer traces and incomplete specifications. It was quite an interesting experience to see all this information distilled into such a readable format.
This isn't the sort of book that one buys grandma for Christmas, but if you run a Windows network and have been curious about what is happening inside all those network packets, how your computers find each other and what that weird error message really means then do yourself a favor and have a read.
Sorry, that's not a Beowulf Cluster. A Beowulf Cluster, by definition, is slapped together from heterogeneous hardware. The idea is to grab up all your outdated hardware that nobody's using (a 486 here, an AMD there), and make them all work together in a cluster.
If it's 73 Playstations, you have a homogenous architecture, and it's just a cluster.
Everytime KDE is mentioned, gnome advocates try and convince me why is GNOME is better, when it is NOT! Here is a detailed description WHY GNOME SUCKS KDE RULES!
1) The file dialog. KDE 0.x ALPHAs had a better file dialog than gnome! Today, the KDE one is the best file dialgog in existance, with influence from all desktops.
2) More apps! KDE comes with over 150 Apps in the full install, with applications for all fields, plus its sleak integration with non kde apps (eg gimp, openoffice) make things more consistant.
3) Configureable as hell. The KDE control center has loads of knobs/dials/sliders and boxes to fiddle with, yet keeps things elegent. In gnome, half the options don't exisit and you are rudley told "use gconf-editor n00b by gnome zealots" (not joking about this, telling the truth gets you a -1, troll and footnotes).
4) I-kandy! The Kde eye candy is really powerful, with styles such as dotNEt, mosfet liquid, kermamik, Crystal and more. Looking at art.gnome.org [gnome.org] reveals the same old theme in different colours. Since gnome dosen't provide a colour changing dialog for its widgets most "themes" are just colour changes. The Crystal from CVS is an Aqua killer, your eyes will want to love it.
5) Its development framework rocks. Take a good look at kioslaves, kparts, dcop, arts and qt and see why KDE is a programmer's dream. Modern c++, wonderful IDE [kdevelop.org], powerful command line scripting. Gnome gives you obsolete c, with a bunch of kludge libraries such as glib, Orbit, bonobo to hack together a application.
6)The defacto choice on Linux. All major Distributions support it by default. This means Mandrake, SuSE, Xandros, ArkLinux, Jamd, Lindows, Slackware, Knoppix, Gentoo and more. How many gnome ones can you mention (Redhat, sure if you like using server distros as your desktop Debian, nope thats the old 1.4 branch Gnoppix, a retarded knoppix rip off.) Most distributions offer gnome as an unsupported alternative.
Also, the only reason why gnome was created in the first place is null and void. Now that Novell has taken over Ximain you can expect VENDOR lock in. Want groupware for linux? Thats $300 a seat.
Get the new Mandrake 9.2 and see the Quality of KDE vs the Sorry state of Gnome 2.4 (and, they STILL haven't fixed that ****ing file dialog), not to mention they REMOVED ALL THE FEATURES. Gnome 2.2 is probably the only gnome version remotley close to kde, that is, KDE 2.0, not the KDE 3.2. I tried the "brokenboring" alpha of it and when it is released this december it will finally put Gnome out of it's misery and kill it off the Linux desktop.
I'm not really a "geek," nor do I play one on TV. But after looking through a book like this, I might just be motivated to try and become one. This book is one that appeals to the "mad scientist" in all of us, the one that is always looking for ways to build the better mouse trap or the perfect home "do it all device." While some of us less "handy types" would be better off not coming anywhere near this book, there are enough projects listed here that even someone with little or no hardware experience would find at least a handful of projects doable. Projects like the "Macintosh aquarium" or the laptop PC power supply. In fact the book is divided into Basic and Advanced Hacks and techniques, so if you've started off with a couple of the basic projects finished, you can move on to more advanced ones. Very cool.
And for each project, there is a graph for project cost, time and difficulty on the beginning page. For some projects, there's a list of what items you will need. There are also extensive step by step instructions for each "project," along with drawings, photos and diagrams. You'll love this book if you're one of those people who loves taking apart products and trying to "improve" upon their original design.
my review...
on
Debugging
·
· Score: 2, Informative
Mr. Agans' book presents real life experiences, or as he calls them war stories and humor filled comment/anecdotes.
I find myself chuckling and giggling along while reading this book, some of what he said brought back my own memories while working/debugging on my own software bug(s), or other people's bug(s) that I have somehow 'inherited' because they left the company, or are too busy on other projects to debug their own code. I like the metaphors that he uses to explain ideas or concepts that seems a bit too complicated to understand.
Mr. Agans made this very clear in the beginning of his book; the book is not a cover-it-all book, it is a general concept book on how to isolate, find, and debug something that has gone wrong. The principles presented by Mr. Agans can be applied to situations covering everyday life. He presented examples of well pump and light bulb, etc...
More experienced software/hardware engineers or more experienced problem solvers who read this book might find it covering bases that they already know, but the humor makes it worth while.
For some reason, nobody ever bothers to mention where the logs of the Slashdot IRC forums get posted. After the IRC interview with CmdrTaco and Hemos a few months ago, it took me some digging to figure out where the log wound up.
OK, so I admit that absolutely nothing about this book drew my attention EXCEPT the name of the author, Kevin Maney. Any devotee of his columns in USA Today knows his ability to tell a story. Yes, I knew I should be intrested in the life of Tom Watson -- he was, after all, one of the first "celebrity CEOs," although the term hadn't been invented. But I never thought I would be so fascinated by a man and his story.
This is a must read for anyone who wants to get a sense of what real leadership is all about. Watson was leading before there were books on leadership and studies on communictation. He was managing corporate culture before there were words for it. He saw his company -- and his employees -- through transitions that go well beyond mainframe vs. PC. When his technologies were rendered obsolete, he simply invented new ones.
Anyone with aspirations to lead should read this book. It's so action-packed that you may forget it's a true story. But it is. And I can't wait to see the movie.
Yes, but saying that it's something less than 7 million implies that it's in the ballpark of 7 million. Say, between 6.5 and 7 million.
I know this is a site for geeks, and thus we tend to look at things solely in mathematical terms, but it helps to be able to understand what people are really saying.
That's one of the best articles I've seen on this event.
I run one of the Grand Challenge teams,
Team Overbot [overbot.com].
We have a vehicle (a modified six wheel drive Polaris Ranger), a shop in Redwood City, funding,
equipment, and people. We're well along; the vehicle has most of its actuators and some of the sensors working, and about a third of the software is running. We're one of the five DARPA-accepted teams.
Many of us are Stanford alumni or students, but this is not a Stanford project.
We need three more good programmers in Silicon Valley. "No pay, some risk, a fraction of the prize." If you're interested, we want to see 1000 lines of C++ you're proud of. You'll need to put in at least 250 hours between now and March. Click here to join. [overbot.com]
Our basic technical approach is to build a rugged, reliable vehicle with conservative control strategies. Others may be faster, but we expect they'll get into trouble at high speed. Our top speed is 40MPH. The real problem with the Grand Challenge is not going fast on the easy parts; it's getting through the hard parts.
The 6WD chassis we're using is one of the most bump-tolerant platforms around. It can go over railroad ties at top speed without problems and
without going airborne. The center of gravity is low. The front and mid axles have independent suspension; the rear axle is a swing arm. This simplifies low-level vehicle control. All wheels can be driven, although at higher speeds, we will switch from 6WD to 4WD.
We have five computers on board. Three are small PC/104 machines, and two are Pentium 4 machines.
All run QNX (the OS for when it has to work.) All are industrial-strength ruggedized units. The actuators are all servomotors driven by industrial microcontrollers. All this hardware is off-the-shelf industrial control gear.
Sensors include LIDAR, doppler RADAR, sonars, cameras, INS, GPS, etc. Some of them are used in unusual ways. That's all I'll say about that.
The pathfinding strategy is indeed borrowed from video game technology. It's more structured than Brooks-type behavior based robotics, and it's less structured than Latoumbe-type planning. There are three layers of control; the top one we call the "back seat driver", because it has only advisory authority over the "driver".
We have road map and topo data onboard, but it's used more as a hint than as rigid guidance. We take the waypoints DARPA gives us (on a CD, at 0430 hrs the
morning of the race) and load it in. There's no offline preplanning. Wouldn't help in the real world.
If nobody wins this year, which is quite likely, we'll be back next year with a faster vehicle.
Reading through the responses to this technology, it seems that several issues are being addressed/readdressed:
1) Mandatory tagging of criminals - There seems to be a fundamental difference between tagging someone as part of their sentence and tagging someone after their sentence has been served (eg, after release from prison). The latter seems a dangerous trend since it indicates that the punishment for certain crimes may change in an arbitrary fashion, even *after* a criminal has served their time and been "rehabilitated" by societal punishments.
Granted, some crimes are heinous and deserve drastic punishments, but punishments should be known at the time of sentencing. Make the punishment as harsh as is warranted (eg, death sentence or consecutive life sentences effectively ensures that an offender never returns to society), but once a punishment has been fulfilled , no additional arbitrary punishments should be levied. Being unable to agree on what the rule-of-law is at the time of sentencing is very bad. A rule-of-law which is not transparent and clear is not a rule-of-law.
2) RFID technology is good|bad - Anyone who has spent their life thinking about technology knows that technology itself it neither our damnation nor our savior. It is amoral and merely a tool created and used by humans to leverage our ideas.
However, history has shown that we have a penchant for killing each other over issues with no obvious resolution (eg, Who's God is better, Who's skin color is better, etc). Technology just speeds up the process of letting us work out our differences, and, when that fails, subjugate/maim/torture/kill the enemy when they it is obvious that they will not take on our point of view.
3) The posters are "anti-technologist fear mongers" - since this crowd is generally very technology savvy, it is probably more likely that you misunderstand the message being articulated. People on Slashdot certainly seem to get more worked up that your general everyday nongeek citizenry. But that is likely because of the "slippery-slope" issues that are addressed. Looking at how humans use and misuse technology to abuse each other, it is often clear to those with a background in technology what form the abuses could take. Generally, it seems that humans eventually arrive at a solution better for everyone (eg, more tolerant), but only after a more short-term period which exploits the technology to the severe disadvantage of an unfortunate minority.
BTW, although annoying that the article is not based on RFID technology, that hardly matters in the grand scheme. GPS, RFID, biometrics, DRM, etc. are all just technologies. They have amazing potential for benefit of societies. But unless the potential for human-rights abuse is acknowledged and carefully monitored, things will get very bad before things get better.
No technology is without potential for abuse. Period.
This is just like the Mac version. Apple put lax restrictions on, people abused it, and Apple had to lock down iTunes a little bit more to avoid getting sued by the RIAA.
The record companies don't care how you get it, they just care that their cut from the sale gets to them.
McDonald's pays Apple 99 cents. Apple pays some RIAA peon 35 cents (and doesn't have to pay the ~30 cent credit card fee). RIAA doesn't care. It obviously isn't thinking of long-term improvement of distribution models, one that doesn't treat the consumer like a criminal (how long until us slashdotters have a mass penetentiary constructed for us!).
They're partnering with McDonald's to give away 1 billion songs. No matter how you cut it--hours, number of iPods filled, Libraries of Congress--that's an assload of music to give away.
This is just one reason why iTunes will likely kick the ass of its competitors for the Windows market--name one other player that has a promo even a tenth as big as this one. Apple is playing hardball, and there aren't many companies out there that can compete with an Apple/McDonald's combination, to say nothing of their partnership with AOL...
What happens when the software for reading these e-books is no longer supported? By using proprietary formats, it is inevitable that one day, the stuff in our nation's own library will be unreadable.
Only by creating an open standard, which anyone can choose to implement on the system of their choice (open source it, while you're at it!), can the information truly be timeless.
I have recently converted to the Linux way of doing things, after being fed up with M$ for too long.
In my department, we use proprietary software for all of our data reporting. I would like to use an open source program instead, but since I'm new to Linux, I'm not sure what's out there.
I'm hoping the slashdot community can help me on this one- what are some good plotting programs that run on Linux?
Geeks like Google because it doesn't try to do too much for them. Mundanes will probably like a super-powered MSN search because it will do everything for them. The best part is that there is room for both mindsets. Just as IE coming with windows does not prevent people from installing Mozilla or some other browser and using it nigh-exclusively (MSNM client, for example, still runs iexplore explicitly, rather than using the system's default browser) MSN search being the default will not stop you from using Google. Especially if you don't use IE. The fact that IE will be ever more closely tied to the OS in no way changes this.
I don't use MSN search at all any more. Even on the rare occasion I'm using IE (usually at school) and I somehow end up with MSN search results, I don't even look at them any more, I just close them and visit google. Or retype my URL:)
It actually depends on the expectations of the shareholders, if an IPO leads to the death of a company.
Normally a company is expected to be worth a certain multiple of its earnings (or better, the cashflow, because cashflow is difficult to forge). A normal multiple would be 10, which gives me a 10% return rate (I buy the company for 100 and get 10 out of it every year).
If google has USD 100 Mio of earnings, it's worth would be USD 1000 Mio, if valued this way. This of course would be a fair value, because it enables them to pay their investors an annual dividend of 10% of the stock price, even without any growth. In this scenario, they could stay in their search-engine-business, something they can (obviously) handle successful.
The problem is, google will not aim at a valuation of one billion, they will aim at a valuation that is about ten times higher. And that means, they will have to grow a lot in a short time, something that will propably kill them.
With IPv6 on the verge of being implemented, how will this affect domain names? There will be a plethora of IPs but less and less usable domain names to bind to. Unless of course people want to start using stuff like y4h00.com! or 47t4v15t4.com; registering unused domains for comerical purposes is a detriment to the world wide web, and also, forces developing groups to use awkward domain names.
p2p filesharing wont die - its the killer app for broadband. Not many people have seemed to grasp this fact yet but, theres not much use for ever-faster connections unless you have something to download. Websites are not going to increase in size that much, streaming video isnt really what gets people going (its just another tv channel) and games have their limit in bandwidth usage.
Now, give people free content without restrictions and you have something that everyone wants. Why are search engines the most popular websites? because the user types in what they want and gets it. From a users point of view, kazaa is the same as google except you can get everything that you cant get on google - its like the too hot for google channel. Are you seriously telling me that people dont want to be able to download all the music, films, porn, software, games, books and southpark they want for free!?!?! get real!
The only things that might kill p2p filesharing as we know it are:
Legislation and heavy enforcement (at the moment RIAA lawsuits and sen. Friz Hollings are restricted to the US only)
Networks collapsing thru abuse, free-loading, or (taking the law into their own hands) sabotage (they seem to be pretty resistant)
Governments (well in the UK anyway) are pushing broadband for all sorts of PHB reasons like "education" and obviously the ISPs - AOL etc are gonna try and sell it. Sen. Hollings is even for it. The absolute irony here is that the very same people who are pushing broadband so they can sell content are the same ones who will be fucked out of their money by filesharing! its brilliant, serves them right for their evil DRM plans.
Slashdot Mirror
Edition: paperback?
...so eager to take Hubble down, when it's still contributing so much to astrophysics? The new space telescope isn't even ready for launch yet, and who knows if it will work at first go? I'd rather have Hubble as backup until the new one is working smoothly and flawlessly before even thinking about bringing it down. Capitalism and politics just don't mix well with science.
I really like this book. The internals of the CIFS protocol is not a subject for the faint hearted, but Chris has really tackled it well. This is just the right book for people like me who want to understand what is going on on their network at the bits and bytes level.
In the Samba Team we have been working on implementing the protocols that Chris describes in this book for the last 12 years or so, but we've always been doing this from sniffer traces and incomplete specifications. It was quite an interesting experience to see all this information distilled into such a readable format.
This isn't the sort of book that one buys grandma for Christmas, but if you run a Windows network and have been curious about what is happening inside all those network packets, how your computers find each other and what that weird error message really means then do yourself a favor and have a read.
Andrew Tridgell
Samba Team
Sorry, that's not a Beowulf Cluster. A Beowulf Cluster, by definition, is slapped together from heterogeneous hardware. The idea is to grab up all your outdated hardware that nobody's using (a 486 here, an AMD there), and make them all work together in a cluster. If it's 73 Playstations, you have a homogenous architecture, and it's just a cluster.
Everytime KDE is mentioned, gnome advocates try and convince me why is GNOME is better, when it is NOT! Here is a detailed description WHY GNOME SUCKS KDE RULES!
1) The file dialog.
KDE 0.x ALPHAs had a better file dialog than gnome! Today, the KDE one is the best file dialgog in existance, with influence from all desktops.
2) More apps!
KDE comes with over 150 Apps in the full install, with applications for all fields, plus its sleak integration with non kde apps (eg gimp, openoffice) make things more consistant.
3) Configureable as hell.
The KDE control center has loads of knobs/dials/sliders and boxes to fiddle with, yet keeps things elegent. In gnome, half the options don't exisit and you are rudley told "use gconf-editor n00b by gnome zealots" (not joking about this, telling the truth gets you a -1, troll and footnotes).
4) I-kandy!
The Kde eye candy is really powerful, with styles such as dotNEt, mosfet liquid, kermamik, Crystal and more. Looking at art.gnome.org [gnome.org] reveals the same old theme in different colours. Since gnome dosen't provide a colour changing dialog for its widgets most "themes" are just colour changes. The Crystal from CVS is an Aqua killer, your eyes will want to love it.
5) Its development framework rocks.
Take a good look at kioslaves, kparts, dcop, arts and qt and see why KDE is a programmer's dream. Modern c++, wonderful IDE [kdevelop.org], powerful command line scripting. Gnome gives you obsolete c, with a bunch of kludge libraries such as glib, Orbit, bonobo to hack together a application.
6)The defacto choice on Linux. All major Distributions support it by default. This means Mandrake, SuSE, Xandros, ArkLinux, Jamd, Lindows, Slackware, Knoppix, Gentoo and more. How many gnome ones can you mention (Redhat, sure if you like using server distros as your desktop Debian, nope thats the old 1.4 branch Gnoppix, a retarded knoppix rip off.) Most distributions offer gnome as an unsupported alternative.
Also, the only reason why gnome was created in the first place is null and void. Now that Novell has taken over Ximain you can expect VENDOR lock in. Want groupware for linux? Thats $300 a seat.
Get the new Mandrake 9.2 and see the Quality of KDE vs the Sorry state of Gnome 2.4 (and, they STILL haven't fixed that ****ing file dialog), not to mention they REMOVED ALL THE FEATURES. Gnome 2.2 is probably the only gnome version remotley close to kde, that is, KDE 2.0, not the KDE 3.2. I tried the "brokenboring" alpha of it and when it is released this december it will finally put Gnome out of it's misery and kill it off the Linux desktop.
I'm not really a "geek," nor do I play one on TV. But after looking through a book like this, I might just be motivated to try and become one. This book is one that appeals to the "mad scientist" in all of us, the one that is always looking for ways to build the better mouse trap or the perfect home "do it all device." While some of us less "handy types" would be better off not coming anywhere near this book, there are enough projects listed here that even someone with little or no hardware experience would find at least a handful of projects doable. Projects like the "Macintosh aquarium" or the laptop PC power supply. In fact the book is divided into Basic and Advanced Hacks and techniques, so if you've started off with a couple of the basic projects finished, you can move on to more advanced ones. Very cool.
And for each project, there is a graph for project cost, time and difficulty on the beginning page. For some projects, there's a list of what items you will need. There are also extensive step by step instructions for each "project," along with drawings, photos and diagrams. You'll love this book if you're one of those people who loves taking apart products and trying to "improve" upon their original design.
Mr. Agans' book presents real life experiences, or as he calls them war stories and humor filled comment/anecdotes.
I find myself chuckling and giggling along while reading this book, some of what he said brought back my own memories while working/debugging on my own software bug(s), or other people's bug(s) that I have somehow 'inherited' because they left the company, or are too busy on other projects to debug their own code. I like the metaphors that he uses to explain ideas or concepts that seems a bit too complicated to understand.
Mr. Agans made this very clear in the beginning of his book; the book is not a cover-it-all book, it is a general concept book on how to isolate, find, and debug something that has gone wrong. The principles presented by Mr. Agans can be applied to situations covering everyday life. He presented examples of well pump and light bulb, etc...
More experienced software/hardware engineers or more experienced problem solvers who read this book might find it covering bases that they already know, but the humor makes it worth while.
For some reason, nobody ever bothers to mention where the logs of the Slashdot IRC forums get posted. After the IRC interview with CmdrTaco and Hemos a few months ago, it took me some digging to figure out where the log wound up.
For those who can't make the chat, the log will eventually be at http://www.slashnet.org/forums/
Editors: After the chat is over, any chance of having the log URL linked to the story text as an update?
VT isn't the one selling these systems... Apple is.
No, Apple sold the machines to VT in the first place. MacMall is selling them.
OK, so I admit that absolutely nothing about this book drew my attention EXCEPT the name of the author, Kevin Maney. Any devotee of his columns in USA Today knows his ability to tell a story. Yes, I knew I should be intrested in the life of Tom Watson -- he was, after all, one of the first "celebrity CEOs," although the term hadn't been invented. But I never thought I would be so fascinated by a man and his story.
This is a must read for anyone who wants to get a sense of what real leadership is all about. Watson was leading before there were books on leadership and studies on communictation. He was managing corporate culture before there were words for it. He saw his company -- and his employees -- through transitions that go well beyond mainframe vs. PC. When his technologies were rendered obsolete, he simply invented new ones.
Anyone with aspirations to lead should read this book. It's so action-packed that you may forget it's a true story. But it is. And I can't wait to see the movie.
Yes, but saying that it's something less than 7 million implies that it's in the ballpark of 7 million. Say, between 6.5 and 7 million.
I know this is a site for geeks, and thus we tend to look at things solely in mathematical terms, but it helps to be able to understand what people are really saying.
Is anyone surprised that the 10 million promised addresses boils down to less than 7 million after removing duplicates?
Yes, I'm very surprised. I would have expected it to boil down to something like 4-5 million.
I run one of the Grand Challenge teams, Team Overbot [overbot.com]. We have a vehicle (a modified six wheel drive Polaris Ranger), a shop in Redwood City, funding, equipment, and people. We're well along; the vehicle has most of its actuators and some of the sensors working, and about a third of the software is running. We're one of the five DARPA-accepted teams.
Many of us are Stanford alumni or students, but this is not a Stanford project.
Our basic technical approach is to build a rugged, reliable vehicle with conservative control strategies. Others may be faster, but we expect they'll get into trouble at high speed. Our top speed is 40MPH. The real problem with the Grand Challenge is not going fast on the easy parts; it's getting through the hard parts.
The 6WD chassis we're using is one of the most bump-tolerant platforms around. It can go over railroad ties at top speed without problems and without going airborne. The center of gravity is low. The front and mid axles have independent suspension; the rear axle is a swing arm. This simplifies low-level vehicle control. All wheels can be driven, although at higher speeds, we will switch from 6WD to 4WD.
We have five computers on board. Three are small PC/104 machines, and two are Pentium 4 machines. All run QNX (the OS for when it has to work.) All are industrial-strength ruggedized units. The actuators are all servomotors driven by industrial microcontrollers. All this hardware is off-the-shelf industrial control gear.
Sensors include LIDAR, doppler RADAR, sonars, cameras, INS, GPS, etc. Some of them are used in unusual ways. That's all I'll say about that.
The pathfinding strategy is indeed borrowed from video game technology. It's more structured than Brooks-type behavior based robotics, and it's less structured than Latoumbe-type planning. There are three layers of control; the top one we call the "back seat driver", because it has only advisory authority over the "driver".
We have road map and topo data onboard, but it's used more as a hint than as rigid guidance. We take the waypoints DARPA gives us (on a CD, at 0430 hrs the morning of the race) and load it in. There's no offline preplanning. Wouldn't help in the real world.
If nobody wins this year, which is quite likely, we'll be back next year with a faster vehicle.
Post questions and I'll answer them here.
John Nagle
Team Overbot
Reading through the responses to this technology, it seems that several issues are being addressed/readdressed:
1) Mandatory tagging of criminals - There seems to be a fundamental difference between tagging someone as part of their sentence and tagging someone after their sentence has been served (eg, after release from prison). The latter seems a dangerous trend since it indicates that the punishment for certain crimes may change in an arbitrary fashion, even *after* a criminal has served their time and been "rehabilitated" by societal punishments.
Granted, some crimes are heinous and deserve drastic punishments, but punishments should be known at the time of sentencing. Make the punishment as harsh as is warranted (eg, death sentence or consecutive life sentences effectively ensures that an offender never returns to society), but once a punishment has been fulfilled , no additional arbitrary punishments should be levied. Being unable to agree on what the rule-of-law is at the time of sentencing is very bad. A rule-of-law which is not transparent and clear is not a rule-of-law.
2) RFID technology is good|bad - Anyone who has spent their life thinking about technology knows that technology itself it neither our damnation nor our savior. It is amoral and merely a tool created and used by humans to leverage our ideas.
However, history has shown that we have a penchant for killing each other over issues with no obvious resolution (eg, Who's God is better, Who's skin color is better, etc). Technology just speeds up the process of letting us work out our differences, and, when that fails, subjugate/maim/torture/kill the enemy when they it is obvious that they will not take on our point of view.
3) The posters are "anti-technologist fear mongers" - since this crowd is generally very technology savvy, it is probably more likely that you misunderstand the message being articulated. People on Slashdot certainly seem to get more worked up that your general everyday nongeek citizenry. But that is likely because of the "slippery-slope" issues that are addressed. Looking at how humans use and misuse technology to abuse each other, it is often clear to those with a background in technology what form the abuses could take. Generally, it seems that humans eventually arrive at a solution better for everyone (eg, more tolerant), but only after a more short-term period which exploits the technology to the severe disadvantage of an unfortunate minority.
BTW, although annoying that the article is not based on RFID technology, that hardly matters in the grand scheme. GPS, RFID, biometrics, DRM, etc. are all just technologies. They have amazing potential for benefit of societies. But unless the potential for human-rights abuse is acknowledged and carefully monitored, things will get very bad before things get better.
No technology is without potential for abuse. Period.
This is just like the Mac version. Apple put lax restrictions on, people abused it, and Apple had to lock down iTunes a little bit more to avoid getting sued by the RIAA.
The record companies don't care how you get it, they just care that their cut from the sale gets to them.
McDonald's pays Apple 99 cents. Apple pays some RIAA peon 35 cents (and doesn't have to pay the ~30 cent credit card fee). RIAA doesn't care. It obviously isn't thinking of long-term improvement of distribution models, one that doesn't treat the consumer like a criminal (how long until us slashdotters have a mass penetentiary constructed for us!).
This is just one reason why iTunes will likely kick the ass of its competitors for the Windows market--name one other player that has a promo even a tenth as big as this one. Apple is playing hardball, and there aren't many companies out there that can compete with an Apple/McDonald's combination, to say nothing of their partnership with AOL...
What happens when the software for reading these e-books is no longer supported? By using proprietary formats, it is inevitable that one day, the stuff in our nation's own library will be unreadable.
Only by creating an open standard, which anyone can choose to implement on the system of their choice (open source it, while you're at it!), can the information truly be timeless.
I have recently converted to the Linux way of doing things, after being fed up with M$ for too long.
In my department, we use proprietary software for all of our data reporting. I would like to use an open source program instead, but since I'm new to Linux, I'm not sure what's out there.
I'm hoping the slashdot community can help me on this one- what are some good plotting programs that run on Linux?
Geeks like Google because it doesn't try to do too much for them. Mundanes will probably like a super-powered MSN search because it will do everything for them. The best part is that there is room for both mindsets. Just as IE coming with windows does not prevent people from installing Mozilla or some other browser and using it nigh-exclusively (MSNM client, for example, still runs iexplore explicitly, rather than using the system's default browser) MSN search being the default will not stop you from using Google. Especially if you don't use IE. The fact that IE will be ever more closely tied to the OS in no way changes this.
I don't use MSN search at all any more. Even on the rare occasion I'm using IE (usually at school) and I somehow end up with MSN search results, I don't even look at them any more, I just close them and visit google. Or retype my URL :)
It actually depends on the expectations of the shareholders, if an IPO leads to the death of a company. Normally a company is expected to be worth a certain multiple of its earnings (or better, the cashflow, because cashflow is difficult to forge). A normal multiple would be 10, which gives me a 10% return rate (I buy the company for 100 and get 10 out of it every year). If google has USD 100 Mio of earnings, it's worth would be USD 1000 Mio, if valued this way. This of course would be a fair value, because it enables them to pay their investors an annual dividend of 10% of the stock price, even without any growth. In this scenario, they could stay in their search-engine-business, something they can (obviously) handle successful. The problem is, google will not aim at a valuation of one billion, they will aim at a valuation that is about ten times higher. And that means, they will have to grow a lot in a short time, something that will propably kill them.
With IPv6 on the verge of being implemented, how will this affect domain names? There will be a plethora of IPs but less and less usable domain names to bind to. Unless of course people want to start using stuff like y4h00.com! or 47t4v15t4.com; registering unused domains for comerical purposes is a detriment to the world wide web, and also, forces developing groups to use awkward domain names.
Now, give people free content without restrictions and you have something that everyone wants. Why are search engines the most popular websites? because the user types in what they want and gets it. From a users point of view, kazaa is the same as google except you can get everything that you cant get on google - its like the too hot for google channel. Are you seriously telling me that people dont want to be able to download all the music, films, porn, software, games, books and southpark they want for free!?!?! get real!
The only things that might kill p2p filesharing as we know it are:
Governments (well in the UK anyway) are pushing broadband for all sorts of PHB reasons like "education" and obviously the ISPs - AOL etc are gonna try and sell it. Sen. Hollings is even for it. The absolute irony here is that the very same people who are pushing broadband so they can sell content are the same ones who will be fucked out of their money by filesharing! its brilliant, serves them right for their evil DRM plans.