HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
microsoft
ambrosia
HISTORICAL RECORD2018–2019
microsoft / ambrosia · Not publicly available

ambrosia

Discover this repository through its Hacker News conversations.

3Distinct people
4Mentions
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 week4 dated mentions

Observed mentions: 2018-12-07 14:59:43 UTC to 2019-04-17 20:49:29 UTC. Weeks start Monday, UTC.

0122018-12-03 00:00:00 UTC to 2018-12-10 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsDec 32018-12-10 00:00:00 UTC to 2018-12-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-12-17 00:00:00 UTC to 2018-12-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-12-24 00:00:00 UTC to 2018-12-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-12-31 00:00:00 UTC to 2019-01-07 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-07 00:00:00 UTC to 2019-01-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-14 00:00:00 UTC to 2019-01-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-21 00:00:00 UTC to 2019-01-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-28 00:00:00 UTC to 2019-02-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-02-04 00:00:00 UTC to 2019-02-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 42019-02-11 00:00:00 UTC to 2019-02-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-02-18 00:00:00 UTC to 2019-02-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-02-25 00:00:00 UTC to 2019-03-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-04 00:00:00 UTC to 2019-03-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-11 00:00:00 UTC to 2019-03-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-18 00:00:00 UTC to 2019-03-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-25 00:00:00 UTC to 2019-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-01 00:00:00 UTC to 2019-04-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-08 00:00:00 UTC to 2019-04-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-04-15 00:00:00 UTC to 2019-04-22 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 15

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
Dec 32018-12-03 00:00:00 UTC2018-12-10 00:00:00 UTC211
Dec 102018-12-10 00:00:00 UTC2018-12-17 00:00:00 UTC000
Dec 172018-12-17 00:00:00 UTC2018-12-24 00:00:00 UTC000
Dec 242018-12-24 00:00:00 UTC2018-12-31 00:00:00 UTC000
Dec 312018-12-31 00:00:00 UTC2019-01-07 00:00:00 UTC101
Jan 72019-01-07 00:00:00 UTC2019-01-14 00:00:00 UTC000
Jan 142019-01-14 00:00:00 UTC2019-01-21 00:00:00 UTC000
Jan 212019-01-21 00:00:00 UTC2019-01-28 00:00:00 UTC000
Jan 282019-01-28 00:00:00 UTC2019-02-04 00:00:00 UTC000
Feb 42019-02-04 00:00:00 UTC2019-02-11 00:00:00 UTC000
Feb 112019-02-11 00:00:00 UTC2019-02-18 00:00:00 UTC000
Feb 182019-02-18 00:00:00 UTC2019-02-25 00:00:00 UTC000
Feb 252019-02-25 00:00:00 UTC2019-03-04 00:00:00 UTC000
Mar 42019-03-04 00:00:00 UTC2019-03-11 00:00:00 UTC000
Mar 112019-03-11 00:00:00 UTC2019-03-18 00:00:00 UTC000
Mar 182019-03-18 00:00:00 UTC2019-03-25 00:00:00 UTC000
Mar 252019-03-25 00:00:00 UTC2019-04-01 00:00:00 UTC000
Apr 12019-04-01 00:00:00 UTC2019-04-08 00:00:00 UTC000
Apr 82019-04-08 00:00:00 UTC2019-04-15 00:00:00 UTC000
Apr 152019-04-15 00:00:00 UTC2019-04-22 00:00:00 UTC101

What Hacker News says

4 sources
Great question. We take a very maximalist stance here and do not provide any environmental API’s in the Bosque language. Instead all IO, data-time, IP address operations must be part of a host platform – similar to how JavaScript does not provide IO or an event loop in the spec but relies on the browser or Node.js to provide it. With this model the host can just log/record the environment interactions. The details of this host and integration are an open issue, both research and engineering, but I am very excited by the AMBROSIA architecture (https://github.com/Microsoft/AMBROSIA) by one of my colleagues as a possible design.
In Bosque Programming Language

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.