[dcrimp]

the inferior methods were slower but more flexible - could handle any and all edge cases. Currently we have a UX that really efficiently realises 80% of cases.

To relate to the article - google flights is the Keyboard and Mouse - covering 80% of cases very quickly. Conversational is better for when you're juggling more contextual info than what can be represented in a price/departure time/flight duration table. For example, "i'm bringing a small child with me and have an appointment the day before and I really hate the rain".

Rushed comment because I'm working, but I hope you get the gist.

Current flight planning UX is overfit on the 80% and will never cater to the 20% because cost/benefit of the development work isn't good