HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
swimos
swim-rust
HISTORICAL RECORD2024–2024
swimos / swim-rust · Not publicly available

swim-rust

Discover this repository through its Hacker News conversations.

2Distinct people
3Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval3 dated mentions

Observed mentions: 2024-07-23 12:22:02 UTC to 2024-07-28 19:21:54 UTC.

0122024-07-23 12:00:00 UTC to 2024-07-23 18:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsJul 23, 12:002024-07-23 18:00:00 UTC to 2024-07-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-24 00:00:00 UTC to 2024-07-24 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-24 06:00:00 UTC to 2024-07-24 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-24 12:00:00 UTC to 2024-07-24 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-24 18:00:00 UTC to 2024-07-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-25 00:00:00 UTC to 2024-07-25 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-25 06:00:00 UTC to 2024-07-25 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-25 12:00:00 UTC to 2024-07-25 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-25 18:00:00 UTC to 2024-07-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-26 00:00:00 UTC to 2024-07-26 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 26, 00:002024-07-26 06:00:00 UTC to 2024-07-26 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-26 12:00:00 UTC to 2024-07-26 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-26 18:00:00 UTC to 2024-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-27 00:00:00 UTC to 2024-07-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-27 06:00:00 UTC to 2024-07-27 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-27 12:00:00 UTC to 2024-07-27 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-27 18:00:00 UTC to 2024-07-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-28 00:00:00 UTC to 2024-07-28 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-28 06:00:00 UTC to 2024-07-28 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-28 12:00:00 UTC to 2024-07-28 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-28 18:00:00 UTC to 2024-07-29 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 28, 18:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 23, 12:002024-07-23 12:00:00 UTC2024-07-23 18:00:00 UTC211
Jul 23, 18:002024-07-23 18:00:00 UTC2024-07-24 00:00:00 UTC000
Jul 24, 00:002024-07-24 00:00:00 UTC2024-07-24 06:00:00 UTC000
Jul 24, 06:002024-07-24 06:00:00 UTC2024-07-24 12:00:00 UTC000
Jul 24, 12:002024-07-24 12:00:00 UTC2024-07-24 18:00:00 UTC000
Jul 24, 18:002024-07-24 18:00:00 UTC2024-07-25 00:00:00 UTC000
Jul 25, 00:002024-07-25 00:00:00 UTC2024-07-25 06:00:00 UTC000
Jul 25, 06:002024-07-25 06:00:00 UTC2024-07-25 12:00:00 UTC000
Jul 25, 12:002024-07-25 12:00:00 UTC2024-07-25 18:00:00 UTC000
Jul 25, 18:002024-07-25 18:00:00 UTC2024-07-26 00:00:00 UTC000
Jul 26, 00:002024-07-26 00:00:00 UTC2024-07-26 06:00:00 UTC000
Jul 26, 06:002024-07-26 06:00:00 UTC2024-07-26 12:00:00 UTC000
Jul 26, 12:002024-07-26 12:00:00 UTC2024-07-26 18:00:00 UTC000
Jul 26, 18:002024-07-26 18:00:00 UTC2024-07-27 00:00:00 UTC000
Jul 27, 00:002024-07-27 00:00:00 UTC2024-07-27 06:00:00 UTC000
Jul 27, 06:002024-07-27 06:00:00 UTC2024-07-27 12:00:00 UTC000
Jul 27, 12:002024-07-27 12:00:00 UTC2024-07-27 18:00:00 UTC000
Jul 27, 18:002024-07-27 18:00:00 UTC2024-07-28 00:00:00 UTC000
Jul 28, 00:002024-07-28 00:00:00 UTC2024-07-28 06:00:00 UTC000
Jul 28, 06:002024-07-28 06:00:00 UTC2024-07-28 12:00:00 UTC000
Jul 28, 12:002024-07-28 12:00:00 UTC2024-07-28 18:00:00 UTC000
Jul 28, 18:002024-07-28 18:00:00 UTC2024-07-29 00:00:00 UTC101

What Hacker News says

3 sources
The Swim Rust SDK contains software framework for building stateful applications that can be interacted with via multiplexed streaming APIs. It is built on top of the Tokio asynchronous runtime and a Tokio runtime is required for any Swim application. Each application consists of some number of stateful agents, each of which runs as a separate Tokio task and can be individually addressed by a URI. An agent may have both public and private state which can either be held solely in memory or, optionally, in persistent storage. The public state of the agent consists of a number of lanes, analogous to a field in a record. There are multiple kinds of lanes that, for example, lanes containing single values and those containing a map of key-value pairs. The state of any lane can be observed by establishing a link to it (either from another agent
Read the rest
instance or a dedicated client). A established link will push all updates to the state of that lane to the subscriber and will also allow the subscriber to request changes to the state (for lane kinds that support this). Links operate over a web-socket connection and are multiplexed, meaning that links to multiple lanes on the same host can share a single web-socket connection. There's a number of example applications available here: https://github.com/swimos/swim-rust/tree/main/example_apps If you're interested in getting started with it a developer guide is available here https://www.swimos.org/server/rust/developer-guide/ as well as reference documentation here https://www.swimos.org/server/rust/ Previously on HN: - SwimOS: Distributed platform for building stateful, real-time streaming apps https://news.ycombinator.com/item?id=22920764 - Real-time traffic light status in Palo Alto powered by swim.ai https://news.ycombinator.com/item?id=19234286
In Show HN: SwimOS Rust – A framework for real-time streaming data applications

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.