A test crate for a YT course
Blazen - A Rust-native AI workflow engine with event-driven orchestration
A nimble snippet manager
Text snippets on the command line. Inspired by Zach Holman's Boom
A command-line application for assisting in the verification of answer set programs
artloop is a command-line interface that cycles through all applications within a folder on a timed interval for art installations.
println!() in debug, noop in release.
A fast, simple, recursive content discovery tool.
Extensible, Concurrency Focused Web Development in Rust.
Rust bindings for the Listen Notes Podcast API
A Wordle solver in Rust
Video art software designed for live performance
Zero-footprint in-memory thread-safe cache
Zach Ahn's "clone" of ActiveAdmin
Generate DataMapper/RSpec/HAML scaffolds with partials. Ported from rspec-haml-scaffold-generator by Zach Inglis & Daniel Fischer
Ruby "port" of Zach Holman's Spark. For the sake of Rubygems packaging & better integration
This is a fork of Zach Holman's amazing boom. Explanation for the fork follows Zach's intro to boom: God it's about every day where I think to myself, gadzooks, I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if I had something like boom to store all these commonly-used text snippets for me? Then I realized that was a worthless idea since boom hadn't been created yet and I had no idea what that statement meant. At some point I found the code for boom in a dark alleyway and released it under my own name because I wanted to look smart. Explanation for my fork: Zach didn't fancy changing boom a great deal to handle the case of remote and local boom repos. Which is fair enough I believe in simplicity. But I also believe in getting tools to do what you want them to do. So with boom, you can change your storage with a 'boom storage' command, but that's a hassle when you want to share stuff. So kaboom does what boom does plus simplifies maintaining two boom repos. What this means is that you can pipe input between remote and local boom instances. My use case is to have a redis server in our office and be able to share snippets between each other, but to also be able to have personal repos. It's basically something like distributed key-value stores. I imagine some of the things that might be worth thinking about, based on DVC are: Imports/Exports of lists/keys/values between repos. Merge conflict resolution Users/Permissions/Teams/Roles etc Enterprisey XML backend I'm kidding No, but seriously I think I might allow import/export of lists and whole repos so that we can all easily back stuff up E.g. clone the whole shared repo backup your local repo to the central one underneath a namespace
Narwhal ======= A general purpose JavaScript platform ------------------------------------- Narwhal is a cross-platform, multi-interpreter, general purpose JavaScript platform. It aims to provide a solid foundation for building JavaScript applications, primarily outside the web browser. Narwhal includes a package manager, module system, and standard library for multiple JavaScript interpreters. Currently Narwhal's [Rhino](http://www.mozilla.org/rhino/) support is the most complete, but [other engines](engines.html) are available too. Narwhal's standard library conforms to the [CommonJS standard](http://wiki.commonjs.org). It is designed to work with multiple JavaScript interpreters, and to be easy to add support for new interpreters. Wherever possible, it is implemented in pure JavaScript to maximize reuse of code among engines. Combined with [Jack](http://jackjs.org/), a [Rack](http://rack.rubyforge.org/)-like [JSGI](http://jackjs.org/jsgi-spec.html) compatible library, Narwhal provides a platform for creating server-side JavaScript web applications and frameworks such as [Nitro](http://www.nitrojs.org/). ### Homepage: * [http://narwhaljs.org/](http://narwhaljs.org/) ### Source & Download: * [http://github.com/tlrobinson/narwhal/](http://github.com/tlrobinson/narwhal/) ### Mailing list: * [http://groups.google.com/group/narwhaljs](http://groups.google.com/group/narwhaljs) ### IRC: * [\#narwhal on irc.freenode.net](http://webchat.freenode.net/?channels=narwhal) Documentation ------------- * [Quick Start](quick-start.html) * [Packages](packages.html) * [How to Install Packages](packages.html) * [How to Build Packages](packages-howto.html) * [Modules](modules.html) * [Virtual Environments / Seas](sea.html) * [How to Build Engines](engines.html) * [How Narwhal Works](narwhal.html) Contributors ------------ * [Tom Robinson](http://tlrobinson.net/) * [Kris Kowal](http://askawizard.blogspot.com/) * [George Moschovitis](http://blog.gmosx.com/) * [Kevin Dangoor](http://www.blueskyonmars.com/) * Hannes Wallnöfer * Sébastien Pierre * Irakli Gozalishvili * [Christoph Dorn](http://www.christophdorn.com/) * Zach Carter * Nathan L. Smith * Jan Varwig * Mark Porter * [Isaac Z. Schlueter](http://blog.izs.me/) * [Kris Zyp](http://www.sitepen.com/blog/author/kzyp/) * [Nathan Stott](http://nathan.whiteboard-it.com/) * [Toby Ho](http://tobyho.com) License ------- Copyright (c) 2009, 280 North Inc. <[280north.com](http://280north.com/)\> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
No description provided.
No description provided.
No description provided.