Small TVs are not comfortable to watch. No one I know is okay with getting a smaller TV and moving their sofa closer. That sounds ridiculous. If there's any comfort to this capatilistic economy, it is the availability of technology at throw away prices. Most people would rather spend on a TV than save the money.

As for the theatre being obsolete, I do agree with you, atleast to some extent. I think everyone is right here. All factors combined is what makes going to the theatre not worth the effort for most of the movies. It's just another nice thing, not what it used to be.

Also, the generational difference too. I think teen and adolescents have a lot of ways to entertain themselves. The craze for movies isn't the same as it used to be. And we grew old(er). With age, I've grown to be very picky with movies.

My point is, although the model itself may have performed in benchmarks, I feel like there are other tools that are doing better just by adapting better training/tooling. Gemini cli, in particular, is not so great looking up for latest info on web. Qwen seemed to be trained better around looking up for information (or to reason when/how to), in comparision. Even the step-wise break down of work felt different and a bit smoother.

I do, however, use gemini cli for the most part just because it has a generous free quota with very few downsides comparted to others. They must be getting loads of training data :D.

Maybe some new standards and maybe a user configurable per site permissions may make it better?

I'm curious to see how this will turn out to be.

Particularly for indie projects, you can essentially dump the entire code into it and with pro reasoning model, it's all handled pretty well.

Telling you from my own experience. It could work for you if you haven't tried already.

What are you even saying about the choas of the world?! Every dev knows how work is. You are just describing every other software job. Somehow it sounds like you are boasting how matured you are just because you do what your client asks/needs. Even then, many business/software make a concious choice to support or not support something based on some guidance. The guidance could be some core principles or just some product managers whim.

It's highly likely that VLC developers chose not to support the feature for the very reason(s) that's described in the post. It's a concious choice they made. I don't see anything wrong in that. They definitely are not some school kids with some daddy issues to hide behind some code. They clearly have answered all the questions from a technical stand point.