HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
isene
chasm
Shell2026–2026
isene / chasm

chasm

CHasm — CHange to ASM. Pure x86_64 assembly Linux tools (bare, show, glass, tile).

3Distinct people
3Mentions
0Explicit recommenders
108GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

CHasm — CHange to ASM. Pure x86_64 assembly Linux tools (bare, show, glass, tile).

GitHub

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 hour3 dated mentions

Observed mentions: 2026-05-03 16:18:06 UTC to 2026-05-04 09:47:10 UTC.

0122026-05-03 16:00:00 UTC to 2026-05-03 17:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 3, 16:002026-05-03 17:00:00 UTC to 2026-05-03 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-03 18:00:00 UTC to 2026-05-03 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-03 19:00:00 UTC to 2026-05-03 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-03 20:00:00 UTC to 2026-05-03 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-03 21:00:00 UTC to 2026-05-03 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-03 22:00:00 UTC to 2026-05-03 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-03 23:00:00 UTC to 2026-05-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-04 00:00:00 UTC to 2026-05-04 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 4, 00:002026-05-04 01:00:00 UTC to 2026-05-04 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-04 02:00:00 UTC to 2026-05-04 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-04 03:00:00 UTC to 2026-05-04 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-04 04:00:00 UTC to 2026-05-04 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-04 05:00:00 UTC to 2026-05-04 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-04 06:00:00 UTC to 2026-05-04 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-04 07:00:00 UTC to 2026-05-04 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-04 08:00:00 UTC to 2026-05-04 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-04 09:00:00 UTC to 2026-05-04 10:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsMay 4, 09: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
May 3, 16:002026-05-03 16:00:00 UTC2026-05-03 17:00:00 UTC101
May 3, 17:002026-05-03 17:00:00 UTC2026-05-03 18:00:00 UTC000
May 3, 18:002026-05-03 18:00:00 UTC2026-05-03 19:00:00 UTC000
May 3, 19:002026-05-03 19:00:00 UTC2026-05-03 20:00:00 UTC000
May 3, 20:002026-05-03 20:00:00 UTC2026-05-03 21:00:00 UTC000
May 3, 21:002026-05-03 21:00:00 UTC2026-05-03 22:00:00 UTC000
May 3, 22:002026-05-03 22:00:00 UTC2026-05-03 23:00:00 UTC000
May 3, 23:002026-05-03 23:00:00 UTC2026-05-04 00:00:00 UTC000
May 4, 00:002026-05-04 00:00:00 UTC2026-05-04 01:00:00 UTC000
May 4, 01:002026-05-04 01:00:00 UTC2026-05-04 02:00:00 UTC000
May 4, 02:002026-05-04 02:00:00 UTC2026-05-04 03:00:00 UTC000
May 4, 03:002026-05-04 03:00:00 UTC2026-05-04 04:00:00 UTC000
May 4, 04:002026-05-04 04:00:00 UTC2026-05-04 05:00:00 UTC000
May 4, 05:002026-05-04 05:00:00 UTC2026-05-04 06:00:00 UTC000
May 4, 06:002026-05-04 06:00:00 UTC2026-05-04 07:00:00 UTC000
May 4, 07:002026-05-04 07:00:00 UTC2026-05-04 08:00:00 UTC000
May 4, 08:002026-05-04 08:00:00 UTC2026-05-04 09:00:00 UTC000
May 4, 09:002026-05-04 09:00:00 UTC2026-05-04 10:00:00 UTC202

What Hacker News says

3 sources
CHasm[0] is a bit of a joke, right? Did it take a lot of Claude massaging to get it to ignore basic engineering knowledge, like that compilers write better assembly than any other tool or person will (in the general case, which this is)? This kind of summarizes the whole post for me. I struggle to see how, on a platform that I thought was passionate about engineering, this is gaining any kind of traction. Writing GUI tools in assembly, not to learn, but for whatever other reasons, is nightmarish levels of silly. I get the idea of making software TRULY yours. I get it. This isn't that. Letting an AI agent literally vibe code your entire desktop is not an idea that would come to anyone's mind as more than the punchline of a joke or a side note in a dystopian book. You're not making software, Claude is. You're not learning anything, and the
Read the rest
tools produced are (by design) not really editable. 0: https://github.com/isene/chasm
In A desktop made for one

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.