Explore >> Select a destination
|
You are here 
|
timilearning.com | ||
| | | | |
babashka.org
|
|
| | | | | A categorised directory of libraries and tools for Babashka | |
| | | | |
www.blog.montgomerie.net
|
|
| | | | | I posted YACYAML, the Cocoa YAML parser/object archiver I've been working on for a little while to GitHub today. It converts Cocoa objects to and from YAML, a plain text, human friendly data serialization format. YACYAML can be used in lots of ways - from replacing plists or JSON for simple config files, up to storing entire custom documents in an easy to view (and easy to hand-edit) format. Why have I made this? The short answer is that I like YAML. It's 'nicer' than plists and JSON to edit, and it's far, far, nicer to look at than NSKeyedArchiver's binary representation (which, to be fair, wasn't meant to be human-readable in the first place, but I think it would be good if it was). | |
| | | | |
bizety.com
|
|
| | | | | In this post, we look at Protocol Buffers and JSON, and draw a comparison between the two, looking at different industry tests to draw our own conclusions. | |
| | | | |
mill-build.org
|
|
| | | [AI summary] The blog post explores the inner workings of modern build tools, emphasizing their use of a build graph to manage tasks efficiently. It compares tools like Bazel, Gradle, and Mill, highlighting how each defines and processes the build graph. The post explains caching, parallelism, and the importance of a structured build graph in optimizing build processes. It also discusses the advantages of using a programming language for defining build configurations, such as better IDE support, compiler assistance, and access to a rich library ecosystem. The conclusion underscores that while build tools may appear different on the surface, they share a common goal of enhancing development efficiency through automation and optimization. | ||
