q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
What's New!
THE JOURNEY THROUGH TIME

Explore Black History

Explore the people, places, events, achievements, struggles and stories that shaped our journey.

✊🏾

Civil Rights

Movements, leaders, victories and the continuing fight for equality.

⚙️

Black Inventors

Innovation, patents, science, technology and world-changing contributions.

🏆

Sports

Pioneers, champions, Negro Leagues, records, activism and excellence.

♟️

People

Meet the people whose lives, choices and achievements shaped the journey.

📍

Places

Black towns, communities, institutions and places where history happened.

📜

Events

Moments that changed communities, movements, institutions and the nation.

Enter a person, place, event, or topic.
MY'STORY

The MOVE Fire

This is a personal recollection on the Move fire on May 13, 1985 Philadelphia police fired thousands of rounds at the MOVE house, city officials approved dropping an explosive device on the roof, the resulting fire was allowed to burn, 11 people—including five children—died, and 61 homes were destroyed. Philadelphia City Council later called it a “brutal attack carried out by the City of Philadelphia on its own citizens” and acknowledged that no individual faced criminal consequences for the bombing. One timeline correction worth preserving for the BHP record: the major previous MOVE-police confrontation was August 8, 1978, about seven years before the bombing, not a year or two earlier. Officer James Ramp was killed, other police and firefighters were wounded, nine MOVE members were later convicted, and television cameras recorded police beating Delbert Africa during his arrest. The 1985 MOVE Commission later specifically criticized city planners for failing to adequately use lessons from that 1978 confrontation. And that actually strengthens the point you’re making: 1985 did not happen without precedent or institutional memory. There had already been a deadly confrontation with MOVE, years of conflict, negotiations and police involvement before Osage Avenue.

MORE →
BLACK FACTS
The Truths They Never Taught You...

Ruler of the Mali Empire in the 14th century

Mansa Musa was the ruler of the Mali Empire in West Africa. Details recorded here should be sourced; unknown information is left blank.

MORE →
BHP gathered finds from its connected research sources. Showing the 4 strongest Black History matches.
← BACK TO RESULTS
Wikipedia

V8 (JavaScript engine)

V8
DeveloperGoogle[1]
Release2 September 2008; 18 years ago (2008-09-02)
Stable release
11.4[2] Edit this on Wikidata / 24 May 2023; 3 years ago (24 May 2023)
Written inC++[1]
PlatformIA-32, x86-64, 32-bit ARM, AArch64, 32-bit MIPS, MIPS64, PowerPC, IBM ESA/390, z/Architecture
TypeJavaScript and WebAssembly engine
LicenseBSD-3-Clause[3]
Websitev8.dev Edit this on Wikidata
Repository

V8 is a JavaScript and WebAssembly engine developed by Google for its Chrome browser.[1] V8 is free and open-source software (FOSS) and part of the Chromium project. It is also used in non-browser contexts, notably including the Node.js runtime system.[1] Other server-side JavaScript runtimes use alternative engines, such as Bun (which uses JavaScriptCore) and Hermes (used by React Native).

History

[edit]

Google created V8 for its Chrome browser, so V8's first release coincided with Chrome's first release in 2008.[citation needed] It was named after the V8 engine, and its lead developer was Lars Bak.[4] For several years, Chrome was faster than other browsers at executing JavaScript.[5][6][7]

The V8 assembler is based on the Strongtalk assembler.[8] On 7 December 2010, a new compiling infrastructure named Crankshaft was released, with speed improvements.[9] In version 41 of Chrome in 2015, project TurboFan was added to provide more performance improvements with previously challenging workloads such as asm.js.[10] Much of V8's development is strongly inspired by the Java HotSpot Virtual Machine developed by Sun Microsystems, with the newer execution pipelines being very similar to those of HotSpot's.

Support for the WebAssembly language began in 2015.[11]

In 2016, the Ignition interpreter was added to V8 with the design goal of reducing the memory usage on small memory Android phones in comparison with TurboFan and Crankshaft.[12] Ignition is a register based machine and shares a similar (albeit not the exact same) design to the templating interpreter utilized by HotSpot.

