Duh!!! Rely on closed-source software and you risk this very problem. We all know that. Developers MOST OF ALL should INSIST on open-source for tools and libraries.
It's getting deep in here! This story just doesn't hold water and it won't scale (imagine a beo... nope, too corny even for me). By the time we see the tail end of this one, it'll smell pretty fishy. I think the data has been salted. Whoever believes this one is smoking a lot of sea weed, and personally I've had enough to make my head swim! I think this needs to be sent to a watery grave before the sharks catch the smell.
Now that sounds logical. Everything that's ever happened in the history of the Earth has been the result of some combination of money and the female anatomy. Actually, money is one of them, so really, *everything* is the result of girls, and/or the lack thereof (think slashdot). It's true!
Balmer would dance across the stage with all those explosives strapped on and detonate right as he passes the podium. DEVELOPERS DEVELOPERS DEVELOPERS DEVELOPERS DEVELOPERS *BOOM*
It wouldn't be safe. Funny as hell, but very unsafe.
I think we all know why MS is refusing to provide Hebrew support. Do you think they'd refuse if there was actual competition? Doubtful. Sounds a little like monopoly abuse to me. I would say Isreal is more justified in it's position than MS is in theirs.
Parent post is exactly correct. Copy protection can't work unless there is legislation making it illegal to circumvent, just like locked doors won't keep thieves out unless there is legislation to make it illegal to break and enter.
Whoever modded that down needs to be flogged with the clue stick.
Those would, I believe, fall under the antique firearms clause, so they are non-restricted. Anything made before 1898 that doesn't use 'fixed ammunition' is considered antique, as is any replica of said firearms (the blunderbuss is a replica?)
And you would have likely just wasted it. 4 ounces is quite a bit when you're talking about black powder (or a synthetic thereof), and that barrel is pretty short.
As of about 10 years ago, federal law stated that a person could own a breach loader no more than.50 cal without a special license. HOWEVER, there were no restrictions that I could find on muzzle loaders. Want a cannon with an 8-foot bore? Go for it, just as long as the projectile and charge go in the same way they come out. Technically, that thing is 50-state legal.
"4 - What you are saying about frequencies applies to RF. This is not about RF. The mention of a high frequency, relatively unused ISM band probably refers to the EM side effects of the devices. (a 10Ghz oscillator, even if it's used via induction, sitll creates a 10Ghz EM signal)"
That's the one that's hanging me up. Wouldn't it then be possible to evesdrop on any communication from a good distance away by using conventional radio equipment?
The stated point of this technology seems to be low power consumption and security (because of the very short range). Point number two is nulled by EM radiation, and point one can't be that hard to achieve with ordinary radio technology... can it?
"It does remain viable for a few select uses, though: small widgets..."
What do you mean by small widgets? My knee jerk reaction to that statement is that if it's small, you probably should NOT do it in Java.
"...but those things it does it does very poorly."
I'm speaking from.NET experience, but I think it applies just fine...
I've fallen in love with the memory allocation stuff that leads to garbage collection. I like using references to everything. Complex applications eventually end up needing some form of reference tracking to make the complexity manageable. However, I miss two things:
1) Destructors (proper ones).
2) Real-time object disposal.
I HATE background garbage collection! In many cases it works fine, but I hate it! Just give me real destructors that fire as soon as the last reference goes out of scope, and then dispose of that sucker in real time. Because of garbage collection, some classes have a Dispose() method, which must be called explicitly, but you don't have any way to know if you hold the last reference (if you keep track, you may as well be writing in c++), and if you call it early, you just effectively created a dangling pointer. An object has no idea whether it's referenced or not, has no idea when a reference goes out of scope, and has no control over when it gets disposed. Indeed, if memory never runs short, it may not be disposed until the process dies. GC gives us better memory allocation at the cost of horrible deallocation. Rant rant rant.
Care to explain how integer math has anything to do with garbage collection?
Re:What's with all of the bellyaching about speed?
on
Does C# Measure Up?
·
· Score: 1
I would add to that the point that slow code can be and is written in any language.
If you use containers and you do a lot of inserting and deleting, things will naturally be slow if you use arrays. If you do a lot of searching, linked lists will likely be slow. Since containers are much easier to come by in higher level languages (I don't believe there are any micro-processors that provide good container libraries:-), it is much easier to write fast code with a high level language when you use containers.
Memory copying is bad for performance. If you need fast code, avoid it. Allowing some other function to look at your data without changing it is NOT a good time to copy it. This is true no matter what language you write in.
Memory allocation is bad for performance. Avoid it if you need fast code by caching things or using the stack. True with any language.
Efficient coding practices will pay off much better in a low level language. Inefficient practices will kill you in ANY language.
12-year-old girls don't usually weight a whole lot. I bet she floats. And we all know what that means! BURNINATION!!!
I'm in the wrong biz. I bet the market for stakes is out of control right now. Which I invented. Indirectly. I declare that I am the owner of stakes everywhere and anyone using one automatically owes me $695.00 per burning!
Slashdot Mirror
Duh!!!
Rely on closed-source software and you risk this very problem. We all know that. Developers MOST OF ALL should INSIST on open-source for tools and libraries.
It's getting deep in here! This story just doesn't hold water and it won't scale (imagine a beo... nope, too corny even for me). By the time we see the tail end of this one, it'll smell pretty fishy. I think the data has been salted. Whoever believes this one is smoking a lot of sea weed, and personally I've had enough to make my head swim! I think this needs to be sent to a watery grave before the sharks catch the smell.
>> *shoots self for being so stupid*
Me first!!
>> Shaking the phone or something? That just looks dumb :^)
Yeah, but it might work pretty well for a vibrator! You know, the *other* device often found in a woman's purse.
Step 2: ???
Step 3: Profit!!!
Now that sounds logical. Everything that's ever happened in the history of the Earth has been the result of some combination of money and the female anatomy. Actually, money is one of them, so really, *everything* is the result of girls, and/or the lack thereof (think slashdot). It's true!
What's wrong with you? We all have cats!
>> I wonder what will be left from us?
Twinkies, of course.
Balmer would dance across the stage with all those explosives strapped on and detonate right as he passes the podium. DEVELOPERS DEVELOPERS DEVELOPERS DEVELOPERS DEVELOPERS *BOOM*
It wouldn't be safe. Funny as hell, but very unsafe.
I think we all know why MS is refusing to provide Hebrew support. Do you think they'd refuse if there was actual competition? Doubtful. Sounds a little like monopoly abuse to me. I would say Isreal is more justified in it's position than MS is in theirs.
Redundant?
Parent post is exactly correct. Copy protection can't work unless there is legislation making it illegal to circumvent, just like locked doors won't keep thieves out unless there is legislation to make it illegal to break and enter.
Whoever modded that down needs to be flogged with the clue stick.
Those would, I believe, fall under the antique firearms clause, so they are non-restricted. Anything made before 1898 that doesn't use 'fixed ammunition' is considered antique, as is any replica of said firearms (the blunderbuss is a replica?)
Maybe the guy is a ... get ready for it ... a mortician!
And you would have likely just wasted it. 4 ounces is quite a bit when you're talking about black powder (or a synthetic thereof), and that barrel is pretty short.
:-)
That said... I probably would try more too
As of about 10 years ago, federal law stated that a person could own a breach loader no more than .50 cal without a special license. HOWEVER, there were no restrictions that I could find on muzzle loaders. Want a cannon with an 8-foot bore? Go for it, just as long as the projectile and charge go in the same way they come out. Technically, that thing is 50-state legal.
I for one welcome our new, more rapidly booting overlords.
Maybe it's just a cash cow?
Want to get me excited about Linux?
1) Rock solid stable.
2) Open source.
3) Great networking support.
4) Solid web servers.
5) Solid SQL servers.
6) Solid remote access.
7) Lots of programming/scripting languages.
Hmmm...
He who has the gold makes the rules.
Murphy's number one rule:
Never mess with Mrs Murphy.
OK, this IS funny, I have to admit. Seeing something like that on the Compaq site is pretty funny.
But, this is NOT news for nerds, and it sure as hell is NOT STUFF THAT FUCKING MATTERS!
Now, just press any key to mod my ass into the dirt.
The stated point of this technology seems to be low power consumption and security (because of the very short range). Point number two is nulled by EM radiation, and point one can't be that hard to achieve with ordinary radio technology... can it?
FOR CIRCUMVENTION!
I've fallen in love with the memory allocation stuff that leads to garbage collection. I like using references to everything. Complex applications eventually end up needing some form of reference tracking to make the complexity manageable. However, I miss two things:
1) Destructors (proper ones).
2) Real-time object disposal.
I HATE background garbage collection! In many cases it works fine, but I hate it! Just give me real destructors that fire as soon as the last reference goes out of scope, and then dispose of that sucker in real time. Because of garbage collection, some classes have a Dispose() method, which must be called explicitly, but you don't have any way to know if you hold the last reference (if you keep track, you may as well be writing in c++), and if you call it early, you just effectively created a dangling pointer. An object has no idea whether it's referenced or not, has no idea when a reference goes out of scope, and has no control over when it gets disposed. Indeed, if memory never runs short, it may not be disposed until the process dies. GC gives us better memory allocation at the cost of horrible deallocation. Rant rant rant.
Care to explain how integer math has anything to do with garbage collection?
I would add to that the point that slow code can be and is written in any language.
:-), it is much easier to write fast code with a high level language when you use containers.
If you use containers and you do a lot of inserting and deleting, things will naturally be slow if you use arrays. If you do a lot of searching, linked lists will likely be slow. Since containers are much easier to come by in higher level languages (I don't believe there are any micro-processors that provide good container libraries
Memory copying is bad for performance. If you need fast code, avoid it. Allowing some other function to look at your data without changing it is NOT a good time to copy it. This is true no matter what language you write in.
Memory allocation is bad for performance. Avoid it if you need fast code by caching things or using the stack. True with any language.
Efficient coding practices will pay off much better in a low level language. Inefficient practices will kill you in ANY language.
12-year-old girls don't usually weight a whole lot. I bet she floats. And we all know what that means! BURNINATION!!!
I'm in the wrong biz. I bet the market for stakes is out of control right now. Which I invented. Indirectly. I declare that I am the owner of stakes everywhere and anyone using one automatically owes me $695.00 per burning!
-Darl