Adianti Studio is a multi-platform environment for PHP development which includes a great range of resources a developer needs to be productive. It uses a tabbed interface which brings basic resources like syntax highlighting, auto-complete, an outline tree, bookmarks, code insight, change tracking, method traceability, workspace saving, brace matching, source code navigation, database navigation, a plugins gallery (managed by the user), a PDF document generator, a calendar, and more. In the professional version, it adds a form design tool called Adianti Designer which allows the user to draw its forms with a graphical interface using Adianti Framework components and containers like inputs, combos, radios, check buttons, imagens, frames, notebooks, datagrids, and more. The professional version also offers a source code generator which allows the user to generate form classes and datagrid classes from database structures using the Adianti Framework pattern of source code.
Fubsy is a tool for efficiently building software. In concrete terms, it lets you conditionally (re)build targets from sources based on which sources have changed since the last build. Typically, targets and sources are all files in a directory tree. In theory, they can be any resource on a computer. More abstractly, Fubsy is an engine for conditional execution of actions based on the dependencies between related resources.
Fluxfont is a specialized tool that attempts to tackle the privacy concerns raised by the possibility to collect information about the fonts installed on a system. Such information can be used to uniquely identify a system. With Fluxfonts, new fonts are randomly created and removed to prevent the same fingerprint from being recreated.
epers stands for "Erlang persistence". As the name suggests, it tries to make it easy to use databases in Erlang programs, to make the language a little more agile, and (humbly) offer a nice adapter for several databases, hiding their implementation details (and the API of the library/framework/driver used to communicate with them). To achieve this, it aims to offer a somewhat consistent API to define and work with your model, while at the same not coupling your code too tightly to it.
Weed-FS is a simple and highly scalable distributed file system. There are two objectives: to store billions of files, and to serve the files fast! Instead of supporting full POSIX file system semantics, it implements only a key-file mapping. Instead of managing all file metadata in a central master, it manages file volumes in the central master and lets volume servers manage files and the metadata. This relieves concurrency pressure from the central master and spreads file metadata into volume servers' memories, allowing faster file access with just one disk read operation. It is modelled on Facebook's Haystack design paper. Only 40 bytes of disk storage are required for each file's metadata, and disk reads are O(1).