JavaScript boy and “lovely thoughtleader” 
he/him 
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Screen recording of running Rome in daemon mode and linting a project. Same as yesterday, 524 files, 40,000 lines of code. Difference here is that subsequent commands pull from a memory cache. Watch the last command closely, it's instantaneous.pic.twitter.com/33dUDS07Ew
Also more context on what is actually being “memory cached”: Only the formatted code and errors for each file are cached. We are still computing all the possible files, filtering them with globs, talking to the workers to get their cached value, and printing it all.
Biggest way I make this so fast is that I’ve written all the code, so it’s pretty easy for me to identify inefficiencies. I can change on piece to fit the performance characteristics of another (ie. changing API, integrating caches etc)
Also to be clear, there are some libraries that I've forked. Notably mozilla/source-map and babel-parser. Both for some of the reasons listed, changing the API and cache integration. Having everything be 100% typed, tested, and in the same codebase gives me a lot more confidence.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
