Hero Background

Confronting notebooks

June 15, 2025

Confronting kaggle notebook with observablehq notebook for a visualization task

  • JupyterJupyter
  • PythonPython
  • JavascriptJavascript
JupyterPythonJavascript

Kaggle notebook

Long Image

ObservableHQ notebook

Long Image
NotebookMain useFor
Kaggle (Jupyter Notebooks)Data science, machine learning, competitionsData scientists, ML engineers
ObservableHQData visualization, interactive documentsData journalists, analysts, visualization experts

Differences

DifferencesKaggle (Jupyter Notebooks)ObservableHQ
Environment LanguagePythonJavaScript (with D3.js, Observable Plot, etc.)
Runtime LocationRuns in a Python environment (cloud backend)Runs directly in modern web browsers
PerformanceSupports heavy computation, including GPU/TPUNot suitable for large-scale computation
ScalabilityCan handle large datasets efficientlyBest for small, in-browser datasets
InteractivityManual execution needed for updatesReal-time, reactive updates with UI interactions

Calories Prediction datasets

A Kaggle dataset used in a competition is explored using two popular and comparable notebook environments: Kaggle Jupyter Notebooks and ObservableHQ Notebooks. Two version of Exploratory data analysis(EDA) is done using the two platforms.

Result

ObservableHQ with the ease of use of Plot command and its reactive programming model allow to quickly create visual charts with interactivity and where updates are instantly reflected. Kaggle notebook, in contrast, can create fast charts using libraries like seaborn but customizing visuals tends to be more verbose and requires deeper familiarity with syntax. While observable notebook is designed for machine learning, it is a good alternative for going from Exploratory Data Analysis to the Presentation, it's browser enviroment allow visual rapresentation that can prove a point much quicker thanks to visual storytelling and interactivity. The point of creating a good visual representation is not also oriented to the data but for the team you are working or the client that you have to provide some documentation about it. It is also possible to combine the workflow from one notebook to the another for example when you made an analysis using kaggle notebook you can create a visualization of that result using observablehq and d3 creating more unique visualization not necessary more complex but more visual appealing to the user.