frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Tiny C Compiler

https://bellard.org/tcc/
109•guerrilla•3h ago•46 comments

SectorC: A C Compiler in 512 bytes

https://xorvoid.com/sectorc.html
191•valyala•7h ago•36 comments

Speed up responses with fast mode

https://code.claude.com/docs/en/fast-mode
114•surprisetalk•7h ago•117 comments

Brookhaven Lab's RHIC concludes 25-year run with final collisions

https://www.hpcwire.com/off-the-wire/brookhaven-labs-rhic-concludes-25-year-run-with-final-collis...
44•gnufx•6h ago•45 comments

Software factories and the agentic moment

https://factory.strongdm.ai/
134•mellosouls•10h ago•282 comments

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
880•klaussilveira•1d ago•270 comments

Stories from 25 Years of Software Development

https://susam.net/twenty-five-years-of-computing.html
132•vinhnx•10h ago•15 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
166•AlexeyBrin•13h ago•29 comments

FDA intends to take action against non-FDA-approved GLP-1 drugs

https://www.fda.gov/news-events/press-announcements/fda-intends-take-action-against-non-fda-appro...
63•randycupertino•3h ago•96 comments

First Proof

https://arxiv.org/abs/2602.05192
98•samasblack•10h ago•65 comments

I write games in C (yes, C) (2016)

https://jonathanwhiting.com/writing/blog/games_in_c/
173•valyala•7h ago•154 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
269•jesperordrup•17h ago•86 comments

Al Lowe on model trains, funny deaths and working with Disney

https://spillhistorie.no/2026/02/06/interview-with-sierra-veteran-al-lowe/
85•thelok•9h ago•18 comments

The F Word

http://muratbuffalo.blogspot.com/2026/02/friction.html
97•zdw•3d ago•49 comments

Eigen: Building a Workspace

https://reindernijhoff.net/2025/10/eigen-building-a-workspace/
4•todsacerdoti•4d ago•1 comments

Show HN: A luma dependent chroma compression algorithm (image compression)

https://www.bitsnbites.eu/a-spatial-domain-variable-block-size-luma-dependent-chroma-compression-...
28•mbitsnbites•3d ago•2 comments

Show HN: I saw this cool navigation reveal, so I made a simple HTML+CSS version

https://github.com/Momciloo/fun-with-clip-path
53•momciloo•7h ago•10 comments

Start all of your commands with a comma (2009)

https://rhodesmill.org/brandon/2009/commands-with-comma/
550•theblazehen•3d ago•204 comments

Microsoft account bugs locked me out of Notepad – Are thin clients ruining PCs?

https://www.windowscentral.com/microsoft/windows-11/windows-locked-me-out-of-notepad-is-the-thin-...
86•josephcsible•5h ago•109 comments

Selection rather than prediction

https://voratiq.com/blog/selection-rather-than-prediction/
25•languid-photic•4d ago•7 comments

The AI boom is causing shortages everywhere else

https://www.washingtonpost.com/technology/2026/02/07/ai-spending-economy-shortages/
252•1vuio0pswjnm7•14h ago•395 comments

Reinforcement Learning from Human Feedback

https://rlhfbook.com/
112•onurkanbkrc•12h ago•5 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

https://arcadeblogger.com/2026/02/02/unseen-footage-of-atari-battlezone-cabinet-production/
138•videotopia•4d ago•46 comments

A Fresh Look at IBM 3270 Information Display System

https://www.rs-online.com/designspark/a-fresh-look-at-ibm-3270-information-display-system
58•rbanffy•4d ago•18 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
216•limoce•4d ago•123 comments

Where did all the starships go?

https://www.datawrapper.de/blog/science-fiction-decline
125•speckx•4d ago•188 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
294•isitcontent•1d ago•39 comments

Coding agents have replaced every framework I used

https://blog.alaindichiappari.dev/p/software-engineering-is-back
305•alainrk•12h ago•491 comments

The silent death of Good Code

https://amit.prasad.me/blog/rip-good-code
56•amitprasad•2h ago•62 comments

72M Points of Interest

https://tech.marksblogg.com/overture-places-pois.html
48•marklit•5d ago•9 comments
Open in hackernews

Myna: monospace typeface designed for symbol-rich programming

https://github.com/sayyadirfanali/Myna
52•vinhnx•3mo ago

Comments

unwind•2mo ago
Repost, see https://news.ycombinator.com/item?id=45849342.
vinhnx•2mo ago
Strangely, I submitted this a week ago, even before the linked HN you mentioned. Now it turns to the front page, maybe the HN algo bumps it.
tyleo•2mo ago
Weird. I thought HN automatically combined submissions with the same URL unless there was like a year or so of space between them.
amoss•2mo ago
The flat shape of the "r" and the lack of curvature on the "p" where it touches the stem would drive me mad, but YMMV.
torstenvl•2mo ago
Font generally looks nice, but I really hate the trend of overly-curly curly braces.

(Also, I'm judging the C code. No check on the fopen()? fclose() on a possibly invalid FILE *? No return from int main()? "FILE *f"?!?!)

sayyadirfanali•2mo ago
thanks for the feedback. a few people have expressed the same criticism. i'm open to producing a variant with less-curly curly brances. please raise an issue, if you want to use it.

as is expected, all codes in the illustrations, especially the C code, are to be judged superficially, ie, by their covers, not content :)

ape4•2mo ago
Might be nice if the ligature of != was ≠
mrweasel•2mo ago
Probably personal preference, but I prefer != not be smashed into one character.
sayyadirfanali•2mo ago
as i mention in the description, Myna doesn't use ligatures. the Unicode sure looks very much like that in the font, though.
zygentoma•2mo ago
Why does the 'l' look different in the title image and in the example images?

I actually like the one in the title image more, because it's less likely to be confused for a 1.

[EDIT:] Also the kerning of l and i in 'lines' looks a bit off …

sayyadirfanali•2mo ago
designer here. thanks for the feedback. i've updated the serif in `l` after an issue raised the possibility of ambiguity with `1`. alas, that would mean i'd need to regenerate all the images, which i haven't done yet.

i didn't produce a variant for the `l` serif, please check issue #8. if you prefer the variant, please open an issue. can you elaborate on the kerning point, preferably there also?