Saving in developer salaries is the only tangible one. You could argue there is less context switching for developers between languages, but I’ve never actually heard that from someone who builds the apps.
Thank you! Looks very interesting. As for working with LLVM codegen libraries, would you recommend anything beyond the official docs? I found that most books for this sort of thing are based older APIs from a few versions ago.
This is super cool, thanks for sharing!
Are there any books or other resources that you found helpful in learning and implementing Whack? I’m dabbling a little bit with PLs and would love to hear your opinion.
If you need well-maintained mobile SDKs, Mapbox's pricing model is a lot more straightforward. If all you need is basic mapping on the web, OpenStreetMap is adequate.
"we once patched openssl to ignore client cert expiry because somebody forgot to create a process to update keys in the field and all the customer cars started falling offline because their certs had expired."
I don't get the point of this article - why single out Google specifically, when a lot of tech companies (as the article notes) hire contractors?
Furthermore, TVCs at Google can use many on-site perks, and I know a few who transitioned into Googlers. I strongly suspect this isn't common at most companies.
For me, trying to implement an unbeatable tic tac toe game using the minimax strategy. I promised myself I wouldn’t look up any hints online outside the Wikipedia page on minimax. It was several weeks of call stack overflows, reading through logged game states, and waking up at night to try ideas. The code for the final result now looks so simple and elegant, but it’s very deceiving.
LinkedIn may be looking like a decent acquisition right now, but my god it feel awfully old to use, and I'm not sure how long the first-mover advantage will mitigate these shortcomings. Performance-wise, LinkedIn seems a step slower than not just Facebook or Twitter but even products from younger companies. The website is not very responsive, especially when displaying more than a few screenfuls of content, and the mobile apps are equally bad and lack any kind of smoothness.
One of the problems I've noticed while using GraphQL (late last year) was that although there are 'officially supported' libraries in a number of languages, there isn't really feature parity between them.
In particular, I remember that the Ruby implementation we were using required manually parsing the AST to do fairly basic operations described in the spec. I wonder if this situation has improved in the last few months.