There are also tentative plans to integrate core.typed with the Clojure compiler so type annotations can be used during compilation (e.g., type hints through inference).
But it doesn't specifically address collection and distribution of API results as a dataset.
(From the page:)
A licensing agreement is required in order to:
* use the reddit API for commercial purposes. Use of the API is considered "commercial" if you are earning money from it, including via in-app advertising or in-app purchases. Open source use is generally considered non-commercial.
* use the reddit alien logo ("snoo") in your app or for its thumbnail. Any new apps you create must be approved as well before usage. The circular "r" logo is reserved solely for use by reddit, Inc.
* allow users to subscribe to reddit gold via in-app purchases. If your platform allows for it, we encourage you to work with us to make this happen. We see gold purchases as a way for you to help reddit and to give back to the reddit community.
Just to clarify, this is _not_ a remote vulnerability. If it was a means to create a remote shell, then it would be. An attacker would need to first find some way to gain remote access and then could use this bug to gain root privilege.
What about Clojure seems dense or implicit to you? Clojure and Python have a similar feel to me. Both are well-designed in the sense they strive for a small set of primitives useful in solving a broad range of problems.
Thanks for writing the book! I first learned about it from here awhile back. It's extremely helpful to get an expert's take on the what and why of organizing game code.
Piazza, a class discussion app, seems to have good adoption even at schools that use Blackboard. I'm hoping to do similar for homework collection with Classhand.
I expect a switch to a basic platform with apps like Piazza that offer tailored features/user experiences. Not unlike the Salesforce ecosystem. That may be Blackboard's future role.
I think zw meant that the Cocoa binaries can't be distributed with Darling. That's not a major problem for users that have a copy of OS X. Darling can allow users to supply their own.
The potential issue you refer to would also prevent implementing the Cocoa API with Qt.
Using Qt as a Cocoa stand-in sounds complicated. Since Darling already uses its own loader and syscall hooking to provide compatibility for the program, why not do the same for a framework like Cocoa?
Adding function parameters solely for testing purposes is bad. However, poorly-designed functions are often difficult to unit test.
I don't know the entire backstory, but it appears someone wrote a publish! method that took a publish_time argument that was only intended to be used in testing. The problem is that the original code didn't properly support some publish_time values.
This is a good example of the library vs. framework distinction. Frameworks favor opinion over composition.
Can you really identify the number of columns being used by looking at a layout? And is Bootstrap the only one to use 12-columns?
I've used Bootstrap as a starting point for several apps and have modified the grid setup before, but it wasn't because I thought it looked like Bootstrap.
Machine learning is full of hacks to connect theory to producing results given constraints. That's not too different from hacks that are done for the sake of performance in graphics rendering.
I'm not sure how they compare, but a friend of mine's company does something similar: http://www.awayfind.com
They provide similar filters and suggest filters from your communication behavior. E.g., you consistently respond to Peter Norvig quickly, perhaps you want an alert.