> And yes, in finance, the correlations between asset classes shoot up toward 1 in periods of crisis (black swan event) . Hence, the research for tail-hedging strategies...
Related to what you said here, I was surprised there wasn't a comparison with Vine Copulas in the paper or thread! But this is pretty far outside of my realm of expertise, so maybe it shouldn't be surprising.
Efficiently? Maybe. Providing the same type trust and guarantees? Probably not. A public, append-only Merkle tree just has a lot of interesting properties and I think there are spaces where they are useful.
> So they set out to describe it as „an accident“ because „blameless post-mortems“ are something people really like?
As someone who has operated bug bounty programs, understanding what processes might have prevented things from going off the rails _in spite of_ internal actors with different motivations is very helpful to me. Placing all of the blame on an individual removes the opportunity to improve things.
This looks fantastic! I'm working on a desktop app and I've been struggling with the extensibility story in the back of my mind for a couple of weeks now.
Thanks for building this!
edit: For what it's worth, the use case and value of something like this was immediately apparent to me.
> I can't find any motivation to write abstract algebra to build UI widgets
This made me chuckle, because I am at this very moment trying to apply the "tagless final style" described here[0] to a custom GUI in a personal-for-fun-and-learning ocaml project : )
For me, I use the simple stuff (Semigroup, Monoid, Monads, Functors, ..) the most. Often times I'll be reasoning about a problem I'm working on in Haskell and realize it is a monad and I can reuse all of the existing monadic control structures. It is also helpful the other way, where you start working with someone else's code and seeing that it is a e.g. Monad immediately tells you so much concrete info about the structure, where in a less structured language you might need to reed through a bunch of docs to understand how to manipulate some objects. The "killer app" is all of that extra structure shared throughout all of the codebases.
Right? Also these companies probably hired a lot of folks during the pandemic, and also relaxed their performance criteria while everyone was adjusting to remote work... So this just sounds like some folks are being caught off guard by the fact that yes, there are real performance expectations and you might not be meeting them.
Agreed. If you're an individual who wants to work this hard, hopefully you can find a team of like-minded folks who will work hard with you and make sure that it is structured in a way that you all reap the benefits.
Flask is a multi-threaded server, so while only one thread can execute Python code at a time (due to the GIL), you still get concurrency with respect to IO. Not to say that e.g. FastAPI won't get you more RPS, but it may or may not be as dramatic as you would expect.
Related to what you said here, I was surprised there wasn't a comparison with Vine Copulas in the paper or thread! But this is pretty far outside of my realm of expertise, so maybe it shouldn't be surprising.