They did? It seems you're right, but even when they get only 56kbit, and if you'r actually using that, then that $39.99 is blown away in 49 minutes of heavy surfing (or a 49 minutes tiny 56kbit realvideo stream for that matter).
fourty bucks for fifty minutes just doesn't sound even close to right yet, neither does eight and a half hours for a hundred bucks.
That's an Interesting theory, so I had to research it.
Actually, the french soldiers liked the neck tie ('cravate') because it was so much more convenient than the white collar they used to ornament their shirts with (the cravate was colored, hence easier to keep a clean appearance). And the french learned about the tie from the croats, explaining the name cravate.
Anyways, so the tie never was about function, but about appearance. It was an ornament more practical than its predecessor. So its a culture thing. But I'm still not sure about the hiding the buttons. Did the white collar hide the buttons too? I need closure;-)
ps: I read this on the Internet, so it has to be true...
Re:Suit and Tie do not make the programmer.
on
Suit Up Or Ship Out?
·
· Score: 2
But I hear the girls like to see men in suits. Maybe I'll reconsider...
Re:Suit and Tie do not make the programmer.
on
Suit Up Or Ship Out?
·
· Score: 2
But how about the tie and the correlation with it and oxygen flow to the head?
And that is just why often the best managers have been a techie themselves. They understand the work being done and the difficulties involved. They don't have to wonder, they know how to deal with real life instead of wondering why things are not perfect.
If the problems are a result of the project structure or content (such as... _testing_), thats where the manager can make changes. If the problems are a result of lack of experience or expertise in the people supposed to do the work, thats where he can make changes too. If the manager only wonders and bitches, it's time for a new manager.
The problem is that the protein isn't exactly telling us exactly what it is doing, it's keeping the results of its calculation secret.
Bluegene stores everything on a RAID array. Let's see a protein store its state on a RAID array at fixed time intervals so that researchers can look at the data and learn from it.
The problem is not getting the thing to fold, the problem is learning from it and doing useful things with it.
I was thinking exactly the same, a dollar per song is waay to pricey.
However, if they made the songs available in uncrippled mp3 (or ogg), and had a nice gui program that would allow you to quickly 'sample' music to see if its worth downloading and burning, and if it would include a 'people who downloaded this song also downloaded these songs'-type of search-helping features, and if it would send me weekly emails of new music I might like based on what I already downloaded, or based on bands that I selected, and if it would have _all_ music available (including all latest, oldest, and international titles), then I'd even pay a hefty flat rate of $80 a month for unlimited burning on a superlong three year contract. And I'd love it, even though I'd probably get a lot less than 80 songs per month (not enough time to listen to it anyway).
Anal retentive Mike? The/. introduction claims 'well over twenty times quieter'. It's not saying 'twenty times quieter', or even just 'over twenty times quieter', no, Jouster is so enthousiastic that he writes 'well over'. It's like calling a $890 TV having a price of well over a thousand dollars.
"You could've worked out that fraction instead"
Anyways, if you can't calculate, 25dB is 10^(25/20)=17.8 times quieter, much less than twenty, and definitely not well over twenty.
What is this site turning into, news for people who cant calculate?
Anyways, I suspect MS will include something that everybody who uses their sf.net clone will have to have their software licensed in a way that it may only be used to run on MS platforms...
Actually thinking more about it, I think his proposal won't gain much performance anyway. Lack of gp registers results in using the stack as an overflow for local data. Because of the rate of accesses on the stack, I'm pretty sure the local variable part of the always resides on L1 cache. That means stack push and pops are pretty fast already, because they go to+from the cache. Maybe it would help a little to have a special register bank that mirrors the 'top of the stack' so that it can be read and written at register speed instead of L1 cache speed. That would be a 'solution' that doesn't require any changes to the instruction set, no recompiling, etc, and probably gives the same performance gain.
I'm not so sure about that. He found a way to address more registers with minimal changes to the instruction set. That is only part of the problem. He doesn't analyze what is needed in the actual hardware, adding the registers and the read and write muxes to actually implement this functionality in gates. With register renaming that all these processors use, it's not so easily said how big this impact will be. Anyways, usually more registers, especially general purpose ones means more silicon area (routing and muxes around the register bits) plus increased critical path. Translation: a bigger chip with a lower clock speed.
The fact that microcontrollers have more gp registers doesn't mean anything, because they don't have to run at 2.8GHz, and often even need multiple processor cycles per clock, so there is a lot of room to work with. At the current speeds of X86 CPUs, the hardware contraints cannot be compared with those of a microcontroller.
Now that makes sense (you are definitely not a quitter!).
I do wish cell phone systems would give the other requirements a higher priority though (I guess I've had terrible service for too long). For users, those are the most important, because it translates into the percieved quality of the wireless service and phone, such as reliability, battery life, etc.
Of course total deregulation would definitely be worse than the current situation. Regulation is necessary, however I think that the politicians allocate the bandwidth with a main target of maximizing license fees (thus creating an artificial shortage, and the europeans are the worst in this respect) while reserving a disproportional large portion of the spectrum for non public uses. Regulation should be to protect the spectrum from abuse, but it's very much so a source of revenue which shifts the priorities of the regulators. Just look at how much innovation resulted from that unlicensed little band that was ruined my microwave interference anyway (2.4Ghz). Sure, wifi wan is spotty at best, but when and where it works, it's generating a lot of companies revenue, and its making a lot of users happy.
(yes you're right, noise is not a signal (by most definitions, because it isa common mistake...)).
"I don't know why I bother, but you seem sorely in need of education."
Please stop trying. You contradict yourself while trying:
"interference is any signal which might reduce reception"
With that definition, noise is interference.
"Noise, to any professional, is very different from interference"
Now you say that noise is not interference.
But noise and interference are the two different forms of signals that can reduce your reception: noise is a totally unpredictable signal and interference is a signal that has a pattern. Interference can be supressed, noise has to be worked around.
You can claim to have been an expert, but that doesn't mean what you're saying makes sense.
Spectral efficiency is not the holy grail. Please stop staring blindly at it. Spectral efficiency (Erlangs/Mhz/km^2) does not take into acount the call reliability, because a dropped call slot that can immediately be taken by another user results in the same spectral efficiency value as when the call was not dropped. But is very annoying for the people whose calls get dropped. Sure, the provider doesn't know, an airtime minute is an airtime minute, is cash, but the consumer cares if his calls get dropped.
Slashdot Mirror
They did? It seems you're right, but even when they get only 56kbit, and if you'r actually using that, then that $39.99 is blown away in 49 minutes of heavy surfing (or a 49 minutes tiny 56kbit realvideo stream for that matter).
fourty bucks for fifty minutes just doesn't sound even close to right yet, neither does eight and a half hours for a hundred bucks.
I'll stick with CSD for now.
After you find out how much they charge for a megabyte of GPRS bits, it doesn't matter anyway.
"and that will support Microsoft's .NET platform, among other things."
All right... PalmOS 5 it is... (no that is not a typo).
The certification verfies the security model used, not the quality of the implementation....
Oh man, combine that with animations and it becomes scary.
"The tie is there to hide the buttons."
;-)
That's an Interesting theory, so I had to research it.
Actually, the french soldiers liked the neck tie ('cravate') because it was so much more convenient than the white collar they used to ornament their shirts with (the cravate was colored, hence easier to keep a clean appearance). And the french learned about the tie from the croats, explaining the name cravate.
Anyways, so the tie never was about function, but about appearance. It was an ornament more practical than its predecessor. So its a culture thing. But I'm still not sure about the hiding the buttons. Did the white collar hide the buttons too? I need closure
ps: I read this on the Internet, so it has to be true...
But I hear the girls like to see men in suits. Maybe I'll reconsider...
But how about the tie and the correlation with it and oxygen flow to the head?
"Mostly managers wonder why techies..."
And that is just why often the best managers have been a techie themselves. They understand the work being done and the difficulties involved. They don't have to wonder, they know how to deal with real life instead of wondering why things are not perfect.
If the problems are a result of the project structure or content (such as... _testing_), thats where the manager can make changes. If the problems are a result of lack of experience or expertise in the people supposed to do the work, thats where he can make changes too. If the manager only wonders and bitches, it's time for a new manager.
The problem is that the protein isn't exactly telling us exactly what it is doing, it's keeping the results of its calculation secret.
Bluegene stores everything on a RAID array. Let's see a protein store its state on a RAID array at fixed time intervals so that researchers can look at the data and learn from it.
The problem is not getting the thing to fold, the problem is learning from it and doing useful things with it.
"There's no such thing as bad publicity."
Oh yeah? What about "Company X has cooked the books"?
Ask Enron or Worldcom if that wasn't bad publicity.
Where is the treshold for ease of cleaning it up that defines leaving a mark on a public wall as not being vandalism?
There is none. Gaffiti is graffiti, independent from ease or cost of the cleanup.
Doesn't New York have a three-strikes-you're-out kind of law?
I was thinking exactly the same, a dollar per song is waay to pricey.
However, if they made the songs available in uncrippled mp3 (or ogg), and had a nice gui program that would allow you to quickly 'sample' music to see if its worth downloading and burning, and if it would include a 'people who downloaded this song also downloaded these songs'-type of search-helping features, and if it would send me weekly emails of new music I might like based on what I already downloaded, or based on bands that I selected, and if it would have _all_ music available (including all latest, oldest, and international titles), then I'd even pay a hefty flat rate of $80 a month for unlimited burning on a superlong three year contract. And I'd love it, even though I'd probably get a lot less than 80 songs per month (not enough time to listen to it anyway).
It's all about value and convenience.
You forget that you're paying for the distribution (Internet connection), for the media (cdr's), and for the manufacturing (cd burner) too.
99 cents per song is a good start for early adopters, but way overpriced for the mass market.
Anal retentive Mike? The /. introduction claims 'well over twenty times quieter'. It's not saying 'twenty times quieter', or even just 'over twenty times quieter', no, Jouster is so enthousiastic that he writes 'well over'. It's like calling a $890 TV having a price of well over a thousand dollars.
"You could've worked out that fraction instead"
Anyways, if you can't calculate, 25dB is 10^(25/20)=17.8 times quieter, much less than twenty, and definitely not well over twenty.
What is this site turning into, news for people who cant calculate?
20 times sound level in decibels is 20*log(20)/log(10)=26.02dB.... 65-40dB is less than 26dB, so it's not well over twenty times quieter
IIS...
Or was it outsmart? By copycatting?
Anyways, I suspect MS will include something that everybody who uses their sf.net clone will have to have their software licensed in a way that it may only be used to run on MS platforms...
"(Score:5, Interesting)"
Funny...
Replying to myself...
Actually thinking more about it, I think his proposal won't gain much performance anyway. Lack of gp registers results in using the stack as an overflow for local data. Because of the rate of accesses on the stack, I'm pretty sure the local variable part of the always resides on L1 cache. That means stack push and pops are pretty fast already, because they go to+from the cache. Maybe it would help a little to have a special register bank that mirrors the 'top of the stack' so that it can be read and written at register speed instead of L1 cache speed. That would be a 'solution' that doesn't require any changes to the instruction set, no recompiling, etc, and probably gives the same performance gain.
"The scheme as proposed would work"
I'm not so sure about that. He found a way to address more registers with minimal changes to the instruction set. That is only part of the problem. He doesn't analyze what is needed in the actual hardware, adding the registers and the read and write muxes to actually implement this functionality in gates. With register renaming that all these processors use, it's not so easily said how big this impact will be. Anyways, usually more registers, especially general purpose ones means more silicon area (routing and muxes around the register bits) plus increased critical path. Translation: a bigger chip with a lower clock speed.
The fact that microcontrollers have more gp registers doesn't mean anything, because they don't have to run at 2.8GHz, and often even need multiple processor cycles per clock, so there is a lot of room to work with. At the current speeds of X86 CPUs, the hardware contraints cannot be compared with those of a microcontroller.
Now that makes sense (you are definitely not a quitter!).
I do wish cell phone systems would give the other requirements a higher priority though (I guess I've had terrible service for too long). For users, those are the most important, because it translates into the percieved quality of the wireless service and phone, such as reliability, battery life, etc.
Of course total deregulation would definitely be worse than the current situation. Regulation is necessary, however I think that the politicians allocate the bandwidth with a main target of maximizing license fees (thus creating an artificial shortage, and the europeans are the worst in this respect) while reserving a disproportional large portion of the spectrum for non public uses. Regulation should be to protect the spectrum from abuse, but it's very much so a source of revenue which shifts the priorities of the regulators. Just look at how much innovation resulted from that unlicensed little band that was ruined my microwave interference anyway (2.4Ghz). Sure, wifi wan is spotty at best, but when and where it works, it's generating a lot of companies revenue, and its making a lot of users happy.
(yes you're right, noise is not a signal (by most definitions, because it is a common mistake...)).
"I don't know why I bother, but you seem sorely in need of education."
Please stop trying. You contradict yourself while trying:
"interference is any signal which might reduce reception"
With that definition, noise is interference.
"Noise, to any professional, is very different from interference"
Now you say that noise is not interference.
But noise and interference are the two different forms of signals that can reduce your reception: noise is a totally unpredictable signal and interference is a signal that has a pattern. Interference can be supressed, noise has to be worked around.
You can claim to have been an expert, but that doesn't mean what you're saying makes sense.
Spectral efficiency is not the holy grail. Please stop staring blindly at it. Spectral efficiency (Erlangs/Mhz/km^2) does not take into acount the call reliability, because a dropped call slot that can immediately be taken by another user results in the same spectral efficiency value as when the call was not dropped. But is very annoying for the people whose calls get dropped. Sure, the provider doesn't know, an airtime minute is an airtime minute, is cash, but the consumer cares if his calls get dropped.
But he's using revolutionary 'security throught obscurity' technology!
Hmm, suddenly I have an idea for a patent too.