Forgot your password?

typodupeerror

Comment: Re:Logically Logical Logic (Score 5, Informative) 510

by Frnknstn (#39383075) Attached to: Van Rossum: Python Not Too Slow

Yes, that is correct. You should write your apps in Python.

Your libraries, you should write in Python first, because it is also a great prototyping language. If they work fine (which they will in most cases) you have saved yourself a bunch of time. If they are too slow, you have saved yourself a bunch of time by fixing algorithmic bugs in a flexible language like Python. It is now trivial to convert it to bug-free C or C++.

Comment: Re:you are mistaken (Score 2) 292

by Frnknstn (#39266653) Attached to: AMD Confirms CPU Bug Found By DragonFly BSD's Matt Dillon

I stand by my original post.

I did not take issue with the floating point irregularities. In fact, I also believe that the issues he experienced were not due to the FDIV problem he believed to be the cause. I probably would have used the fact that the last release of QuickBasic was in about 1989, before the widespread inclusion of FPUs in PCs, and that QuickBasic would almost certainly use software emulation for floating point arithmetic. It therefore would not have triggered a bug with the FDIV instruction.

What I did take issue with was your notion that he would have run on the AMD chip and seen a less accurate result. As I said, the bug he was talking about was the FDIV bug.

The idea that the QuickBasic would trigger an overheating-related bug on a 2006 Opteron is even more laughable than the OP's original troll post. :p

Comment: Re:Well... how else are you gona prove them? (Score 2) 48

by Frnknstn (#39213993) Attached to: Controversial Bioethicist Resigns From Celltex

True enough, but it's the best information we have.

Exactly, and in this case the best we have isn't good enough, therefore administering untested treatments remains unethical.

If the doctors themselves are not adequately informed about a patient, how could a patient ever give informed consent?

Comment: Re:Why not both? (Score 4, Informative) 164

by Frnknstn (#39129647) Attached to: Is It Time For NoSQL 2.0?

A hierarchy IS a relationship. In a hierarchical databases, child segments and parent segments were the main kind of relationship used.

All relational databases did was allow the relationships to be more freely defined.

Further to that, a key / value pair is also a relationship, in that the key symbolically represents the data. That's why it is correct to call them NoSQL databases: They forgo the complexity of a general query language. In doing so, they also lose the ability to inherently store anything except the most basic relationship: the key / value lookup.

Never raise your hand to your children -- it leaves your midsection unprotected. -- Robert Orben

Working...