esnet / esnet/pond

Successor: pond-ts (TypeScript rewrite by the original author)

Open
#297 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
211
Forks
42
PR merge metrics
No merged PRs in 30d

Description

Hello,

I wrote Pond.js while I was at ESnet, and I'm opening this so anyone who lands here has a pointer to where the work went.

Pond.js hasn't had a release since 0.9.0 (November 2019).

The successor is [pond-ts](https://github.com/pond-ts/pond) — a from-scratch TypeScript rewrite of the same ideas (typed time series, temporal keys, event collections, aggregation and rolling pipelines), plus a lot of things Pond.js never built: a dedicated streaming LiveSeries with the same operator vocabulary, per-entity partitioning, bounded-memory retention, typed columnar storage, arrow support, and a React canvas charting package (@pond-ts/charts) that succeeds react-timeseries-charts.

npm: **pond-ts**
docs: https://pond-ts.org/
benchmarks: faster that pondjs on all 54 shared tested operations, mean improvement was about 20×): https://pond-ts.org/docs/reference/benchmarks

It is pre-1.0 and API-stable-ish, MIT, and actively maintained.

It is not an ESnet project and I'm not speaking for ESnet. This is the original author pointing at the continuation.

Ask for the maintainers: a one-paragraph note at the top of the README (I'll open a PR with exactly that), and/or marking this repository archived with the pointer in the description. Happy to help anyone migrating; issues on the pond-ts repo are the right place.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the repository README and description, using the pond-ts link and migration context in this issue. Done means adding a brief successor pointer to the README and, if chosen, marking the repository archived with the same pointer; no tests are mentioned.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.