LPCRoy

5 ms·

1.
Tautology Tests are bad because they're not good(medium.com)
3 points by LPCRoy 9y ago|0 comments
2.
Automated Style Review with Linty Fresh(eng.lyft.com)
9 points by LPCRoy 11y ago|0 comments
3.
by LPCRoy 13y ago
This has nothing to do with Go. It sounds like a case of poorly managed dependencies and build rules and likely weak engineering. The fact that they wanted to support the iPad and chose Go also shows this wasn't well thought out.
4.
Show HN: GLSL Compiler - UglifyJS for WebGL(glslunit.appspot.com)
6 points by LPCRoy 15y ago|0 comments
5.
by LPCRoy 15y ago
A little background on this: I work at Google on the MapsGL effort, and as part of launching MapsGL we decided to launch a unit testing framework we wrote for our shaders. Shaders can get hugely complicated and bug prone, and don't provide
6.
GLSLUnit - A unit testing framework for WebGL Shaders written in JavaScript(glslunit.appspot.com)
2 points by LPCRoy 15y ago|1 comments
7.
by LPCRoy 15y ago
Sorry, this will only work in browsers that support WebGL, so Chrome and FF7+ for now.
8.
by LPCRoy 15y ago
We do not have an exclusion list, but we do run a micro-benchmark on your machine to ensure your GPU will be powerful enough to handle MapsGL. You can try upgrading your drivers as well, which sometimes improves performance (looks like inte
9.
by LPCRoy 15y ago
There is also "LINQ for Javascript", which is fully integrated in with JQuery and VS as well. http://linqjs.codeplex.com/ Streams seems to be a proper subset of the things you can do with linqjs. Sometimes MSFT can do cool things too, i
10.
by LPCRoy 15y ago
Can't really comment, but this blog post may point you in the right direction. http://googleblog.blogspot.com/2009/08/bright-side-of-sittin...
11.
by LPCRoy 15y ago
This was my first big launch at Google! The traffic estimates we eliminated are different that the ones we use in Route Around Traffic. The old ones (e.g. "Up to XX Hours, XX Minutes in traffic") were pretty inaccurate and was a picture on