thicket
I’m not offended by the idea, but I definitely subscribed here to hear about the electronic game development industry. So, my vote is against board/card game posts
Are you trying to do something programmatic with thousands of calls, or just engineer your own bespoke stuff? Seconding AWS SNS for big things. For small projects things, Google Voice at least used to be free or cheap and let you treat phone communications much more like emails than a standard phone number does.
Does anybody have insight into the design choice away from named arguments? Everything in the article and in the comments seems like different levels of kludge around an unfortunate decision
For the curious: this is an impressive and meditative ~5 minute video showcasing a simple but flexible recursive drawing system. I found it worth the watch and I’m curious about the code
Interesting. Would love to know more about languages that can and can’t be parsed by this approach; the abstract assumes some greater formal-language proficiency that I don’t have
While I would love to see Twitter auguring straight into the ground, Twitter’s API changes would explain some portion of this traffic changes. I wonder if there are any other proxy measures for audience engagement as separate from basic traffic
Wow, the tone here is… really arrogant. When somebody starts off calling their audience idiots, I find it a little harder to read along.
I think I’m glad I did, though. Tone aside, I think it’s a worthwhile insight to note that caching is making up for a shortcoming in your data supply, and that fixing that shortcoming if at all possible should be a priority. The author’s summary would have helped me in the past:
Caching is a useful tool, but can be easily abused without giving any signs of the abuse.
Don’t get involved with caching till the last minute; find any other way you can first. Optimise your application before you use the blunt tool of caching.