I wasn't being facetious BTW. Just before 9/11, relaxing the border with Mexico was high on Bush's agenda and NPR ran many stories on it. It obviously dropped out of sight immediately after 9/11 but the fact that's it being discussed again now might be a sign that maybe we're going to see a slight movement towards normality again.
This article on US immigration policy. Was it largely about how relaxing border controls with Mexico might allow more Middle Eastern terrorists into the country? That was the slant in the last story on this subject I listened to.:-)
The above comment needs to be modded up. The profit a company earns is the product of profit per item sold and the number sold. Increasing price increases profit and decreases sales. The goal is to find the price that maximizes the product of these numbers. But determining that maximum is a non-trivial task and depends on the relative rates of change of the sales and profit as a function of price. Without other information we cannot tell, a priori, whether 99c is above or below the optimum. There are some rules of thumb as the poster above suggests. But in practice the way to find out is to try varying your price either way and assessing the market's response. Eventually you may be able to build a model that makes reasonable predicitions but as Apple have been selling everything at a flat rate so far there is no data to even make a start.
I gave up listening to NPR in about 2001. Every so often I try again but it's just the same old thing. Wake me up when they run a story that's not about the Middle East - either about Saudi oil running out, or downtrodden Iranian women architects, or about education opportunities for Afghans, or about he psychology of suicide bombers, or Persian music, or Shakespeare performed in Iran, or Kuwaiti democarcy, or American troops in Iraq, or life under the threat of terror in Israel, or Arab media bias, or bias in American reporting in the Middle East, or about the risks taken by reporters in the Middle East, or discrimination against Arabs in the US, or life on an aircraft carrier in the Persian Gulf, or whatever. What about Tonga? I'm sure stuff happens there too and it needs to be reported.
That's asking companies to take great risks. They ramp up production on the promise of a monopoly of only one or two years and then risk having the patent rejected after investing heavily. Companies need to know beforehand whether or not their investment is going to be protected.
This is why you're taught in courses on physics how to estimate things like the weight of the pyramids or the capacitance of clouds (well we were). So you aren't just a slave to your calculator and can actually detect when a number is BS.
And here is the last part of the code. I'm putting some extra text here to work around the stupid filter that/. has which prevents us from talking about code even though this is a geek web site. Had to delete whitespace too. Anyway, you can just paste these segments of code together and compile with your favorite C++ compiler. It shouldn't take too long to complete on a reasonable CPU.
This code can be speeded up massively. I only wrote it to demonstrate how lame the original/. story is.
Pipe your favorite list of 10 letter words to the following C++ program. (A web search on 'scarlatina', 'galangalan' and 'lessnesses' will point you to the one used by the person the story is about.)
This is a brute force search. It's total crap. But it finds all the solutions in a reasinable time even for a dictionary expanded with non-words like nonesevent.
#include #include #include #include #include
using namespace std;
const int n = 11;
set prefixes;
bool solve(const vector &tableau,int row) {
if (row>=9)
{
cout "Solution:" endl;
for (int i = 0; in; ++i)
{
cout setw(2) i ". " tableau[i] endl;
}
}
The fact is, any half intelligent criminal doesn't get caught. Pick up any 'true crime' account and you'll find they often present the work of investigators as a great achievement but in just about every such story I have read criminals have either taken very few steps to cover their tracks or have become overconfident. This sounds like a typical overconfidence story though I haven't investigated the details thoroughly.
It may seem obvious that you should cover your tracks but actually many people get away with simply brazenly carrying out crimes in front of other people with no attempt to hide anything. Unfortunately this has a limited chance of success and repeated attempts to do this are more or less guaranteed to eventually meet catastrophic failure.
As is well known, police and investigators rarely solve crimes. Instead their presence, in conjunction with propaganda like TV crime series that portray unsolved crimes as the exception, serve to give the illusion that crime doesn't pay.
See my other comment about ctrl-alt-backspace. My problem is probably with the X server and ctrl-alt-backspace fails to work. (I've been using Linux since v. 0.99 so I know my way around...)
I think the problem is X rather than Linux itself (SUSE 9.1 and 9.3 on both 32 and 64 bit procs). The machine starts slowing down and eventually grinds to a halt. If I spot it early enough I can kill the X server (meaning I lose all of my apps) and occasionally I've managed to login from another machine to find the X server pegged out even though I'm not running intensive applcations. It may yet turn out to be nvidia again though it's completely different behavior I've seen for bad drivers under Windows - multicolored pixellated screens of death.
I've also had at least one spontaneous reboot and one or two sudden freezes (may be the same problem as above) under Linux in the last year. I guess these might just possibly be from power spikes.
you can always kill -9 it and it will go away
But I've had way more success getting the Task Manager to pop up on a machine with a runaway process than getting an xterm to pop up allowing me to type 'kill -9'. The Task Manager, and the process monitoring the keystrokes to bring it up, seem to run at pretty high priority.
And as we're just talking about crashes so I won't bitch about anything else.
I'm guessing you don't use MS products and are just talking out of your ass. I haven't seen a serious crash from a Windows box (either at home or for 4 years at work) since about 2001 apart from driver problems clearly caused by NVidia. I've had things like the desktop lock up on me but killing and restarting explorer.exe with the task manager seems to cure that. Meanwhile I now work at a Linux based company and have rebooted on a regular basis. Of course this isn't in line with/. groupthink so I'll be immediately modded into oblivion.
The set of states of a qubit is essentially given by a 2 dimensional complex vector space. The set of pure quantum states of a qubyte (8 qubits) is given by a 256 dimensional complex vector space. Despite being fairly familiar with quantum computing I've no idea what a computing matrix is and I don't know where the 65536 is coming from. I guess I could pay the money and read the Nature article. But right now this looks like science journalism at its worst - just random keywords thrown together.
Hmmm...maybe they're using quantum error correction so they're using 16 elements to represent 8 qubits reliably. But that doesn't fit the wording either.
People have been expecting quantum computing to take off in a big way but after a couple of decades of research we still have only machines with a handful of qubits. I claimed from day one that the difficulty of building a quantum computer with memory N goes up exponentially. Because of Moore's law type effects our ability to build computers goes up exponentially. The net result is that I expect the memory of quantum computers to go up linearly over time, not exponentially like classical computers. I think we're seeing this borne out over the years. So don't expect quantum algorithms to crack codes any time soon. For what it's worth, I think the claims of scalability in the article are BS - but we'll see...
A qubit does not have four states. As I have no idea what rabbit-hole you have pulled this notion from so I can't really figure out what your error is. A qubit is described by an element in a 2D complex vector space. The basis for this vector space has size two and the basis elements are often labelled |up> and |down>. So at a stretch you might say a qubit has two states. More accurately it has a countably infinite number of states.
Maybe you have seen states like |left> and |right> written down so you have guessed these are also states. But |left> and |right> are merely two linear combinations of |up> and |down> along with infinitely many other states.
Just for the record - that's not the title I submitted. I'm glad I got that off my chest. I couldn't have coped thinking that a complete stranger might have thought I was too lazy to write 'with'.
I wouldn't bother criticizing the body of a story on Slashdot, grammatical errors there are par for the course. I'm actually referring to the title. Even the telegraphic writing used in headlines is usually made up of grammatically correct phrases, if not entire sentences.
Slashdot Mirror
Is there any sign that Apple used some of the guts of Shake which has always supported 16 bit and shares some other features with Aperture?
I wasn't being facetious BTW. Just before 9/11, relaxing the border with Mexico was high on Bush's agenda and NPR ran many stories on it. It obviously dropped out of sight immediately after 9/11 but the fact that's it being discussed again now might be a sign that maybe we're going to see a slight movement towards normality again.
This article on US immigration policy. Was it largely about how relaxing border controls with Mexico might allow more Middle Eastern terrorists into the country? That was the slant in the last story on this subject I listened to. :-)
The above comment needs to be modded up. The profit a company earns is the product of profit per item sold and the number sold. Increasing price increases profit and decreases sales. The goal is to find the price that maximizes the product of these numbers. But determining that maximum is a non-trivial task and depends on the relative rates of change of the sales and profit as a function of price. Without other information we cannot tell, a priori, whether 99c is above or below the optimum. There are some rules of thumb as the poster above suggests. But in practice the way to find out is to try varying your price either way and assessing the market's response. Eventually you may be able to build a model that makes reasonable predicitions but as Apple have been selling everything at a flat rate so far there is no data to even make a start.
I gave up listening to NPR in about 2001. Every so often I try again but it's just the same old thing. Wake me up when they run a story that's not about the Middle East - either about Saudi oil running out, or downtrodden Iranian women architects, or about education opportunities for Afghans, or about he psychology of suicide bombers, or Persian music, or Shakespeare performed in Iran, or Kuwaiti democarcy, or American troops in Iraq, or life under the threat of terror in Israel, or Arab media bias, or bias in American reporting in the Middle East, or about the risks taken by reporters in the Middle East, or discrimination against Arabs in the US, or life on an aircraft carrier in the Persian Gulf, or whatever. What about Tonga? I'm sure stuff happens there too and it needs to be reported.
I'm not going to worry about the horse and cart and Filofaxes either.
That's asking companies to take great risks. They ramp up production on the promise of a monopoly of only one or two years and then risk having the patent rejected after investing heavily. Companies need to know beforehand whether or not their investment is going to be protected.
This is why you're taught in courses on physics how to estimate things like the weight of the pyramids or the capacitance of clouds (well we were). So you aren't just a slave to your calculator and can actually detect when a number is BS.
And here is the last part of the code. I'm putting some extra text here to work around the stupid filter that /. has which prevents us from talking about code even though this is a geek web site. Had to delete whitespace too. Anyway, you can just paste these segments of code together and compile with your favorite C++ compiler. It shouldn't take too long to complete on a reasonable CPU.
/. story is.
This code can be speeded up massively. I only wrote it to demonstrate how lame the original
vector new_tableau = tableau;
new_tableau[row] = temp;
if (row!=len-1)
{
new_tableau[len-1] += l;
}
if (len>row+1)
{
solve(new_tableau,row+1);
} else
{
solve(new_tableau,0);
}
}
}
}
Here's some more of the code (/.'s lameness filter is lame):
for (char l = 'a'; l='z'; ++l)
{
string temp = tableau[row]+l;
int len = temp.length();
string temp2 = tableau[len-1]+l;
if (prefixes.find(temp)!=prefixes.end() && prefixes.find(temp2)!=prefixes.end())
{
Pipe your favorite list of 10 letter words to the following C++ program. (A web search on 'scarlatina', 'galangalan' and 'lessnesses' will point you to the one used by the person the story is about.)
This is a brute force search. It's total crap. But it finds all the solutions in a reasinable time even for a dictionary expanded with non-words like nonesevent.
#include
#include
#include
#include
#include
using namespace std;
const int n = 11;
set prefixes;
bool solve(const vector &tableau,int row)
{
if (row>=9)
{
cout "Solution:" endl;
for (int i = 0; in; ++i)
{
cout setw(2) i ". " tableau[i] endl;
}
}
Remainder in next post...
It may seem obvious that you should cover your tracks but actually many people get away with simply brazenly carrying out crimes in front of other people with no attempt to hide anything. Unfortunately this has a limited chance of success and repeated attempts to do this are more or less guaranteed to eventually meet catastrophic failure.
As is well known, police and investigators rarely solve crimes. Instead their presence, in conjunction with propaganda like TV crime series that portray unsolved crimes as the exception, serve to give the illusion that crime doesn't pay.
See my other comment about ctrl-alt-backspace. My problem is probably with the X server and ctrl-alt-backspace fails to work. (I've been using Linux since v. 0.99 so I know my way around...)
I've also had at least one spontaneous reboot and one or two sudden freezes (may be the same problem as above) under Linux in the last year. I guess these might just possibly be from power spikes.
But I've had way more success getting the Task Manager to pop up on a machine with a runaway process than getting an xterm to pop up allowing me to type 'kill -9'. The Task Manager, and the process monitoring the keystrokes to bring it up, seem to run at pretty high priority.And as we're just talking about crashes so I won't bitch about anything else.
I'm guessing you don't use MS products and are just talking out of your ass. I haven't seen a serious crash from a Windows box (either at home or for 4 years at work) since about 2001 apart from driver problems clearly caused by NVidia. I've had things like the desktop lock up on me but killing and restarting explorer.exe with the task manager seems to cure that. Meanwhile I now work at a Linux based company and have rebooted on a regular basis. Of course this isn't in line with /. groupthink so I'll be immediately modded into oblivion.
The set of states of a qubit is essentially given by a 2 dimensional complex vector space. The set of pure quantum states of a qubyte (8 qubits) is given by a 256 dimensional complex vector space. Despite being fairly familiar with quantum computing I've no idea what a computing matrix is and I don't know where the 65536 is coming from. I guess I could pay the money and read the Nature article. But right now this looks like science journalism at its worst - just random keywords thrown together.
Hmmm...maybe they're using quantum error correction so they're using 16 elements to represent 8 qubits reliably. But that doesn't fit the wording either.
You guys asleep? I'm surprised nobody caught my typo.
People have been expecting quantum computing to take off in a big way but after a couple of decades of research we still have only machines with a handful of qubits. I claimed from day one that the difficulty of building a quantum computer with memory N goes up exponentially. Because of Moore's law type effects our ability to build computers goes up exponentially. The net result is that I expect the memory of quantum computers to go up linearly over time, not exponentially like classical computers. I think we're seeing this borne out over the years. So don't expect quantum algorithms to crack codes any time soon. For what it's worth, I think the claims of scalability in the article are BS - but we'll see...
A qubit does not have four states. As I have no idea what rabbit-hole you have pulled this notion from so I can't really figure out what your error is. A qubit is described by an element in a 2D complex vector space. The basis for this vector space has size two and the basis elements are often labelled |up> and |down>. So at a stretch you might say a qubit has two states. More accurately it has a countably infinite number of states. Maybe you have seen states like |left> and |right> written down so you have guessed these are also states. But |left> and |right> are merely two linear combinations of |up> and |down> along with infinitely many other states.
Just for the record - that's not the title I submitted. I'm glad I got that off my chest. I couldn't have coped thinking that a complete stranger might have thought I was too lazy to write 'with'.
I wouldn't bother criticizing the body of a story on Slashdot, grammatical errors there are par for the course. I'm actually referring to the title. Even the telegraphic writing used in headlines is usually made up of grammatically correct phrases, if not entire sentences.
...a mass noun. 'Vast' doesn't really work with mass nouns.
I'm sure you can aim higher than merely satisfying your needs.
You're winning! I was unaware that there were USB chargers for the DS and GBA Micro. I just need a powered USB hub with lots of ports.
Thanks for that Radio Baton link! Doesn't look too tricky to build, especially now that I have acquired an oscilloscope.