3 ms·

Cool. Various issues: * Airport code matches should always rank higher than substring searches. I found a number of cases where it was 3rd or 4th. * I'm onto

Cool. Various issues: * Airport code matches should always rank higher than substring searches. I found a number of cases where it was 3rd or 4th. * I'm onto your crypto mining operation ;) - the searches are pretty CPU intensive. Do you do any kind of threadpool sizing based on number of cores / existing load average? * It'd be nice to display some kind of status in the main screen beyond just adding flights as they come in. "X of Y searches complete" etc * Speaking of the CPU load, it'd be cool to stop it as soon as "Update Search" is hit, since the prior searches are now obsolete. * Finally, if you can add a truly useful "I don't really care about the dates, just somewhere around here" mode, that'd be awesome. _You picked Sunday but that adds a minimum of 5 hours; you really should pick Wednesday. Also it should be a week before._

maxmorlocke 5y ago
Thanks for the feedback. Re: codes: yup, that's a bug and will be fixed (or at least the obvious one will be...) Re: performance - this is on our radar, and we'll keep chipping away at making things a little better as we go. We do have some limits based on system characteristics, but the primitives available to chrome extensions for system information are limited (praise WECG - there's a lot of bad that can be done with too much info). Re: ballpark dates - This is on our radar, but is both a thorny interaction and below the priority of a few other things users commonly request. No firm commitments on dates as such... but yes, it's a useful tool when you know you want a "May" vacation, and you want a reasonably priced flight that is comfortable.