Code Monkey home page Code Monkey logo

sbshah97 / hello-world Goto Github PK

View Code? Open in Web Editor NEW
46.0 4.0 70.0 321 KB

Hello-World! The baby steps to be a Programmer! Explore this repository to check out various languages in Computer Science and understand how to contribute to Open Source effectively and easily. Sending your first Pull Request is not hard and made easier by this repository!

License: MIT License

Java 8.17% C 0.31% C++ 0.46% Python 83.32% Ruby 0.09% C# 1.18% HTML 1.42% M 1.10% JavaScript 0.25% Scala 0.45% Shell 0.53% Groovy 0.55% PHP 0.16% Go 0.38% Haskell 0.15% Pascal 0.26% Boo 0.11% Fortran 0.13% Perl 0.35% NewLisp 0.62%
open-source starter-project c languages android arnoldc assembly b bash boo

hello-world's Introduction

hello-world

This project shows you how to write the legendary fundamental "hello-world" in all languages that you can think of.

Prerequisites and usage

For each hello-world download that language's compiler and run the file.

Structure

The hello-world code for each language is in its own directory. This directory also contains a specific README.md with instructions on how to run the code.

Running projects via Docker:

Running the container

  • Make sure you have docker.io installed on your system by running docker -v, which should log the current version of docker installed.
  • Run docker run -v $(pwd):/home/docker -w /home/docker -it --rm <image_name> /bin/bash to run an interactive container.
  • Compile and run your desired program

Docker hello-world:

  • After installing Docker, simply run docker run hello-world.
  • This should create a container which displays a hello-world message.

Finding your desired image:

  • Goto the docker hub.
  • Search for the language/environment you want to run.
  • Choose any image in the list.
  • Run the command mentioned above by replacing the <image_name> with the corresponding image.

Contributing

  • I am always looking for more contributions.
  • If you're wondering how to contribute do check out Contributing

License

hello-world's People

Contributors

aditya5558 avatar arfatbk avatar ativerc avatar balachandarsv avatar brandonbilbrey avatar dariotecchia avatar dinika avatar divayprakash avatar dumptyd avatar duxy1996 avatar erikweibust avatar fadc80 avatar grrttedwards avatar haugenmitch avatar hrily avatar ivanovyordan avatar jbmiles avatar kameramann23 avatar mj10 avatar monst12 avatar oanarosca avatar pvgupta24 avatar raymondboswel avatar sbshah97 avatar seancyw avatar sumeshpremraj avatar thenickcox avatar tony133 avatar trqx avatar valkheim avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

hello-world's Issues

Edit Readme

Modify the readme to reflect the new directory structure

Fortran 90 - Add README for MacOS and Windows

Go to the folder for Fortran 90 where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to edit the README for the same and make sure it covers all instructions on how to set up Fortran 90 Dev Environment in Windows and MacOS.

If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Create folder for 'Hello World' R Programming Language and create README

Create a folder for R where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (the file should be named hello-world.r ) and a README file which tells you how to run the particular file in that language.
The README should also contain steps to install that language on various OSs like Mac, Linux and Windows. If you don't know any of these steps, kindly create another Issue so that someone else can add the details.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Piet - Add Installation instructions for Piet on Windows, Linux and MacOS

Go to the folder for Piet where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to edit the README for the same and make sure it covers all instructions on how to set up Piet Dev Environment on Windows, Linux and MacOS and how to run the same as well.

  • Windows
  • Linux
  • Mac

If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Include Frameworks

There are a lot of frameworks, like AngularJS, React, Django, etc which could be added.

Update README to standard format

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Check out this link to understand better.

Add Instruction how to run Android and set it up

Go to the folder for Android where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to create a README for the same and make sure it covers all instructions on how to set up Android Dev Environment.

The README should also contain steps to install that language on various OSs like Mac, Linux and Windows. If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

PHP - Add Instructions to install and run PHP in Linux and MacOS

Go to the folder for PHP where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to edit the README for the same and make sure it covers all instructions on how to set up PHP Dev Environment on Linux and MacOS and how to run the same as well.

If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Add Clojure

I have a PR ready for Clojure that I'll add tomorrow at the start of Hacktoberfest, but I wanted to claim it just in case!

Create folder for 'Hello World' in Haskell and add README

Create a folder for Haskell where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (the file should be named hello-world.hs ) and a README file which tells you how to run the particular file in that language.
The README should also contain steps to install that language on various OSs like Mac, Linux and Windows. If you don't know any of these steps, kindly create another Issue so that someone else can add the details.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Dart - Edit README to add Windows and MacOS

Go to the folder for Dart where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to edit the README for the same and make sure it covers all instructions on how to set up Dart Dev Environment and how to run the code on Windows and MacOS.

If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Standardize format for title.

Almost every different example has a different variation on hello-world as the title. Should have a standard name. Im suggesting hello-world to stick with the name of the repo.

Add CONTRIBUTING.MD

Add a CONTRIBUTING.md file. Take a look at the various formats put up by various repositories online. A simple Google Search will suffice for this.
This is a First-Timers-Issue only. Make sure you understand the correct process of making a Pull Request

Create folder for 'Hello World' in C# and add README

