Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #478

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,11 @@
[![Join the Gitter Chat](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/QuantStack/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

`xeus-cling` is a Jupyter kernel for C++ based on the C++ interpreter [cling](https://github.com/root-project/cling) and
the native implementation of the Jupyter protocol [xeus](https://github.com/jupyter-xeus/xeus).
the native implementation of the Jupyter protocol [xeus](https://github.com/jupyter-xeus/xeus).

## Comparisons to other alternatives
### [cling](https://github.com/root-project/cling)
clings already comes with a [Jupyter](https://jupyter.org/) support. Cling uses the wrapper kernel approach, which means it depends on [ipykernel](https://github.com/ipython/ipykernel) and thus on the Python runtime. The kernel of `xeus-cling` is based on [xeus](https://github.com/jupyter-xeus/xeus), a native implementation of the Jupyter Kernel protocol. So, No dependency on ipykernel nor any Python part of the Jupyter ecosystem. The xeus based approch has proven to be more stable on the long run.

## Installation

Expand Down