So, if you lose some weight, you could slip it off, pass it to your buddy who gets it in contact with his skin within 15 seconds, go do your crime, and get away with it.
So... losing weight will reduce the size of your hand so that it's circumference is the same as or less than that of your wrist?
Not bloody likely.
Now if you'd said inmates who know Kung Fu may be able to slip off the bracelet, I'd offer a different response.
No more TV for you.
Most people would be unable to remove a simple plastic hospital bracelet without proper tools, let alone something constructed with braided stainless steel and an RFID tag, and that's been strapped to your wrist by a prison guard with no beside manner.
Since we're on the subject... I have just patented the.sig file.
^_^
And since we are on the subject, a sig is not a set of extraneous ascii characters sometimes followed by a name. A sig is denoted (putting on my pointy pedantic Slashdot Public Service Announcement hat, here) by a
dash dash space return
followed by a name, extraneous ascii characters, advertising, and/or a pity quotation that is incidental to the content of the message. It facilitates email and usenet clients from appyling syntax colouring to the incidental text to distinguish it from normal text, and further allows for it's automated removal from quoted text when a reply is made. Among other things.
Slashdot makes allowances for sigs so that those of use who use the Disable sigs don't have to view them. Among other things.
So, with the rise of grown diamonds, I look forward to many advances in easy to use cooking gear.
If you're looking for advances in cooking gear, your time would be best served reading history books. Most everything used in the kitchen as we know it today was created a hundred years or more ago (fancy ergonomic handles excluded).
Teflon or most any "coated surfaced" gear is especially nasty, unhealthy and offers a false economy of convenience. It doesn't stand up to high heat, it's limited in the kinds of food that can be cooked in it ( acidic foods or those with high water content, for example, often react (badly) with the coating), scratches easily, and is marketed to those who don't cook much. It's highly unusual to see any teflon gear in a professional kitchen.
If you're looking for "non-stick/easy-to-clean", there's nothing that comes close to properly seasoned steel (think "carbon deposit on a wok" or "cast iron baking/frying pan"). If you don't need something to last you a hundred years, use stainless steel. Nothing sticks to it either. The reason you see stainless and not carbon steel in a professional kitchen is women. Historically, chefs were always men because women simply couldn't lift huge pots of stock, or handle the iron pots and pans.
Which brings us back to the topic at hand: if diamonds are a girl's best friend, and a dog is man's best friend, there's not much chance of either side really understanding the other, is there?
My Theory(TM) is that Apple, while maintaining its Hip and Kewl image, will begin to offer products that compete more directly with commodity hardware in the same way that manufacturers of commodity hardware will seek to develop their own Hip and Kewl image. The huge success of the iPod has pushed Apple into the general marketplace where the unwashed masses shop, and the mini is accelerating that push. Until there's an Apple Store on every corner like Starbuck's, Apple would be hard pressed not to build on their success and expand their product line.
The issue as to whether this is a slippery slope, or an asymptotic curve will be answered in a few years time no doubt.
In the interim we can scratch our heads examining the extent to which features found in either of OS X, Linux or Windows converge.
... he figured it was about 6-7 hours a day that people used a Microsoft product. He went on to state that there were, therefore, 18 or so hours a day that people weren't using Microsoft software, and HE WANTED THOSE 18 HOURS!.
He's got most of those hours already.
We're busy trying to figure out why we had problems for the first 6-7 hours!
PHP was made by taking a cute language for embedding a broken imitation of Perl-esque syntax in-between HTML and extending it with bajillions of functions that badly needed to be namespaced. It never provided anything useful that Perl couldn't, except that it made newbies comfortable by making them feel like they're in "HTML land" instead of "Programming language land."
I'll requote as I share the same opinion. In fact, I'd offer the argument that contrary to the "right tool for the job" advice that gets bandied about so frequently, if you write a lot of code in Perl, it's often more efficient to keep writing code in Perl, as there's very few areas where Perl doesn't shine.
My personal opinions aside, I wonder how you would explain the widespread and seemingly increasing usage (and popularity) of PHP?
Our household has 4 (working) computers, soon there will be five... wouldn't stave off the inevitable power crunch... [a]s things stand now: CATASTROPHE.
And moving from a catastrophe to a power crunch isn't an improvement?
Tell ya what. If you agree to start collecting rainwater, I'll turn off a few night lamps in my house and perform fewer Google searches, and you can get that fifth computer working without feeling guilty, knowing that together we've restored balance to the universe.
Efficient energy usage is a complex subject that demands context, perspective and careful analysis. Hyperbole has no place in the discussion.
The Internet Explorer, Recycle Bin, "My Network places" icons are links, not shortcuts, right?
WTF? The Recycle Bin, Network Places, etc. are not icons, links, or shortcuts. They're namespaces.
Since you've googled for Hard links & junctions, you may want to google some more and try to learn the differences between icons, links (aka "shortcuts"), namespaces, symbolic links, hard links and reparse points.
Cygwin offers an implementation of symbolic links which works nicely, not only within a Cygwin environment (shell + the standard unix toolset) but also in Windows generally. Windows, on the other hand, doesn't support "real" symlinks, but does have native support for hard links. Reparse points/junctions, on the other hand, are only partially supported and have limitations. Those limitations exist whether the junction was created natively (using the "Mount in this NTFS folder" approach), the ResKit linkd.exe program, or SysInternal's junction utility.
I hope I don't get a troll rating on this, but I think that as any kernel grows, it becomes exponentially more difficult to project all of the possible interactions between components.
Actually, that's not the case at all according to this new NY Times Article
...the Purdue researchers say the real explosive secret lies in the hull, or pericarp... In some varieties, the pericarp becomes more moistureproof as it is heated, sealing in the steam until the pressure gets so high that the hull fractures and the kernel goes pop.
In other varieties that don't undergo heat-induced change, the moisture escapes, the hull never breaks and then the kernel goes pfffft.
What? You're complaining that Longhorn's ability to distinguish file types by using something other than a registered 3-letter extension is a Bad Thing?
For Microsoft, I'd say that was Damned Fine Progress! Windows users everywhere will soon be able to make better use of files named STARTHERE.EXE.TXT, and may even be able to double click those funny little files that start with #!/bin/bash.
In stark contrast to some of his peers, Flake recently reminded us that "data is not information; information is not knowledge; knowledge is not wisdom." Asked by Gary Price if the internet would replace librarians, he replied,
"Search engines can give you more data than you'll ever need, and a lot of valuable information as well, but they aren't even in the running when it comes to knowledge and wisdom."
I wish to complain on the strongest possible terms about the previous post. Some of my best friends are Star Trek fans, and not one owns a tribble. And only a few own parrots.
All you need is a few lawyers to file these lawsuits and one or two supervise them all. It's anyone's guess how large Microsoft's legal department is, but between in-house counsel/staff and the all attorneys working for law firms hired by Microsoft to represent them in their never ending litigation, I doubt anyone is working overtime.
As for the cost, most likely it's a drop in the bucket when compared to what's already been spent or is being spent on antitrust cases. Whatever the cost, the bankers are used to it, the shareholders are used to it, as so is everyone else. And when one considers the PR value of these lawsuits, I doubt anyone would raise an eyebrow if real money was at stake.
By posting here & now you're letting us know your opinion. We read it because we're interested in comparing your views to ours... Bloggers are just doing that too...
I'm not sure whether I should be amused or amazed after reading this. Slashdot being compared to a blog? Sorry, but my interpretation of a blog is a self-absorbed self-referential monologue about one or more subjects that's been transcribed and marked up with html. Sort of like public masturbation, but with css styling.
A typical Slashdot page has everything in common with a usenet thread. For the web weenies who don't know what usenet is or those equally uninformed who proclaim it dead, usenet is sortofkindof like a discussion board, but without the board.
Personally, I enjoy reading anything that's well-written. If I wanted an editorial, I'd check out The NY Times, or Harpers. If I wanted to be informed or amused, there's lots in print and available for free on the web. And aside from an occasional salicious or informative tidbit, mostly time-wasting amusement, if that. Put another way blogging is to good writing (to steal a pithy quote) like a dog walking on its hind legs. It's not done very often, and when it is, it's not done very well.
Slashdot Mirror
So, if you lose some weight, you could slip it off, pass it to your buddy who gets it in contact with his skin within 15 seconds, go do your crime, and get away with it.
... losing weight will reduce the size of your hand so that it's circumference is the same as or less than that of your wrist?
So
Not bloody likely.
Now if you'd said inmates who know Kung Fu may be able to slip off the bracelet, I'd offer a different response.
No more TV for you.
Most people would be unable to remove a simple plastic hospital bracelet without proper tools, let alone something constructed with braided stainless steel and an RFID tag, and that's been strapped to your wrist by a prison guard with no beside manner.
^_^
And since we are on the subject, a sig is not a set of extraneous ascii characters sometimes followed by a name. A sig is denoted (putting on my pointy pedantic Slashdot Public Service Announcement hat, here) by a
followed by a name, extraneous ascii characters, advertising, and/or a pity quotation that is incidental to the content of the message. It facilitates email and usenet clients from appyling syntax colouring to the incidental text to distinguish it from normal text, and further allows for it's automated removal from quoted text when a reply is made. Among other things.
Slashdot makes allowances for sigs so that those of use who use the Disable sigs don't have to view them. Among other things.
If you're looking for advances in cooking gear, your time would be best served reading history books. Most everything used in the kitchen as we know it today was created a hundred years or more ago (fancy ergonomic handles excluded).
Teflon or most any "coated surfaced" gear is especially nasty, unhealthy and offers a false economy of convenience. It doesn't stand up to high heat, it's limited in the kinds of food that can be cooked in it ( acidic foods or those with high water content, for example, often react (badly) with the coating), scratches easily, and is marketed to those who don't cook much. It's highly unusual to see any teflon gear in a professional kitchen.
If you're looking for "non-stick/easy-to-clean", there's nothing that comes close to properly seasoned steel (think "carbon deposit on a wok" or "cast iron baking/frying pan"). If you don't need something to last you a hundred years, use stainless steel. Nothing sticks to it either. The reason you see stainless and not carbon steel in a professional kitchen is women. Historically, chefs were always men because women simply couldn't lift huge pots of stock, or handle the iron pots and pans.
Which brings us back to the topic at hand: if diamonds are a girl's best friend, and a dog is man's best friend, there's not much chance of either side really understanding the other, is there?
My Theory(TM) is that Apple, while maintaining its Hip and Kewl image, will begin to offer products that compete more directly with commodity hardware in the same way that manufacturers of commodity hardware will seek to develop their own Hip and Kewl image. The huge success of the iPod has pushed Apple into the general marketplace where the unwashed masses shop, and the mini is accelerating that push. Until there's an Apple Store on every corner like Starbuck's, Apple would be hard pressed not to build on their success and expand their product line.
The issue as to whether this is a slippery slope, or an asymptotic curve will be answered in a few years time no doubt.
In the interim we can scratch our heads examining the extent to which features found in either of OS X, Linux or Windows converge.
... relatively poor ... way more huge ... way too ugly"
A thoughtful analysis if ever I read one.
Eating isn't the only thing you shouldn't do at your desk.
... he figured it was about 6-7 hours a day that people used a Microsoft product. He went on to state that there were, therefore, 18 or so hours a day that people weren't using Microsoft software, and HE WANTED THOSE 18 HOURS!.
He's got most of those hours already.
We're busy trying to figure out why we had problems for the first 6-7 hours!
PHP was made by taking a cute language for embedding a broken imitation of Perl-esque syntax in-between HTML and extending it with bajillions of functions that badly needed to be namespaced. It never provided anything useful that Perl couldn't, except that it made newbies comfortable by making them feel like they're in "HTML land" instead of "Programming language land."
I'll requote as I share the same opinion. In fact, I'd offer the argument that contrary to the "right tool for the job" advice that gets bandied about so frequently, if you write a lot of code in Perl, it's often more efficient to keep writing code in Perl, as there's very few areas where Perl doesn't shine.
My personal opinions aside, I wonder how you would explain the widespread and seemingly increasing usage (and popularity) of PHP?
And moving from a catastrophe to a power crunch isn't an improvement?
Tell ya what. If you agree to start collecting rainwater, I'll turn off a few night lamps in my house and perform fewer Google searches, and you can get that fifth computer working without feeling guilty, knowing that together we've restored balance to the universe.
Efficient energy usage is a complex subject that demands context, perspective and careful analysis. Hyperbole has no place in the discussion.
it tends to become a mass-babbling, where several adults mumble the same things over and over
So the singing of birds is like talk radio?
WTF? The Recycle Bin, Network Places, etc. are not icons, links, or shortcuts. They're namespaces.
Since you've googled for Hard links & junctions, you may want to google some more and try to learn the differences between icons, links (aka "shortcuts"), namespaces, symbolic links, hard links and reparse points.
Cygwin offers an implementation of symbolic links which works nicely, not only within a Cygwin environment (shell + the standard unix toolset) but also in Windows generally. Windows, on the other hand, doesn't support "real" symlinks, but does have native support for hard links. Reparse points/junctions, on the other hand, are only partially supported and have limitations. Those limitations exist whether the junction was created natively (using the "Mount in this NTFS folder" approach), the ResKit linkd.exe program, or SysInternal's junction utility.
Actually, that's not the case at all according to this new NY Times Article
...the Purdue researchers say the real explosive secret lies in the hull, or pericarp ... In some varieties, the pericarp becomes more moistureproof as it is heated, sealing in the steam until the pressure gets so high that the hull fractures and the kernel goes pop.
In other varieties that don't undergo heat-induced change, the moisture escapes, the hull never breaks and then the kernel goes pfffft.
Yeah, but you cheated and used a calculator, hence the off by one error.
The correct answer is 2. Only 2 version updates separate them.
What? You're complaining that Longhorn's ability to distinguish file types by using something other than a registered 3-letter extension is a Bad Thing?
For Microsoft, I'd say that was Damned Fine Progress! Windows users everywhere will soon be able to make better use of files named STARTHERE.EXE.TXT, and may even be able to double click those funny little files that start with #!/bin/bash.
Who knows what else they might be able to do?
In stark contrast to some of his peers, Flake recently reminded us that "data is not information; information is not knowledge; knowledge is not wisdom." Asked by Gary Price if the internet would replace librarians, he replied,
"Search engines can give you more data than you'll ever need, and a lot of valuable information as well, but they aren't even in the running when it comes to knowledge and wisdom."
Zen and the Art of Search, it seems.
Either that, or the triumph of optimism over experience.
set -o vi
Discuss among yourselves.
With an attitude like that, you'll never work in advertising.
And you can forget about politics.
But that's progress. innit?
I don't think anyone's pointed it out yet, but I believe in Canada it's still the case that change for a fiver is two 2's and a 1.
Dear Sir,
I wish to complain on the strongest possible terms about the previous post. Some of my best friends are Star Trek fans, and not one owns a tribble. And only a few own parrots.
Yours etc.,
Brigadier Arthur Gormanstrop (Mrs).
All you need is a few lawyers to file these lawsuits and one or two supervise them all. It's anyone's guess how large Microsoft's legal department is, but between in-house counsel/staff and the all attorneys working for law firms hired by Microsoft to represent them in their never ending litigation, I doubt anyone is working overtime.
As for the cost, most likely it's a drop in the bucket when compared to what's already been spent or is being spent on antitrust cases. Whatever the cost, the bankers are used to it, the shareholders are used to it, as so is everyone else. And when one considers the PR value of these lawsuits, I doubt anyone would raise an eyebrow if real money was at stake.
Apparently, the correct spelling of his name isn't as well known.
Woohoo! More wizards!
Now you too can become a Microsoft Widows Server 2003 Administrator. Who said you can't have both security and easy of use? Err ... or can you?
I'm not sure whether I should be amused or amazed after reading this. Slashdot being compared to a blog? Sorry, but my interpretation of a blog is a self-absorbed self-referential monologue about one or more subjects that's been transcribed and marked up with html. Sort of like public masturbation, but with css styling.
A typical Slashdot page has everything in common with a usenet thread. For the web weenies who don't know what usenet is or those equally uninformed who proclaim it dead, usenet is sortofkindof like a discussion board, but without the board.
Personally, I enjoy reading anything that's well-written. If I wanted an editorial, I'd check out The NY Times, or Harpers. If I wanted to be informed or amused, there's lots in print and available for free on the web. And aside from an occasional salicious or informative tidbit, mostly time-wasting amusement, if that. Put another way blogging is to good writing (to steal a pithy quote) like a dog walking on its hind legs. It's not done very often, and when it is, it's not done very well.