18 of the 79 named engineers worked for Apple.
https://www.docdroid.net/uf3z/typec.pdf
My sense is the spec was designed by a consortium and no one company owns it, but I would bet Apple did contribute lessons from lightning to it.
1,747 karma · joined January 4, 2011
18 of the 79 named engineers worked for Apple.
https://www.docdroid.net/uf3z/typec.pdf
My sense is the spec was designed by a consortium and no one company owns it, but I would bet Apple did contribute lessons from lightning to it.
That Lat+Long, the implied time of the venue search call, and some type of disambiguation user id is all you'd need to start building a location history for someone.
The uses for the iPad on shoots I totally get is if you're Mike Kelley and you need to check that flash fills could be composed into a final image for architecture stuff.
But a larger question, at what point do we focus on the novelty of the project, not that it was written in a specific language?
The .net CLR has a lot of the features that he would want to enable the kind of interactive debugging (variable hovers, REPL) he talks about, and Visual Studio itself supports a lot of them.
Personally going from doing C# development in VS2k15 to doing golang development in VSCode feels like going back in time.
Docker just makes it super opaque when you have to rotate images.
density is the answer though, demand will always be there and is harder to control
> gofmt's choices are no one's favorite, but gofmt is everyone's favorite.
If that's actually the case across the full population of Lasik patients that's insane.
Once you know what tools to ignore, and build scripts around the ones you need, it's very powerful.
This line of thinking is like faulting the golang stdlib for having a lot of useful stuff in it.
Is this a joke? or was that intentional?