188 karma · joined September 14, 2008
That being said, you should take a look at the '-s' flag for saving state to a sqlite database. After the initial run the stored state can be used to only scan changed files. For a patch with a few files changed it should be about 0.5s to run the analysis.
If you want to start working on that, feel free to open up an issue (https://github.com/etsy/phan/issues/new) to start a conversation about it.
We currently store method/function callers in the sqlite database (see https://github.com/etsy/phan/blob/master/src/Phan/Analyze/Br...), but aren't yet exposing an interface for getting callers. We'll want to store callers for constants, classes, properties and global variables as well.
I'm not sure what SIMD refers to. Can you clarify that?
For now, we have a primordial Syntastic vim plugin (https://github.com/etsy/phan/blob/master/plugins/vim/bundle/...) for getting errors into the quickfix view.
The rectangle of light isn't noticeable at all in normal light if you adjust the brightness on the tablet well. In a dark room it can be noticeable, though.
As for hot-linking; I have no business plan and just wanted to make something useful. I should probably figure that stuff out.
You should check out Bugshot (https://itunes.apple.com/us/app/bugshot/id669858907?mt=8) which I think does a much better job on iOS.
To cure the curiosity, however, we're largely running on Linux, Apache, MySQL, PHP with many other tools thrown in the mix.
re Full-Stack: We're looking for people who design and build full systems from low to high levels. Some have made their career working just as a front- or back-end hacker. We want to meet people who wouldn't dream of letting someone else take half their work or who would be comfortable throwing part of the problem over the fence. People that are a good fit probably don't care that much about what the stack is beyond some reasonable constraints.
If you end up sending that cover letter there's a chance that we'd all be amused enough to read your resume.
The IRC coffee service uses a Pelouze postage scale and https://github.com/morria/coffeed
When resources are thin and there is no way to deduce a provably optimal allocation, we start having to make guesses given the best possible information and algorithms. Until we can come up with something better, schools will continue needing instruments like these (as well as other tools) for making the best possible guesses.
http://www.childrensprogress.com/about-us/softwareengineer.s...
Perhaps by assessing all students to find the easiest concept the child has not mastered, teaching it to them, and then measuring their ability after being taught, we would be able to measure their ability to use new information effectively.