In 2017, V8 shipped a brand-new compiler pipeline, consisting of Ignition and TurboFan (the optimizing compiler). Starting with V8 version 5.9, Full-codegen (the early baseline compiler) and Crankshaft are no longer used in V8 for JavaScript execution, since the team believed they were no longer able to keep pace with new JavaScript language features and the optimizations those features required.[13]

In 2021, a new tiered compilation pipeline was introduced with the release of the SparkPlug compiler, which supplements the existing TurboFan compiler within V8, in a direct parallel to the profiling C1 Compiler used by HotSpot.

In 2023, the Maglev SSA-based compiler was added, which is 10 times slower than Sparkplug but 10 times faster than TurboFan, bridging the gap between Sparkplug and TurboFan for less frequently run loops that do not get "hot" enough to be optimised by TurboFan, as is the case for most web applications that spend more time interacting with the browser than in JavaScript execution.[14]

Design

[edit]

V8 first generates an abstract syntax tree with its own parser.[15] Then, Ignition generates bytecode from this syntax tree using the internal V8 bytecode format.[16] TurboFan compiles this bytecode into machine code. In other words, V8 compiles ECMAScript to native machine code using just-in-time compilation before executing it.[17] The compiled code is additionally optimized (and re-optimized) dynamically at runtime, based on heuristics of the code's execution profile. Optimization techniques used include inlining, elision of expensive runtime properties, and inline caching. The garbage collector is a generational incremental collector.[18]

Usage

[edit]

V8 can compile to x86, ARM or MIPS instruction set architectures in both their 32-bit and 64-bit editions; it has additionally been ported to PowerPC,[19][20] and to IBM ESA/390 and z/Architecture,[21][19] for use in servers.[22]

V8 can be used in a browser or integrated into independent projects. V8 is used in the following software:

See also

[edit]

References

[edit]
  1. ^ a b c d "Documentation". V8.dev. Google. Retrieved 3 March 2024.
  2. ^ "Chrome Platform Status". Retrieved 29 June 2023.
  3. ^ "v8/LICENSE.v8 at master". Github.
  4. ^ "V8: an open source JavaScript engine". YouTube. Google. 15 September 2008. Retrieved 15 March 2024.
  5. ^ "Big browser comparison test: Internet Explorer vs. Firefox, Opera, Safari and Chrome". PC Games Hardware. Computec Media AG. 3 July 2009. Archived from the original on 2 May 2012. Retrieved 28 June 2010.
  6. ^ Purdy, Kevin (11 June 2009). "Lifehacker Speed Tests: Safari 4, Chrome 2". Lifehacker. Archived from the original on 14 April 2021. Retrieved 8 May 2021.
  7. ^ "Mozilla asks, 'Are we fast yet?'". Wired. Archived from the original on 22 June 2018. Retrieved 18 January 2019.
  8. ^ "V8 JavaScript Engine: License". Google Code. Archived from the original on 22 July 2010. Retrieved 17 August 2010.
  9. ^ "A New Crankshaft for V8". Chromium Blog. 7 December 2010. Retrieved 22 April 2011.
  10. ^ "Revving up JavaScript performance with TurboFan". 7 July 2015. Retrieved 5 March 2016.
  11. ^ "Experimental support for WebAssembly in V8". V8.dev. Retrieved 12 March 2024.
  12. ^ "BlinkOn 6 Day 1 Talk 2: Ignition – An Interpreter for V8". 26 June 2016. Archived from the original on 21 December 2021. Retrieved 2 September 2016 – via YouTube.
  13. ^ "Launching Ignition and TurboFan". 16 May 2017. Retrieved 13 July 2017.
  14. ^ "Maglev - V8's Fastest Optimizing JIT". V8.dev. 5 December 2023. Retrieved 26 January 2024.
  15. ^ Verwaest, Toon (25 March 2019). "Blazingly fast parsing, part 1: optimizing the scanner". V8.dev. Archived from the original on 21 April 2021. Retrieved 1 June 2021.
  16. ^ Hinkelmann, Franziska (19 December 2017). "Understanding V8's Bytecode". Medium. Retrieved 17 October 2019.
  17. ^ "Firing Up the Ignition interpreter". V8.dev. Retrieved 30 September 2020.
  18. ^ "A game changer for interactive performance". Blog.Chromium.org. 21 November 2011. Retrieved 6 February 2022.
  19. ^ a b "PPC support for Google V8 goes mainstream". 30 June 2015. Archived from the original on 12 September 2015.
  20. ^ "GitHub - ibmruntimes/v8ppc: Port of Google V8 javascript engine to PowerPC". 21 April 2019 – via GitHub.
  21. ^ "Port of Google V8 JavaScript engine to z/OS. The Linux on Z port is maintained in the community: ibmruntimes/v8z". 2 April 2019 – via GitHub.
  22. ^ "V8 Changelog v3.8.2". Archived from the original on 22 October 2012. Retrieved 23 October 2012.
  23. ^ "V8 Runtime Overview | Apps Script". Google for Developers. Retrieved 26 January 2025.
  24. ^ "A secure JavaScript/TypeScript runtime built with V8, Rust, and Tokio: denoland/deno". 8 July 2019 – via GitHub.
  25. ^ "Overview - NativeScript Docs". docs.nativescript.org. Archived from the original on 28 July 2020. Retrieved 8 July 2019.
  26. ^ O'Dell, Jolie (10 March 2011). "Why Everyone Is Talking About Node". Mashable.
