Well, if you're only making an agreement with each person for $20 or whatever there's no reason you should stop selling more if people will buy it. If you have someone renting a house from you, how many months should you charge them before you let them live there for free?
In this case, each copy of the good (the house) is "sold" to a different month rather than a different customer, but it's the same idea. (assuming you bought the house outright, no loans, and all you have to pay is property taxes)
If they stop paying, you kick them out, they no longer get to use your house. Same for these weird burgers, same for information goods. (at least as I see it) That's how capitalism works.
hehe, it's a very new feature, btw. I went and downloaded the nightly build as soon as I saw it (yesterday?)
Yeah, the configuration UI needs work... The option for links in new windows is under edit->preferences->advanced->scripts and windows, so at least you don't have to go into prefs.js or wherever.
And as for sites that "disable" right clicks, I immediately turn off javascript so I can open links in separate tabs. Wish these people would get a clue.
Now I don't know how much it actually costs to record a CD professionally, but this idea would also extend to software, and I have some idea there.
In that sense, it's more like making (including thinking up how to make it, but that's only part) the first burger costs $250,000. After that, each burger only costs $.10.
So what do you do? Charge the first customer $250,000 (good luck finding that sucker) or charge every customer $20 and hope that you'll sell 13,000 burgers?
Basically, there are two ways to compensate someone for their work. You can pay them in full, which costs a LOT but you then can do whatever you want with their work, including resell it. You own it. The alternative is to license it/pay royalties. In this case the cost is MUCH less, but you are very limited in what you can do with it. You can't have the best of both worlds.
Personally, I would suggest the best option would be for an artist to release one track, then allow people to bid small amounts until some large total amount builds up, then release the rest and take the money. Content is paid for, no royalties, no worries about piracy. If their price is never reached, nobody gets charged and nobody gets the rest of the music.
and as for the actual encoding, they dropped all the 1-byte inc/dec operations (there have always been 2-byte alternatives to those) to use as a set of prefixes for 64-bit registers, as well as for the extra registers.
Porting *ANYTHING* to x86-64 will be much easier than porting to ia64. Whether or not Microsoft has chosen to spend time for this is a matter of choosing their partners.
Apparently AMD talked with various "OS vendors" during the design of this architecture, so presumably Microsoft has even had some say in what would make it easier for them to use it.
It is a misconception that water is a requirement for life. Sure, life without water is practically impossible on earth.
Do we have any examples of life that does not require water? For all I know, it's more of a hasty assumption than a misconception.
Water is just *really* strange stuff, and I don't think there's any other substance remotely like it. ('course I'm not a chemist or whatever so there ya go)
The problem with analog is that it's impossible to transmit a signal and have the exact same thing appear on the other end.
While you could set that crypto key to some infinitely long number, there's no hope that you could produce an identical copy of it, so you need to either be fuzzy (essentially shortening the key) or never get your data back. Pi and sqrt 2 are trivial examples since they can be exactly represented even in digital very easily. (hint: I just did.) Restricting yourself to such numbers loses the benefit of their length.
Notice that another biological feature, DNA, is digital. DNA and neurons have different jobs. DNA needs to be able to produce a very large number of nearly identical copies. You can't do that in analog. Analog is better for some thing, digital is better for others.
It wouldn't have to be a button, just about any event on the page can be made to execute a javascript function
If that were the problem, it would be obvious you'd want to do it when the computation was complete. You're already running in the background, just execute one last thing when it's done.
The problem is that you need to contact the server and the standard way of doing that is to send a page request with form submit data, which usually needs the page to be reloaded at least.
Of course, there's probably sneaky ways around that, like doing a submit as a background image preload or something. (I don't know, can you directly manipulate sockets in javascript?)
Just use an encrypted filesystem and make sure you can trust the people you're emailing. Self-shredding documents will only work better if you're sending to someone you can't trust that doesn't know anything about computers.
If they're human, they have to get their genes from someplace. Personally, I think this is a great solution, once it becomes possible. You don't end up with 20 generations of people whose whole purpose in life is to raise the next generation. Of course you need to have a perfectly functioning machine for this...
Not everyone can use a trackball, at least without a lot of training. It requires a great degree of motor control in the thumb that some of us just don't have.
For me at least, using a trackball is like typing with my elbows.
The rate at which a mouse ball will get dirty is related to the environment, and the MOUSE PAD. I have an anchient Genius Mouse/Cutting Pad and it greatly reduces (or should I say "eliminates"? I never have to clean it out...) the amount of dirt that gets in to muck up the mouse. The sponge/cloth things are crap.
I'm curious as to the relative market share of the various operating systems they listed. Wouldn't it be expected that more popular systems would have a greater percentage of their security holes found? If only ten people used some os, you'd expect very few vulnerabilities to be found...
Then why not use "int", "short" etc... with an "assert( sizeof(int)) >= 4)" at the beginning of the program ? "int" is guaranted to be at least 32 bits, "short" at least 16 bits, and "char" at least 8 bits, so you are achieving exactly nothing with your typedefs, if they don't guarantee the exact size.
Int is guaranteed to be at least the size of short and at most the size of long. 16/32 bits are not guaranteed. (on an 8-bit machine, int could very well be 8 bits)
Checking the sizeof(int) is a good idea, but you'd have to make sure it's done at compile time. You are right, the int16/int32/etc typedefs aren't really appropriate in this case, but some others could be, something with a nasty name like int_atleast32. X6
"Otherwise you can just write a class that emulates the specific bit size you want."
Which is quite heavy.
For the programmer perhaps, but the actual code would be no worse than what you could get by rewriting stuff. Everything could be inline and optimized to an extra and every time you try to convert the value to a different type.
except you can't use your data with third-party libraries without doing conversions in all directions
...which also need to be written to be portable somehow. Chances are they'll use a data type you have natively available. In any case, the conversion could be as simple as assigning an int, so it shouldn't really matter.
Usually you don't acutally need exactly 16 bits, say. Usually you need *at least* 16 bits, in which case you just substitute a 32 bit int if you have to.
Otherwise you can just write a class that emulates the specific bit size you want. If you rely on the right overflow, use a larger data type that constantly ands out the high bits. If you're matching a file format, use several byte-length or other shorter data types. Do this in a class and the actual code doesn't need to change at all.
Just remember that not each generation have exactly the same number of people, on which your conclusion would be based.
I was implying a maximum reproduction rate, which reality would certainly fall short of. Thus each new generation would not be half of the preceding on, but LESS THAN half.
Quiz: The life expectancy (near 70) is about three times the length of generation (20+). So if the three existing generations have sizes x, 2x, and 4x, respectively, (so the total is 7x) and each couple has two children, what will be the total population one generation later? (answer: 10x)
Yeah, I missed the fact that generations are concurrent, but how does this work? Now: 4x+2x+1x=7x. One generation later: 2x+x+.5x=3.5x? Where does 10x come from? (and where does that "two children" come from?)
If you go by the language specification only, yes. (are there even any compilers that fully adhere to that?) Practically speaking, int is by convention 32 bits on modern desktop systems. If you plan to port to something else, there is a standard way to avoid problems:
typedef int int32;
typedef short int16;
etc.
If I were designing the language, I'd probably have such types built in, but oh well.
Slashdot Mirror
If you do waste that page view, the worst that'll happen is that near the end of the year you'll get ads on one more page.
If that's your one barrier, go ahead and install junkbuster for that one page and pay for the rest.
Well, if you're only making an agreement with each person for $20 or whatever there's no reason you should stop selling more if people will buy it. If you have someone renting a house from you, how many months should you charge them before you let them live there for free?
In this case, each copy of the good (the house) is "sold" to a different month rather than a different customer, but it's the same idea. (assuming you bought the house outright, no loans, and all you have to pay is property taxes)
If they stop paying, you kick them out, they no longer get to use your house. Same for these weird burgers, same for information goods. (at least as I see it) That's how capitalism works.
Yeah, I probly should've looked them up...
WRONG. The original spelling was alumium. (no "in")
t ml
This was then changed to aluminum, then aluminium. Then it changed back to aluminum in the US.
See http://www.world-aluminium.org/history/language.h
But none of this really matters unless you wanna go back to wulfram, plubnum, etc. (and originally, English had no "correct" spellings for anything.)
hehe, it's a very new feature, btw. I went and downloaded the nightly build as soon as I saw it (yesterday?)
Yeah, the configuration UI needs work... The option for links in new windows is under edit->preferences->advanced->scripts and windows, so at least you don't have to go into prefs.js or wherever.
It would be nice if browsers included an option for reversing that behavior though. . . .
Poof!! Your wish has been granted.
And as for sites that "disable" right clicks, I immediately turn off javascript so I can open links in separate tabs. Wish these people would get a clue.
Now I don't know how much it actually costs to record a CD professionally, but this idea would also extend to software, and I have some idea there.
In that sense, it's more like making (including thinking up how to make it, but that's only part) the first burger costs $250,000. After that, each burger only costs $.10.
So what do you do? Charge the first customer $250,000 (good luck finding that sucker) or charge every customer $20 and hope that you'll sell 13,000 burgers?
Basically, there are two ways to compensate someone for their work. You can pay them in full, which costs a LOT but you then can do whatever you want with their work, including resell it. You own it. The alternative is to license it/pay royalties. In this case the cost is MUCH less, but you are very limited in what you can do with it. You can't have the best of both worlds.
Personally, I would suggest the best option would be for an artist to release one track, then allow people to bid small amounts until some large total amount builds up, then release the rest and take the money. Content is paid for, no royalties, no worries about piracy. If their price is never reached, nobody gets charged and nobody gets the rest of the music.
and as for the actual encoding, they dropped all the 1-byte inc/dec operations (there have always been 2-byte alternatives to those) to use as a set of prefixes for 64-bit registers, as well as for the extra registers.
Porting *ANYTHING* to x86-64 will be much easier than porting to ia64. Whether or not Microsoft has chosen to spend time for this is a matter of choosing their partners.
Apparently AMD talked with various "OS vendors" during the design of this architecture, so presumably Microsoft has even had some say in what would make it easier for them to use it.
It is a misconception that water is a requirement for life. Sure, life without water is practically impossible on earth.
Do we have any examples of life that does not require water? For all I know, it's more of a hasty assumption than a misconception.
Water is just *really* strange stuff, and I don't think there's any other substance remotely like it. ('course I'm not a chemist or whatever so there ya go)
In otherwords, launder it a bit more as soon as you can ;)
The problem with analog is that it's impossible to transmit a signal and have the exact same thing appear on the other end.
While you could set that crypto key to some infinitely long number, there's no hope that you could produce an identical copy of it, so you need to either be fuzzy (essentially shortening the key) or never get your data back. Pi and sqrt 2 are trivial examples since they can be exactly represented even in digital very easily. (hint: I just did.) Restricting yourself to such numbers loses the benefit of their length.
Notice that another biological feature, DNA, is digital. DNA and neurons have different jobs. DNA needs to be able to produce a very large number of nearly identical copies. You can't do that in analog. Analog is better for some thing, digital is better for others.
It wouldn't have to be a button, just about any event on the page can be made to execute a javascript function
If that were the problem, it would be obvious you'd want to do it when the computation was complete. You're already running in the background, just execute one last thing when it's done.
The problem is that you need to contact the server and the standard way of doing that is to send a page request with form submit data, which usually needs the page to be reloaded at least.
Of course, there's probably sneaky ways around that, like doing a submit as a background image preload or something. (I don't know, can you directly manipulate sockets in javascript?)
Just use an encrypted filesystem and make sure you can trust the people you're emailing. Self-shredding documents will only work better if you're sending to someone you can't trust that doesn't know anything about computers.
So how does the mirror at the back end of the laser's resonance chamber hold up?
The humans on those planets will not be "us".
If they're human, they have to get their genes from someplace. Personally, I think this is a great solution, once it becomes possible. You don't end up with 20 generations of people whose whole purpose in life is to raise the next generation. Of course you need to have a perfectly functioning machine for this...
Not everyone can use a trackball, at least without a lot of training. It requires a great degree of motor control in the thumb that some of us just don't have.
For me at least, using a trackball is like typing with my elbows.
The rate at which a mouse ball will get dirty is related to the environment, and the MOUSE PAD. I have an anchient Genius Mouse/Cutting Pad and it greatly reduces (or should I say "eliminates"? I never have to clean it out...) the amount of dirt that gets in to muck up the mouse. The sponge/cloth things are crap.
I'm curious as to the relative market share of the various operating systems they listed. Wouldn't it be expected that more popular systems would have a greater percentage of their security holes found? If only ten people used some os, you'd expect very few vulnerabilities to be found...
Then why not use "int", "short" etc... with an "assert( sizeof(int)) >= 4)" at the beginning of the program ? "int" is guaranted to be at least 32 bits, "short" at least 16 bits, and "char" at least 8 bits, so you are achieving exactly nothing with your typedefs, if they don't guarantee the exact size.
Int is guaranteed to be at least the size of short and at most the size of long. 16/32 bits are not guaranteed. (on an 8-bit machine, int could very well be 8 bits)
Checking the sizeof(int) is a good idea, but you'd have to make sure it's done at compile time. You are right, the int16/int32/etc typedefs aren't really appropriate in this case, but some others could be, something with a nasty name like int_atleast32. X6
"Otherwise you can just write a class that emulates the specific bit size you want."
Which is quite heavy.
For the programmer perhaps, but the actual code would be no worse than what you could get by rewriting stuff. Everything could be inline and optimized to an extra and every time you try to convert the value to a different type.
except you can't use your data with third-party libraries without doing conversions in all directions
No.
Usually you don't acutally need exactly 16 bits, say. Usually you need *at least* 16 bits, in which case you just substitute a 32 bit int if you have to.
Otherwise you can just write a class that emulates the specific bit size you want. If you rely on the right overflow, use a larger data type that constantly ands out the high bits. If you're matching a file format, use several byte-length or other shorter data types. Do this in a class and the actual code doesn't need to change at all.
Just remember that not each generation have exactly the same number of people, on which your conclusion would be based.
I was implying a maximum reproduction rate, which reality would certainly fall short of. Thus each new generation would not be half of the preceding on, but LESS THAN half.
Quiz: The life expectancy (near 70) is about three times the length of generation (20+). So if the three existing generations have sizes x, 2x, and 4x, respectively, (so the total is 7x) and each couple has two children, what will be the total population one generation later? (answer: 10x)
Yeah, I missed the fact that generations are concurrent, but how does this work? Now: 4x+2x+1x=7x. One generation later: 2x+x+.5x=3.5x? Where does 10x come from? (and where does that "two children" come from?)
Matrix a, b, c;
a = b; a += c;
No temporary object.
Ugly as hell, might as well use a.add(c);
If you go by the language specification only, yes. (are there even any compilers that fully adhere to that?) Practically speaking, int is by convention 32 bits on modern desktop systems. If you plan to port to something else, there is a standard way to avoid problems:
typedef int int32;
typedef short int16;
etc.
If I were designing the language, I'd probably have such types built in, but oh well.
because you CAN'T implement high speed internet over powerlines.
As others have pointed out, the main problem is that the power lines are not designed to handle that much bandwidth and sheild it from interference.