HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
rubyjs
therubyracer
C++2010–2021
rubyjs / therubyracer · Archived

therubyracer

Embed the V8 Javascript Interpreter into Ruby

9Distinct people
9Mentions
0Explicit recommenders
1.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Embed the V8 Javascript Interpreter into Ruby

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year9 dated mentions

Observed mentions: 2010-11-08 21:54:05 UTC to 2021-12-14 21:45:03 UTC.

01232010-01-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20102011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20102010-01-01 00:00:00 UTC2011-01-01 00:00:00 UTC110
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC312
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC202
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC000
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101

What Hacker News says

9 sources
I use both OSX and Linux extensively. I had the choice to go either way for my work computer and I chose OSX (intel chip). A couple of days ago I wanted to use a Ruby gem ( https://github.com/rubyjs/therubyracer ) for some random project. To install the library (compile native bindings), OSX wanted me to download an install 12 GB of crap (full XCode, it didn't work with the command line tools)... In linux it was just a matter of downloading and installing the gem (100MB at most). That's crazy. What I dislike more and more about OSX is how they have been aggresive against developers and technical people in the last years (like, why do I have to jump through hoops to modify my /usr/lib folder with SUDO/root? I AM ROOT ASSHOLE OS, LET ME DO WHATEVER I WANT TO MY COMPUTER. But other than that, it's OK.
In Linux Touchpad Like MacBook Update: Touchpad Gestures Now Shipping
This new version fixes issues that many customers have had with rubies built with darwin15 (OSX 10.11). For this version, no V8 pre-compiled binaries were available. So the install fallbacks on the source, and people with XCode 7.3 installed were unable to compile V8 as is - because Clang 7.3 now enables the -Wshift-negative-value warning - itself turned into error by a global -Werror defined in libv8. This resolves many issues raised by therubyracer users: https://github.com/cowboyd/libv8/issues#205 https://github.com/cowboyd/therubyracer#405 https://github.com/cowboyd/therubyracer#403 Despite what the changelog states, this is indeed released, thanks to @ignisf. For the record, the error was looking like that: In file included from ../src/elements.h:32: ../src/objects.h:5252:44: error: shifting a negative signed value is undefin
Read the rest
ed [-Werror,-Wshift-negative-value] static const int kElementsKindMask = (-1 << kElementsKindShift) & ~~ ^ ../src/objects.h:7386:36: error: shifting a negative signed value is undefined [-Werror,-Wshift-negative-value] (~kMaxCachedArrayIndexLength << kArrayIndexHashLengthShift) | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ 2 errors generated.
In OS X 10.11 Ruby / Rails users can install therubyracer again
The readme compares this to the ruby racer (https://github.com/cowboyd/therubyracer): Similarities: Both are using similar integration with ruby's garbage collector. Actually, Mustang's code which handles that references is just improved version of TheRubyRacer's code (check the ext/v8/v8_ref.cpp). Both are reflecting JS objects to ruby and vice-versa. Diffs: Mustang reflects all JavaScript objects and values properly. Properly, means all values from within V8 are reflected to Mustang::V8::* objects, regarding V8 inheritance tree which you can find here. Once reflected ruby object (and vice-versa) is always the same object in ruby world. All reflected V8 objects acts exacltly the same as ruby natives. For example you can deal with Mustang::V8::Array exactly the same as with native Ruby arrays (eg. they are comparable with ruby objects, et
Read the rest
c). Functions are reflected more accurately. Ruby objects' methods are represented properly. Classes are converted to V8 function templates, so you can deal with them as with prototypes. Different approach to deal with contexts, compiling JS scripts and exceptions handling. Support for regexp reflections. Way more friendly ruby api. A very thorough test suite (over 250 tests passing on all ruby versions) Clean codebase, less magic, fully documented. Lower memory usage.
In Mustang - A Ruby interface to V8

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.