A JavaScript 2D physics engine.
MCP server for Automattic internal context (Linear, Slack, P2s)
png to svg png2svg
Static analysis tool for JavaScript
Encodes and decodes address formats for various cryptocurrencies
Pipe any command line output to a slack channel or private message
Pipe any command line output to a slack channel or private message as a code block
Encodes and decodes address formats for various cryptocurrencies
Static analysis tool for JavaScript
Static analysis tool for JavaScript
Static analysis tool for JavaScript
virtual physical network infrastructure layer interface
virtual physical network infrastructure layer for node
virtual physical network infrastructure layer for chrome
bioinformatics toolkit in rust
An easy to use framework for building Ergo headless dApps.
Convert bmap images to Android sparse
A library for converting string-string hashmaps to structs.
derive macro for map2struct.
The p2sh Programming language interpreter
use a pgdump to create a sqlite db
Converts the zip file to an sqlite archive.
P2: component-based HTML templating for Ruby
## A mirror API for Ruby In various [research][p1] [projects][p2] the advantages of having a [mirror API][p3] to separate reflection from a language implementation have been discussed, and "industry grade" implementations exist for [Java][p4] and [C#][p5]. This project aims at providing a number of specs and classes that document a mirror API for Ruby. The mirror implementation that is part of this project will use only those language facilities that are available across Ruby implementations. The specs, however, will also test behavior that cannot be provided in such a manner. The idea here is that in time, all implementations provide their own implementation of the mirror API, and all implementations collaborate on this one spec. Why do this, you ask? Because Ruby needs tools, and those tools need to be written in Ruby. If they are not, then people will be excluded from tinkering with their tools, thus impeding innovation. You only have to look at Emacs or Smalltalk to see what's possible when programmers can extend their tools, all tools, in a language they feel comfortable in. If we have a standard mirror API, all tools that are written **for** Ruby, **in** Ruby, can be shared across implementations, while at the same time allowing language implementers to use the facilities of their platform to provide optimal reflective capabilities without tying them to internals. [p1]: http://www.cs.virginia.edu/~lorenz/papers/icse03/icse2003.pdf "Pluggable Reflection: Decoupling Meta-Interface and Implementation" [p2]: http://bracha.org/newspeak-spec.pdf "Newspeak Programming Language Draft Specification, Version 0.06, pages 40 onward" [p3]: http://www.hpi.uni-potsdam.de/hirschfeld/events/past/media/100105_Bracha_2010_LinguisticReflectionViaMirrors_HPI.mp4 "Linguistic Reflection Via Mirrors" [p4]: http://bracha.org/mirrors.pdf "Mirrors: Design Principles for Meta-level Facilities of Object-Oriented Programming Languages" [p5]: http://oreilly.com/catalog/progcsharp/chapter/ch18.html "See esp. 18-3, highlighting how C# reflection works on assembly rather than VM objects"
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.