New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using e and Τ? #29
Comments
+1 I agree with OP. I never understood why anyone would ever use plain Pi when we have so much better constants. Please fix!!!11111oneoneonelevenπ |
I agree. Perhaps you could use both contemporarily. The constant to search the file in is whichever you find first. As to which constant to search in to find the values, that information too can be stored in whichever constant you find first, so it all works out in the end. |
@nsharmon oh yeah, it could be awesome if we could parallelize the search through an hadoop mapreduce query on the cloud. That would definitely be something I'd want in my desktop file system which I desperately need to scale on the cloud. |
I think that, as i said on issue #18, the easy computable irrational numbers would be the best to use instead pi, euler or any of the transcedental numbers. As @ke7ofi said, Fibonacci seems to be a good number to start. |
This issue seems to be a duplicate of #18. |
Everyone knows Euler's constant and Tau are better constants that scale better to cloud infrastructure. They also both contain every finite sequence of digits of Pi in them anyway.
It would be cool if we could use these clearly superior constants instead of Pi, which I believe is deprecated and should not be used for anything in the age of web scale and the cloud. Due to recent breakthroughs like the internet of things - it would be cool if you let users choose which mathematical constant to use instead of Pi.
By the way, one easy way to calculate Pi based on e is to take a circle with radius e and then compare the ratio between its diameter and circumference so you could introduce an abstraction layer.
The text was updated successfully, but these errors were encountered: