InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now. Learn more →
V8 Alternatives
Similar projects and alternatives to V8
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
-
-
-
-
-
-
Stream
Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.
-
-
-
-
gallery
Discontinued Flutter Gallery was a resource to help developers evaluate and use Flutter (by flutter)
-
-
-
-
ChakraCore
Discontinued ChakraCore is an open source Javascript engine with a C API. [Moved to: https://github.com/chakra-core/ChakraCore] (by Microsoft)
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better V8 alternative or higher similarity.
V8 discussion
V8 reviews and mentions
Posts with mentions or reviews of V8.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2025-07-04.
-
JavaScript's Asynchronous Execution: V8 and the Event Loop
Source Code: Key V8 APIs are defined in v8.h, isolate.cc, and api.cc (see V8 GitHub, version 12.5).
-
Hidden Classes and Inline Caches in V8
V8 GitHub Repository
-
MCP Run Python
It's a bit hard to do comparisons without going into threat models and all that _fun_ stuff :shrug:
For example, JS runs in almost every browser on earth too, yet it took V8 devs 2 years to find out that `Math.expm1()` could return -0.0 (https://chromium.googlesource.com/v8/v8.git/+/56f7dda67fdc97...). This is a cherry-picked example, and JS is clearly more complex than WASM, but still.
Just because stuff runs on a lot of devices doesn't mean it's more or less secure.
Linux runs on quite a few devices too, yet we still find bugs, people still don't ship updates to said bugs, yadda yadda yadda.
My point is just that lots of devs often skip the threat modeling and just think "I'll slap it in a WASM thingie an it'll be fine". Well good luck.
-
Tiny JITs for a Faster FFI
Much of the standard library in v8 is written in Torque, a custom language.
https://v8.dev/docs/torque
Example file for array.find(…): https://github.com/v8/v8/blob/5fe0aa3bc79c0a9d3ad546b79211f0...
-
🚀⚙️ JavaScript Visualized: the JavaScript Engine
V8 Docs || V8 Github || Chrome University 2018: Life Of A Script If you like the post then follow me for more and subscribe on youtube Dev Studio
- Show HN: V8serialize – Read/write V8-serialized JavaScript values from Python
-
JavaScript Dates Are About to Be Fixed
Thank god!
Presumably this new API will fix the fact that JS does in fact know about some time zones, but not most.
Shield your eyes from this monstrosity that will successfully parse some dates using `new Date()` in some select special time zones, but assume UTC in the other cases:
https://github.com/v8/v8/blob/781c20568240a1e59edcf0cb5d713a...
-
The Renaissance of Meteor.js
And that happened in 2021.
-
Boehm Garbage Collector
https://chromium.googlesource.com/v8/v8.git/+/HEAD/include/c...
Due to the nature of web engine workloads migrating objects to being GC'd isn't performance negative (as most people would expect). With care it can often end up performance positive.
There are a few tricks that Oilpan can apply. Concurrent tracing helps a lot (e.g. instead of incrementing/decrementing refs, you can trace on a different thread), in addition when destructing objects, the destructors typically become trivial meaning the object can just be dropped from memory. Both these free up main thread time. (The tradeoff with concurrent tracing is that you need atomic barriers when assigning pointers which needs care).
This is on top of the safey improvements you gain from being GC'd vs. smart pointers, etc.
One major tradeoff that UAF bugs become more difficult to fix, as you are just accessing objects which "should" be dead.
-
The Everything NPM Package
> If that standard library would be written in JS, a new browser (or rather a new JS engine being a part of the browser) could just use some existing implementation
That sounds great, but I'm doubtful of the simplicity behind this approach.
If my understanding is correct, v8 has transitioned to C++[0] and Torque[1] code to implement the standard library, as opposed to running hard-coded JavaScript on setting up a new context.
I suspect this decision was made as a performance optimization, as there would obviously be a non-zero cost to parsing arbitrary JavaScript. Therefore, I doubt a JavaScript-based standard library would be an acceptable solution here.
[0]: https://github.com/v8/v8/tree/main/src/runtime
-
A note from our sponsor - InfluxDB
www.influxdata.com | 18 Jul 2025
Stats
Basic V8 repo stats
63
24,260
10.0
7 days ago
v8/v8 is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of V8 is C++.
Popular Comparisons
Sponsored
InfluxDB – Built for High-Performance Time Series Workloads
InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
www.influxdata.com