> Note the HEAVY editing; 1) The white sleeve is to the left instead of right as in the original picture. > 2) a brick wall has been added 3) a caption has been added "Dump Your Pen Friend".
There isn't heavy editing. 1) The image was reversed and cropped to show just the girl. 2) The brick wall was already present behind the girl. 3) Yes, a caption was added.
I don't think it counts as "heavy editing" if I can do it in 2 minutes with almost any basic image editing program.
Personally, I think it's a good business choice for AMD. It provides a number of benefits. 1> It generates some good press (At first I thought it was currently available from reading the article. It isn't. It's just being added to the roadmap for next year.) 2> They can get some utility out of the down-binned processors (ones that aren't able to get all 4 cores running at the specified speed, etc. for the quad-core, or that have a hard failure in one of the 4 cores) 3> They can use the product to hit price/performance points that they wouldn't hit otherwise (well, not without hurting their profits on quad-core) Possibly that may mean they even wind up with PhenomX3 parts that could have been quad-core, but just weren't tested on all 4 cores, as a test-time saving measure. Ex. Only test 3 cores, and if they're good, ship the part, cutting test time (and therefore production costs) by some amount. I believe Intel used this methodology on a number of Celeron parts - they had a huge volume of sales for Celerons because of price. I bet that for at least one of the versions of Celerons that was a downbinned Pentium at some point they said "Hey, we're only going to test these N wafers to see if they're good enough to be Celerons, so we can get more Celeron parts out the door faster"
> designed that way from the ground up So what's the codename for the chip then? Not the marketting name. Everyone has heard the codename of "Barcelona". And that's a quad-core chip.
What team of engineers worked on it / are working on it? If you say it's the Barcelona team, I'd have to strongly disagree that it was a "ground up" design for 3 cores.
>DEC was bought by Compaq way back when (1997?). Compaq was bought by HP more recently. AMD was not involved with either of those takeovers. >So how did AMD get the DEC Alpha engineers? As far as I know, the DEC Alpha guys are still within HP. Did I miss something?
How many people were working on Alpha EV7 are still working at Intel would be a valid question -one you couldn't easily answer. Probably there are even some engineers that worked on EV7 that changed jobs to work for Intel outside of Intel acquiring the teams.
Also - IIRC, Intel acquired some engineers from DEC (mostly process folks I think) back around when Compaq acquired them.
I'm sure there are people who work for AMD now that had worked on an Alpha project. Just like I am sure there are people who work for Intel that worked on an Opteron project. People switch jobs, and there's only so many companies that do microprocessor design. (or even more broadly, only so many semiconductor design companies)
> I'm hoping the NFL accepts this tech. It'd be nice to get around local TV blackouts without having to rig ticket sales.
What local TV blackouts? We haven't had one here in WI. Maybe it's something to do with there being a waitlist for season tickets of 57000+ people. (An average of 30+ years waiting for tickets)
If you enter $110 it tells you you're 98.28%. If you enter $100 it stays with whatever the previous % was - whether it was previously 98% ($110) or 0.6% ($100K)
Re:One Thing I Never Understood...
on
Itanium Problems
·
· Score: 2, Informative
It runs legacy... code, but under a sort of emulation that cripples performance.
It is no more emulation than Athlon, Pentium Pro, Pentium 4, or any of the other current x86 CPUs are. The performance of legacy code on Itanium is certainly less than stellar. But it isn't emulation like Transmeta's methodology or DEC's FX!32.
It is a microcode based method very similar to any current x86 CPU. (just much lower performance)
This is something we've seen before in Intel's Pentium Pro. Never heard of?
*snicker* You really think people haven't heard of Pentium Pro? Or that *I* haven't? It's not like it's the 486SL. It was a fairly successful product. Quite a few of those chips were shipped. And it became the basis for many later Intel CPUs.
it's performance sucked for legacy code. Intel is doing the same thing again, and I doubt if they will succeed this time
It isn't the same thing. It's a significantly different situation. Intel isn't killing off Pentium 4 line of CPUs in favor of Itanium CPUs. And hasn't indicated any willingness to consider that. They also haven't shown an improvement in legacy code on Itanium systems.
This is a different situation with different tactics being used by Intel.
Re:One Thing I Never Understood...
on
Itanium Problems
·
· Score: 1
But why not have it both ways?
Intel's Itanium *does* have it "both ways". You can be in "16-bit stone age legacy mode" or switch to 64-bit mode. A large part of the criticism of Intel's design is that the "stone age legacy mode" sucks in performance. Opteron (at least in theory) won't suck for performance for 16-bit/32-bit compatibility. But their drawback is not having a "clean" 64-bit design.
The 64-bits code could then be clean like Intel proposes, and we'd all be happy.
Considering that Intel has what you suggest in Itanium, it seems that it won't be that everyone is happy.
I know you can work on a farm starting at age 11 or 12. (At least in some states - never found out if it was state or federal laws that applied to me and >100 of my classmates working for a local farming company.)
There may be other exceptions as well that you can exploit. You seem intelligent enough to do the research to find out, so do it.
In any case, I believe that the current system is Evil and Wrong. We should fix it instead fo forcing kids to be liars.
I wouldn't say it was "evil".
IMO it is a problem that the point where one is considered an "adult" is determined by age.
But I haven't seen a proposal of a much better methodology. We could have a "test" that you have to take - but those could discriminate against many groups. And do people who always fail automatically become one when they are 18? 21? never? How do you even construct a good test?
And with our current political system, it's obvious that below 18 has practically NO political clout. Even 18-21 has very little political clout.
Add to that the fact that there are plenty of 18 year olds who probably shouldn't be recognized as an adult, and it's a ugly political problem.
Given all this, a teen-ager is IMO getting screwed by the system that's trying to "protect" him, and has little choice but to accept it and learn to handle it as one of the many disappointments of life. If he can change it for the better, he has my full support. But I suspect he won't be able to, and all I can give him is my sympathy.
So, having proved the concept, I am going to go back to my slightly less offensive bootleg DSL connection until I can find out who owns that oak tree and make my new installation legit.
I was going to suggest getting a plat book from the Sonoma county extension office. But I called them, and they don't do plat books... (Maybe plat books are just a midwestern thing. I'm used to most every farmer having a plat book that shows who owns which acreage.)
So it looks like for Cringely to find out who owns that part of Bennett Mountain he's going to have to go to the Recorder or Assessor's office and find it on a map there.
"Must an employer pay a non-exempt employee for time spent on-call?"
"It depends"
"...
to determine whether an employee's on-call time is compensable under FLSA:
(1) the terms of the employment agreement, if any;
(2) the physical restrictions placed on an employee while on call;
(3) the response time;
(4) the percentage of calls expected to be returned by the on-call employee;
(5) frequency of actual calls during on-call periods;
(6) actual uses of the on-call time by the employee; and
(7) the disciplinary action, if any, taken by the employer against employees who fail to answer calls. "
And consult a lawyer. (And you'll probably still not have a crystal clear answer unless there is case law identical to your situation.)
BTW: My father works as a mechanic/engineer on critical machines, and they also have pager-duty that rotates, so it isn't just IT/IS people. His company only rotates the pager among salaried (exempt) individuals now because the company didn't want to pay overtime for the pager.
Their pager system limited the person to a fairly small geographical area (less than 1 hour drive), and the employee was to respond immediately, and they were the only person on-call at a time.
As a former employee, I know that they often/usually use Unix servers for their database back-end.
I don't know much about their web-based applications, as I was an employee with them before Web-based things were really done anywhere...
As I've not been there for a number of years, I can't say much about their pricing, other than I do know that non-profit medical organizations have implemented their systems. (And the non-profit that I know of is definitely cost sensitive.)
Personally, I see little problem with using Windows platforms for the client ends in the exam rooms...
My thought is to look at the various options available and just choose the best one for the application. If it's on top of BSD or Linux, great. If it is partially using Windows, so what? As long as the patients get the best care, I think that is the most important thing.
Feel like taking some money out of Microsoft's accounts and giving it to the Post Office and some printers?
Sign up for the Freedom to Innovate Network!
Give them a spamable email address.
And a name and address you don't mind getting junk paper mail sent to.
For those who think Microsoft is the Evil Empire, you get to do 4 things: 1> take money away from Microsoft (at pennies a month rates, but with enough people it adds up.) 2> You help Microsoft support the US Post office (part of those pennies/month.) 3> You get to see what ridiculous claims Microsoft is making. 4> Potentially kill the current form of the FIN campaign by reducing it's effectiveness... (If 1/2 their mailings go to non-Microsoft-supporters, their mailings become less useful.)
The way you're implying encryption works is just changing the way it's represented. In that way, I could be encrypting a message just by writing it down
Changing the way something is represented is the definition of encryption...
If you write it down in egyptian hyroglyphs or apache, noone would consider it not to be encryption. Possibly poor encryption if it was easily translated back, but encryption nonetheless.
What encrypting it does is distribute that entropy over as much space as possible, and turn your large secret (the plaintext) into a small secret (the secret key).
Not necessarily so.
keys can be extremely large. Even larger than the plaintext. Or just as large. (Learn about one-time-pads to see an example.
Encryption says *nothing* about entropy.
Good encryption codes take into account entropy, as statistical methods can be used against encryption codes that do not take that into account.
I'd suggest reading "Applied Cryptography". It's an excellent background on what cryptography is and explains some of the various attacks against encryption methods and uses.
a message like "JUNE6_INVASION: NORMANDY" probably has different enough statistics from the rest of the DNA around it that it might stand out
Why would the text "probably" be statistically different enough?
And I'd say that since the text had to be transformed from plaintext to nucleotides, that alone qualifies as encryption.
Encryption: "the activity of converting from plain text into code"
but she's implying that straight plaintext is also unfindable there, and it's not, any more than hiding it in the low order bits of a picture is.
Well, it can't be straight plaintext, it has to be encoded somehow.
And since she is apparantly choosing the DNA to surround it, it is easy enough to make the background be similar to the text to be hidden and the keys.
Also, since we're dealing with DNA here, it becomes difficult for someone to do any statistical analysis on it. With any significant amount of DNA it would be rather difficult to sequence it all.
"These crimes were the high-tech equivalent of physically breaking into a business and stealing valuable documents from a locked file cabinet..."
People need to learn that the two simply don't equate. Stealing means that a victim does no longer have what was once theirs. Breaking into something means physically harming a device intended to prevent entry for the purpose of extracting data.
They aren't that far off.
Ok, how's this:
"These crimes were the high-tech equivalent of breaking into a business and stealing valuable secret documents from a locked file cabinet, photocopying them, and returning them to the same cabinet."
Also, Breaking into does not necessarily mean physical harm to a device. If I watch someone open a safe, then without their permission/knowledge I later go and open that safe using the combination I just saw, IMO it is common usage to refer to my opening it as "breaking into" the safe, even though no physical harm was done.
Slashdot Mirror
> Note the HEAVY editing; 1) The white sleeve is to the left instead of right as in the original picture.
> 2) a brick wall has been added 3) a caption has been added "Dump Your Pen Friend".
There isn't heavy editing.
1) The image was reversed and cropped to show just the girl.
2) The brick wall was already present behind the girl.
3) Yes, a caption was added.
I don't think it counts as "heavy editing" if I can do it in 2 minutes with almost any basic image editing program.
> Despite both the summary and the article, it's a real 3-core chip, designed that way from the ground up,
And you know it is because...????
It isn't just hothardware that is speculating it's a variant of Barcelonas.
http://www.news.com/8301-13579_3-9780049-37.html
Personally, I think it's a good business choice for AMD.
It provides a number of benefits.
1> It generates some good press (At first I thought it was currently available from reading the article. It isn't. It's just being added to the roadmap for next year.)
2> They can get some utility out of the down-binned processors (ones that aren't able to get all 4 cores running at the specified speed, etc. for the quad-core, or that have a hard failure in one of the 4 cores)
3> They can use the product to hit price/performance points that they wouldn't hit otherwise (well, not without hurting their profits on quad-core) Possibly that may mean they even wind up with PhenomX3 parts that could have been quad-core, but just weren't tested on all 4 cores, as a test-time saving measure. Ex. Only test 3 cores, and if they're good, ship the part, cutting test time (and therefore production costs) by some amount. I believe Intel used this methodology on a number of Celeron parts - they had a huge volume of sales for Celerons because of price. I bet that for at least one of the versions of Celerons that was a downbinned Pentium at some point they said "Hey, we're only going to test these N wafers to see if they're good enough to be Celerons, so we can get more Celeron parts out the door faster"
> designed that way from the ground up
So what's the codename for the chip then? Not the marketting name.
Everyone has heard the codename of "Barcelona". And that's a quad-core chip.
What team of engineers worked on it / are working on it?
If you say it's the Barcelona team, I'd have to strongly disagree that it was a "ground up" design for 3 cores.
>DEC was bought by Compaq way back when (1997?). Compaq was bought by HP more recently. AMD was not involved with either of those takeovers.
m s/2100-1006_3-1023146.html
>So how did AMD get the DEC Alpha engineers? As far as I know, the DEC Alpha guys are still within HP. Did I miss something?
Alpha team was spun off to Intel.
http://news.com.com/Intel+gets+more+key+Alpha+alu
http://www.theinquirer.net/?article=20024
How many people were working on Alpha EV7 are still working at Intel would be a valid question -one you couldn't easily answer.
Probably there are even some engineers that worked on EV7 that changed jobs to work for Intel outside of Intel acquiring the teams.
Also - IIRC, Intel acquired some engineers from DEC (mostly process folks I think) back around when Compaq acquired them.
I'm sure there are people who work for AMD now that had worked on an Alpha project.
Just like I am sure there are people who work for Intel that worked on an Opteron project.
People switch jobs, and there's only so many companies that do microprocessor design. (or even more broadly, only so many semiconductor design companies)
> I'm hoping the NFL accepts this tech. It'd be nice to get around local TV blackouts without having to rig ticket sales.
What local TV blackouts?
We haven't had one here in WI.
Maybe it's something to do with there being a waitlist for season tickets of 57000+ people. (An average of 30+ years waiting for tickets)
For: http://www.globalrichlist.com/
It keeps the previous % for anything entered less than $100.
If you enter $110 it tells you you're 98.28%.
If you enter $100 it stays with whatever the previous % was - whether it was previously 98% ($110) or 0.6% ($100K)
An appetizier at outback steakhouse, a restaurant with an annoying "australian" theme and annoying radio ads.
recipe to make a similiar one yourself
It runs legacy ... code, but under a sort of emulation that cripples performance.
It is no more emulation than Athlon, Pentium Pro, Pentium 4, or any of the other current x86 CPUs are.
The performance of legacy code on Itanium is certainly less than stellar. But it isn't emulation like Transmeta's methodology or DEC's FX!32.
It is a microcode based method very similar to any current x86 CPU. (just much lower performance)
This is something we've seen before in Intel's Pentium Pro. Never heard of?
*snicker*
You really think people haven't heard of Pentium Pro?
Or that *I* haven't?
It's not like it's the 486SL.
It was a fairly successful product. Quite a few of those chips were shipped.
And it became the basis for many later Intel CPUs.
it's performance sucked for legacy code. Intel is doing the same thing again, and I doubt if they will succeed this time
It isn't the same thing.
It's a significantly different situation.
Intel isn't killing off Pentium 4 line of CPUs in favor of Itanium CPUs. And hasn't indicated any willingness to consider that.
They also haven't shown an improvement in legacy code on Itanium systems.
This is a different situation with different tactics being used by Intel.
But why not have it both ways?
Intel's Itanium *does* have it "both ways".
You can be in "16-bit stone age legacy mode" or switch to 64-bit mode.
A large part of the criticism of Intel's design is that the "stone age legacy mode" sucks in performance.
Opteron (at least in theory) won't suck for performance for 16-bit/32-bit compatibility.
But their drawback is not having a "clean" 64-bit design.
The 64-bits code could then be clean like Intel proposes, and we'd all be happy.
Considering that Intel has what you suggest in Itanium, it seems that it won't be that everyone is happy.
Before fifteen ... you simply can't work.
Not quite accurate.
I know you can work on a farm starting at age 11 or 12. (At least in some states - never found out if it was state or federal laws that applied to me and >100 of my classmates working for a local farming company.)
There may be other exceptions as well that you can exploit.
You seem intelligent enough to do the research to find out, so do it.
In any case, I believe that the current system is Evil and Wrong. We should fix it instead fo forcing kids to be liars.
I wouldn't say it was "evil".
IMO it is a problem that the point where one is considered an "adult" is determined by age.
But I haven't seen a proposal of a much better methodology.
We could have a "test" that you have to take - but those could discriminate against many groups.
And do people who always fail automatically become one when they are 18? 21? never?
How do you even construct a good test?
And with our current political system, it's obvious that below 18 has practically NO political clout.
Even 18-21 has very little political clout.
Add to that the fact that there are plenty of 18 year olds who probably shouldn't be recognized as an adult, and it's a ugly political problem.
Given all this, a teen-ager is IMO getting screwed by the system that's trying to "protect" him, and has little choice but to accept it and learn to handle it as one of the many disappointments of life. If he can change it for the better, he has my full support.
But I suspect he won't be able to, and all I can give him is my sympathy.
So, having proved the concept, I am going to go back to my slightly less offensive bootleg DSL connection until I can find out who owns that oak tree and make my new installation legit.
I was going to suggest getting a plat book from the Sonoma county extension office. But I called them, and they don't do plat books... (Maybe plat books are just a midwestern thing. I'm used to most every farmer having a plat book that shows who owns which acreage.)
So it looks like for Cringely to find out who owns that part of Bennett Mountain he's going to have to go to the Recorder or Assessor's office and find it on a map there.
that would be a warehouse.
Wherehouse == music store chain.
http://www.wherehouse.com for their (almost) defunct website
And more importantly near the telco CO for DSL, and/or in a neighborhood with cablemodem. :)
My suggestions:
http://realestate.yahoo.com/
dslreports.com
Get Microsoft and AOL to put PGP in their email agents. (and maybe Eudora - although they seem to be in decline)
Once the major players have 1 standard methodology, everyone else will start talking to that methodology.
Unfortunately noone can agree to 1 standard method, and there isn't enough business demand for it to make it a high priority feature.
So everyone suffers...
"Must an employer pay a non-exempt employee for time spent on-call?"
m l
"It depends"
"...
to determine whether an employee's on-call time is compensable under FLSA:
(1) the terms of the employment agreement, if any;
(2) the physical restrictions placed on an employee while on call;
(3) the response time;
(4) the percentage of calls expected to be returned by the on-call employee;
(5) frequency of actual calls during on-call periods;
(6) actual uses of the on-call time by the employee; and
(7) the disciplinary action, if any, taken by the employer against employees who fail to answer calls. "
For more on this see:
http://www.iog.unc.edu/programs/hresources/q02.ht
And consult a lawyer. (And you'll probably still not have a crystal clear answer unless there is case law identical to your situation.)
BTW: My father works as a mechanic/engineer on critical machines, and they also have pager-duty that rotates, so it isn't just IT/IS people. His company only rotates the pager among salaried (exempt) individuals now because the company didn't want to pay overtime for the pager.
Their pager system limited the person to a fairly small geographical area (less than 1 hour drive), and the employee was to respond immediately, and they were the only person on-call at a time.
my @output =
map { $_->[0] }
sort { $a->[1] cmp $b->[1] }
map { [$_, expensive_func($_)] }
@input;
The question is: Is this code that is "really bad"? Or "code that shows elegant and masterful design"?
Or is it both?
My vote is for both... Elegant, masterful, excellent and beautiful, yet can be really bad in certain uses.
http://www.epicsystems.com/
As a former employee, I know that they often/usually use Unix servers for their database back-end.
I don't know much about their web-based applications, as I was an employee with them before Web-based things were really done anywhere...
As I've not been there for a number of years, I can't say much about their pricing, other than I do know that non-profit medical organizations have implemented their systems. (And the non-profit that I know of is definitely cost sensitive.)
Personally, I see little problem with using Windows platforms for the client ends in the exam rooms...
My thought is to look at the various options available and just choose the best one for the application. If it's on top of BSD or Linux, great. If it is partially using Windows, so what? As long as the patients get the best care, I think that is the most important thing.
Don't like Microsoft?
;)
Dislike this FIN astro-turf campaign?
Feel like taking some money out of Microsoft's accounts and giving it to the Post Office and some printers?
Sign up for the Freedom to Innovate Network!
Give them a spamable email address.
And a name and address you don't mind getting junk paper mail sent to.
For those who think Microsoft is the Evil Empire, you get to do 4 things:
1> take money away from Microsoft (at pennies a month rates, but with enough people it adds up.)
2> You help Microsoft support the US Post office (part of those pennies/month.)
3> You get to see what ridiculous claims Microsoft is making.
4> Potentially kill the current form of the FIN campaign by reducing it's effectiveness... (If 1/2 their mailings go to non-Microsoft-supporters, their mailings become less useful.)
Some might think this is unethical...
But when has that bothered Microsoft?
"You agree that we may, in our sole discretion, delete or transfer your domain name at any time."
In short: We'll do whatever we want, and you're screwed.
Changing the way something is represented is the definition of encryption...
If you write it down in egyptian hyroglyphs or apache, noone would consider it not to be encryption. Possibly poor encryption if it was easily translated back, but encryption nonetheless.
What encrypting it does is distribute that entropy over as much space as possible, and turn your large secret (the plaintext) into a small secret (the secret key).
Not necessarily so.
keys can be extremely large. Even larger than the plaintext. Or just as large. (Learn about one-time-pads to see an example.
Encryption says *nothing* about entropy.
Good encryption codes take into account entropy, as statistical methods can be used against encryption codes that do not take that into account.
I'd suggest reading "Applied Cryptography". It's an excellent background on what cryptography is and explains some of the various attacks against encryption methods and uses.
Why would the text "probably" be statistically different enough?
And I'd say that since the text had to be transformed from plaintext to nucleotides, that alone qualifies as encryption.
Encryption: "the activity of converting from plain text into code"
but she's implying that straight plaintext is also unfindable there, and it's not, any more than hiding it in the low order bits of a picture is.
Well, it can't be straight plaintext, it has to be encoded somehow.
And since she is apparantly choosing the DNA to surround it, it is easy enough to make the background be similar to the text to be hidden and the keys.
Also, since we're dealing with DNA here, it becomes difficult for someone to do any statistical analysis on it. With any significant amount of DNA it would be rather difficult to sequence it all.
People need to learn that the two simply don't equate. Stealing means that a victim does no longer have what was once theirs. Breaking into something means physically harming a device intended to prevent entry for the purpose of extracting data.
They aren't that far off.
Ok, how's this:
"These crimes were the high-tech equivalent of breaking into a business and stealing valuable secret documents from a locked file cabinet, photocopying them, and returning them to the same cabinet."
Also, Breaking into does not necessarily mean physical harm to a device. If I watch someone open a safe, then without their permission/knowledge I later go and open that safe using the combination I just saw, IMO it is common usage to refer to my opening it as "breaking into" the safe, even though no physical harm was done.