Chris Jeffries
Chris Jeffries

Apart from verbosity, can anyone see anything wrong with using waitfor_ as a prefix for promise returning functions? To me it improves readability enormously (and thus reduces the possibility of...
As a bald statement I think you would be right. However the promise is in this context: .then(waitfor_something) .then(waitfor_somethingelse) i.e. it is not the machine waiting, but my logic.
re-inventing the wheel is not a good idea. It presents maintenance and compatibility issues. There is a solution already. See: https://dev.mysql.com/doc/refman/5.7/en/c-api-multiple-queries.html Why not just interface to that?
Thanks
Maybe allow users to share their list of stations to a central point (optional of course), that could be searched by others to add items to their own station list.
I have a use case, (simply wanting to pass extra information about how data should be presented on a web page e.g. SELECT vs DATALIST, INPUT TYPE=TEXT vs TEXTAREA etc)...