[edit]

Source: Wikipedia. Article content is retrieved live through the MediaWiki API.

No preview image
Wikipedia

V8 (JavaScript engine)

V8 is a JavaScript and WebAssembly engine developed by Google for its Chrome browser. V8 is free and open-source software (FOSS) and part of the Chromium project. It is also used in non-browser contexts, notably including the Node.js runtime system. Other server-side JavaScript runtimes use alternative engines, such as Bun (which uses JavaScriptCore) and Hermes (used by React Native).

MORE →
No preview image
Wikipedia

V8 engine (disambiguation)

A V8 engine is an engine with eight cylinders mounted on the crankcase in two banks of four cylinders. V8 engine may also refer to: V8 (JavaScript engine), the JavaScript compiler used by Google Chrome

MORE →
No preview image
Wikipedia

Sputnik (JavaScript conformance test)

Sputnik was a JavaScript conformance test suite. The purpose of the test suite was to determine how well a JavaScript implementation adheres to the ECMA-262 specification, 5th edition, looking only at those features that were also present in the 3rd edition. It contained over 5000 tests that touched all aspects of the JavaScript language. The test was created in Russia for testing the conformance of the V8 JavaScript engine used in Google Chrome. As part of phasing out Google Labs, Google has shut down Sputnik. All current Sputnik tests have been incorporated into ECMA's Test262 test suite.

MORE →
Wikipedia

Node.js

Node.js is a cross-platform, open-source JavaScript runtime environment that can run on Windows, Linux, Unix, macOS, and more. Node.js runs on the V8 JavaScript engine, and executes JavaScript code outside a web browser. According to the Stack Overflow Developer Survey, Node.js is one of the most commonly used web technologies. Node.js allows developers to use JavaScript for writing command line tools and server-side scripting. Running Javascript on the server is commonly used to generate dynamic web page content before the page is sent to the user's web browser. Consequently, Node.js represents a "JavaScript everywhere" paradigm, unifying web-application development around a single programming language, as opposed to using different languages for the server- versus client-side programming. Node.js has an event-driven architecture capable of asynchronous I/O. These design choices aim to optimize throughput and scalability in web applications with many input/output operations, as well as for real-time Web applications (e.g., real-time communication programs and browser games). The Node.js distributed development project was previously governed by the Node.js Foundation, and has now merged with the JS Foundation to form the OpenJS Foundation. OpenJS Foundation is facilitated by the Linux Foundation's Collaborative Projects program.

MORE →
TOPIC OF THE DAY

Greenwood / Black Wall Street

Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.

MORE →
TRIVIA QUESTION OF THE DAY

What prosperous Tulsa district became widely known as “Black Wall Street”?

The Greenwood District.