cmoog

Thanks! That's because it just started. I intend to keep the full history.

I can assure you I am not earning a commission :)

Agreed. Planning to add that next.

I plan to add that shortly. The data collection model supports it though.

Haha true. I should fix that.

Source code here: https://github.com/cmoog/traderjoes

Discussion of regional price differences in other comments.

And with Haskell and Nix at that!

Good catch. These prices are hard coded to my local store in Chicago. Soon I will add support for selecting your local store.

Yes, you make a good point. Although I suspect there may be regional differences in price, I haven't yet run the diff on that. Should be simple enough for me to allow the user to select their regional store location.

Source code here: https://github.com/cmoog/traderjoes

This is not correct as stated. It does not “tend towards extremes” as you might expect intuitively. That would be the case if half the time it approached 100% blue and half the time it approached 100% red, which is precisely not what happens.

For me as well. And when my stochastic probability professor posed this question to the class by way of hands, it was nearly unanimous in favor of the 0/100% end behavior.

Ah, good idea! I'll add those in a bit and will remark that the answer/proof are specific for the special case where r_0 = b_0 = 1.

Not to be a FOSS-thumping loser, but an a16z backed company that records anything and everything on your screen sounds like a recipe for disaster. May as well set the countdown for the bait-and-switch.

Looks like a cool demo with neat tech though. Maybe someone will reimplement as OSS?