You're right, I don't think 1997 is old for programming. Considering most of the widely used programing paradigms today have their roots in the 1960's or earlier, FRP is relatively very young. x2 when you take into account it hasn't even hit mainstream yet.
I think the better question is what can you cite to say the design is based on the programing frameworks.
And my god, read your own quote "Design is important, but I don’t see it as the only way we can be successful."
Did you read the article or even my comment?
My entire point was the final product the consumer sees is the result of a massive effort of many and vary different departments that each play their part.
To say it all comes down to the engineers and even more specifically FRP isn't just unfair to all those other parties, it's just simply and factually incorrect.
So again, if you would for a minute stop insisting you're right and we're so wrong, can you explain to me why the UI for Netflix sucks so bad?
I can't give you that answer, if I have any personal opinions on the UI itself I'm not here to share them. The only real motivation behind my comment was to correct some of the inaccuracies.
If you want more of an official insight you can look to these parts of the article.
We have core metrics we’re always trying to improve. We love to test new features first before implementing them more broadly to see if it’s really moving the needle in a positive direction. In other words, we believe actions speak louder than words. If we determine through testing that it’s successful, then it’s likely going to get released—and people will always have their opinions about new features.
and
Great design, to me, is simple and stripped back.
and
To be an effective designer, you have to understand how things will affect the business.
If you just want to comment on your personal experience with the service you would better spend your time directed at Netflix on social media or here rather than me.
Especially when the quotes you're using seem to disagree with you
Actually if you had read the article you would know it agrees with me pretty much exactly. From the input of several different departments, to the importance of metrics, to the design process, to the incredible amount of testing and the evolutionary type of approach.
Netflix is heavy on data, algorithms and engineering; low on design.
Correct on the first part and it's a very good thing as not many companies are. Incorrect on the second. Just because you don't like the design doesn't mean Netflix is "low on design." As stated in the article the design is extensively iterated, prototyped, tested, refined, etc, etc. If it's “productized” then there is quantifiable support for it.
You can't make everyone happy. Have you considered you may not share the same preferences as Netflix's growing and evolving international audience?
that doesn't mean you've presented a valid source.
Ugh, I can't spend anymore time on this man. It's a primary source directly from an interview of a designer at Netflix. I don't know what more I could do for you apart from personally putting you in touch with someone.
Let's just agree to disagree.