This is a deeply predictable (and pedestrian) take, and I 100% expected to see it here (as I expect to see it in any technical forum).
Highly technical people -- developers, engineers, etc -- are much more likely (at least in my experience) to react negatively to nonlinear storytelling. Further, the reaction is almost never "wow, not for me" but instead "THIS IS STUPID".
It's essentially the equivalent of walking through, say, a Mondrian exhibit and spouting "my kid can do that."
I do not know why this correlation exists. I could make guesses, tying the exacting nature of programming with an attraction to well-defined and explicit storytelling, but it is what it is.
THE BIG SLEEP is awesome. MULHOLLAND DRIVE is a tremendous (and award-winning) film. Ambiguity and vagueness are integral to art (and life!).
Years ago, I saw a play by Maria Irene Fornes called THE DANUBE. It's a bizarre, baffling, and beautiful piece, and you cannot really approach it like you would (say) a Marvel film expecting a traditional narrative. That's not what it's FOR. It's an experience. You have to let go of the desire to tick off plot points and characters like players in a football program and just experience the art on its own terms.
Creating something that includes, or even hinges on, ambiguity is challenging in the extreme. It's like when jazz musicians break the "rules" of music and melody; you can only break the rules and have it work when you have really mastered the underlying craft.
Exploring these kinds of challenging works can be incredibly rewarding. I encourage anyone reading this to do so. I long ago decided that if I only ever saw plays/read books/watched movies that I liked, I wasn't branching out enough. Find things that challenge you, and engage them on their own terms. Figure out why (for example) a host of professional movie critics loved Lynch's film when it left you cold and maybe even angry. What do they see that you don't?