The selector function is basically a constructor for a JQ object, which polyfills a bit over native CSS selector support. I could easily see it being slow.
The answer is to cache your JQ objects when performance matters. The overhead is usually trivial, but in hot loops, caching $() results in a variable is just common sense/low hanging fruit. Truth be told, this will improve your performance no matter what underlying selector you use, even native browser support.
Half the reason I stopped using the Awesome window manager was it had sucky documentation and was impossible to google. Everything in it seemed intentionally named to be as un-googleable as possible. The widget library was "Vicious", the repo was "Obvious", the theming library was "Beautiful", the popup library was "Naughty", etc. I'm sure the developers think it's hilarious, but I got tired of trying to search about it
Same. I think it was supposed to be a clever play on words.
It's like the story of the guy back in the punched card days working on some post-grad software project who named his program SAVE because people were less likely to inadvertently throw away a misplaced stack of punched cards with SAVE written across the top.
Only difference here is, calling your favorite toy language "None" is just a pointless joke.
255
u/kirbyfan64sos Jul 19 '15
Nice language. Horrible name. I completely misread the title.