Functions should be static instead of instance-based.

[JoshMcCullough]

For most functions, it seems I should be able to simply call (for example), geostats.min(values) without creating a geostats instance.

I haven't used the library enough yet to understand when/why I'd want my own instance of geostats instead of just calling its functions statically.

[simogeo]

This could be discussed indeed but you could also imagine to compare several series as follow :

if(serie1.min() < serie2.min()) {
// whatever
}

[JoshMcCullough]

Yes, I think it is pretty simple to make it work both ways by having the instance methods call the static methods. Just a suggestion. 👍

[simogeo]

Would you propose a pull to make it work both ways?

[JoshMcCullough]

Yes I'll work on it at some point this week.

On Sat, Mar 21, 2015 at 12:13 PM Simon Georget [email protected]
wrote:

Would you propose a pull ?

—
Reply to this email directly or view it on GitHub
#22 (comment).

[mtralka]

@JoshMcCullough Apologies to ping an old issue. I've made GeoBuckets which is a modern take on geostats. All functions are static. Additionally the library is tree-shakable and asynchronous. Please let me know if that fulfills your usage scenario. If not, I'd be happy to accept PRs or make adjustments as needed

[simogeo]

@mtralka see new reference to GeoBuckets in geostats readme file 418113a

[mtralka]

@simogeo Awesome stuff! I appreciate the mention. Thank you for your continued work with geostats