loading words...

May 05, 2019 02:00:02

Forking the Source (code)

by @brianball PATRON | 248 words | 389💌

Brian Ball

Total posts: 389💌
Total words: 107477 (429 pages 📄)

The Chrome browser by Google uses a JavaScript engine called v8 - the idea is that it's fast.


I'm not here to discuss speed or performance of any kind. Rather, I just want to dive in to the source code.


I have one browser window open with 200Wad ( @baz, please redirect it to the main site ) -- and a second window open to the v8 code repository on Github.


Github is a site that allows you to visualize and socialize code. Git - is a version control system. Instead of saving changes to files with different file names, you can use the Git system.


If you're not a coder, it can still be useful.


In the source code main folder, we have 13 subfolders at the root level and 25 files.

The folders organize tooling and testing and samples and libraries and source code.

Some folders are 3rd-party cold libraries.

Some files are mundane things like License agreements.


This is a big project. 2,416 people have forked it. Which means they can copy the whole collection of files and do whatever they want. If they want to contribute changes and offer them back to the main project, they do so by first forking ( copying ) -- then making their changes and finally submitting a request to pull their changes into the main repo.


tl;dr: Github is a website people use to share and socialize software projects -- and other computer file based projects.

Fork - means to make a copy.

Software is composed of many, many files.

From Brian Ball's collections:

contact: email - twitter / Terms / Privacy