rhizome
mb-sound-jackffi
Our great sponsors
| rhizome | mb-sound-jackffi | |
|---|---|---|
| 8 | 2 | |
| 814 | 2 | |
| - | - | |
| 1.8 | 0.0 | |
| almost 3 years ago | over 1 year ago | |
| Ruby | Ruby | |
| MIT License | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rhizome
- How do optimizing compilers convert variables into registers
- YJIT: Building a New JIT Compiler for CRuby
-
Tenderjit – A JIT for Ruby Written in Ruby
There was actually an existing, similar in concept, Ruby JIT, Rhyzome: https://github.com/chrisseaton/rhizome.
It's good to see (IMO) the development of a JIT in a strict sense. I'm personally skeptical about the current approach (invoking a compiler separately).
On the other hand, it's important to know that JITs may take a long development time to be performant, and that they also complicate the performance profile of a virtual machine.
-
Let's write a compiler, part 5: A code generator
Lots of compiler tutorials are like this - there's very little out there to explain how compilers really work.
This is my effort - trying to show genuine data structures and processes.
https://github.com/chrisseaton/rhizome
- Thoughts about Intermediate representations
- A JIT for Ruby, implemented in pure Ruby (/r/ruby)
- Rhizome – a JIT for Ruby, implemented in pure Ruby
mb-sound-jackffi
-
Tenderjit – A JIT for Ruby Written in Ruby
Yeah, here's my main sound repo: https://github.com/mike-bourgeous/mb-sound
There's also an FFI wrapper for jackd: https://github.com/mike-bourgeous/mb-sound-jackffi
I'm certain there are still improvements that could be made to the APIs and to performance, so I'm not currently releasing these on rubygems.
-
Torvalds: Shared libraries are not a good thing in general
Shared libraries and dynamic linking make writing FFI wrappers in other languages possible. If every library were statically linked, I wouldn't be able to write things like this: https://github.com/mike-bourgeous/mb-sound-jackffi
What are some alternatives?
yjit - Optimizing JIT compiler built inside CRuby
reprepro-updater
sqlite-parser - JavaScript implentation of SQLite 3 query parser
mb-sound - A library of simple Ruby tools for processing sound.
grammars-v4 - Grammars written for ANTLR v4; expectation that the grammars are free of actions.
spinnaker_sdk_camera_driver - Point Grey (FLIR) Spinnaker based camera driver (Blackfly S etc.)
zetasql - ZetaSQL - Analyzer Framework for SQL
tenderjit - JIT for Ruby that is written in Ruby
swifties - a custom language construction kit
pointgrey_camera_driver - ROS driver for Pt. Grey cameras, based on the official FlyCapture2 SDK.
langjam
spinnaker_sdk_camera_dri