Create a folder for C# where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (the file should be named hello-world.cs ) and a README file which tells you how to run the particular file in that language.
The README should also contain steps to install that language on various OSs like Mac, Linux and Windows. If you don't know any of these steps, kindly create another Issue so that someone else can add the details.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Create folder for 'Hello World' in Boo and add README to it!

Create a folder for Boo where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (the file should be named hello-world.boo ) and a README file which tells you how to run the particular file in that language.
The README should also contain steps to install that language on various OSs like Mac, Linux and Windows. If you don't know any of these steps, kindly create another Issue so that someone else can add the details.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Add code for M# Hello World

Go to the folder for M# where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file.

Your task is to edit the heloworld.m file and add code for the same there. If possible edit the README as well for more precise instructions on how to contribute to the repository.

If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

MIPS - Add instructions for MacOS

Go to the folder for MIPS where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to edit the README for the same and make sure it covers all instructions on how to set up MIPS Dev Environment on MacOS.

If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Add Crystal

Add hello world for the Crystal programming language

Standard format for all the Hello World files

Create a folder for each language where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (the file should be named hello-world.c or any other language that is there) and a README file which tells you how to run the particular file in that language.
The README should also contain steps to install that language on various OSs like Mac, Linux and Windows. If you don't know any of these steps, kindly create another Issue so that someone else can add the details.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

In the comments below kindly claim only for one language. After you're done with one language and have sent me a Pull Request regarding the same, you can move to another language.

Best of luck. Let the Hacktoberfest begin!!

C++ - Edit README for Windows

Go to the folder for C++ where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to edit the README for the same and make sure it covers all instructions on how to set up C++ Dev Environment on Windows and Mac.

If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Erlang - Add Windows and MacOS Documentation

Go to the folder for Erlang where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to edit the README for the same and make sure it covers all instructions on how to set up Erlang Dev Environment on Windows and MacOS and try to send a Pull Request with the same!

If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Create folder for 'Hello World' in Groovy Language and add README

Create a folder for Groovy where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (the file should be named hello-world.groovy ) and a README file which tells you how to run the particular file in that language.
The README should also contain steps to install that language on various OSs like Mac, Linux and Windows. If you don't know any of these steps, kindly create another Issue so that someone else can add the details.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Create folder for 'Hello World' in M# Programming Language and create README

Create a folder for M# where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (the file should be named hello-world.m ) and a README file which tells you how to run the particular file in that language.
The README should also contain steps to install that language on various OSs like Mac, Linux and Windows. If you don't know any of these steps, kindly create another Issue so that someone else can add the details.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

F# - Add README for Linux and MacOS

Go to the folder for F# where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to edit the README for the same and make sure it covers all instructions on how to set up F# Dev Environment in Linux and MacOS.

If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

hello world in go

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add Hello World in golang.

Add Documentation for Ezhil

Go to the folder for Ezhil where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to create the README for the same and make sure it covers all instructions on how to set up Ezhil Dev Environment in Windows, Linux and MacOS. Kindly refer the other README for a suitable template.

If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Create folder for 'Hello World' in Visual Basic and add README

Create a folder for Visual Basic where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (the file should be named hello-world.vb ) and a README file which tells you how to run the particular file in that language.
The README should also contain steps to install that language on various OSs like Mac, Linux and Windows. If you don't know any of these steps, kindly create another Issue so that someone else can add the details.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Update README for ASSEMBLY Language

Go to the folder for Assembly where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to create a README for the same and make sure it covers all instructions on how to set up Assembly Environment.

The README should also contain steps to install that language on various OSs like Mac, Linux and Windows. If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Scala - Add instructions to run Scala on Linux and MacOS

Go to the folder for Scala where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to edit the README for the same and make sure it covers all instructions on how to set up Scala Dev Environment on Linux and MacOS.

  • Linux
  • MacOS

If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Scala - README.md formatting could use cleaning up

In the Scala README.md the Mac subsection has some crazy formatting. In addition, some of the markdown is inconsistent, i.e. some inline code(` `), some code blocks(``` ```) and some 4-space indented code.

Add Idris

I also have a PR ready for Idris to open when Hacktoberfest opens tomorrow. I just wanted to claim Idris in case anyone else was thinking about it!

Julia - Edit README for adding instructions to run Julia in Windows and MacOS

Go to the folder for Julia where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to edit the README for the same and make sure it covers all instructions on how to set up Julia Dev Environment for Windows and MacOS.

If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

C# - Add Instructions for compiling in Linux and Mac systems

Go to the folder for C# where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (there will be quite a few files there).

Your task is to edit the README for the same and make sure it covers all instructions on how to set up C# Dev Environment. For more resources, you can check them out here

If you don't know any of these steps, kindly ping back in the comments so that I can help you out.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Create folder for 'Hello World' in Fortran 90 and add README to it.

Create a folder for Fortran 90 where the name of the folder should be the name of the language itself. Inside the folder should be the Hello World! code of the file (the file should be named hello-world.f90 ) and a README file which tells you how to run the particular file in that language.
The README should also contain steps to install that language on various OSs like Mac, Linux and Windows. If you don't know any of these steps, kindly create another Issue so that someone else can add the details.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Best of luck. Let the Hacktoberfest begin!!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.