frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

SectorC: A C Compiler in 512 bytes

https://xorvoid.com/sectorc.html
112•valyala•4h ago•18 comments

The F Word

http://muratbuffalo.blogspot.com/2026/02/friction.html
49•zdw•3d ago•15 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...
28•gnufx•3h ago•20 comments

Speed up responses with fast mode

https://code.claude.com/docs/en/fast-mode
59•surprisetalk•4h ago•66 comments

Software factories and the agentic moment

https://factory.strongdm.ai/
103•mellosouls•7h ago•183 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
146•AlexeyBrin•9h ago•26 comments

Stories from 25 Years of Software Development

https://susam.net/twenty-five-years-of-computing.html
103•vinhnx•7h ago•13 comments

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

https://openciv3.org/
854•klaussilveira•1d ago•261 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
1096•xnx•1d ago•618 comments

First Proof

https://arxiv.org/abs/2602.05192
70•samasblack•6h ago•51 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-...
9•mbitsnbites•3d ago•0 comments

Italy Railways Sabotaged

https://www.bbc.co.uk/news/articles/czr4rx04xjpo
13•vedantnair•34m ago•4 comments

I write games in C (yes, C)

https://jonathanwhiting.com/writing/blog/games_in_c/
141•valyala•4h ago•117 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
240•jesperordrup•14h ago•81 comments

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

https://spillhistorie.no/2026/02/06/interview-with-sierra-veteran-al-lowe/
64•thelok•6h ago•11 comments

Start all of your commands with a comma (2009)

https://rhodesmill.org/brandon/2009/commands-with-comma/
521•theblazehen•3d ago•192 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
34•momciloo•4h ago•5 comments

Reinforcement Learning from Human Feedback

https://rlhfbook.com/
95•onurkanbkrc•9h ago•5 comments

Selection Rather Than Prediction

https://voratiq.com/blog/selection-rather-than-prediction/
14•languid-photic•3d ago•5 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
51•rbanffy•4d ago•10 comments

The AI boom is causing shortages everywhere else

https://www.washingtonpost.com/technology/2026/02/07/ai-spending-economy-shortages/
193•1vuio0pswjnm7•10h ago•281 comments

72M Points of Interest

https://tech.marksblogg.com/overture-places-pois.html
38•marklit•5d ago•6 comments

Coding agents have replaced every framework I used

https://blog.alaindichiappari.dev/p/software-engineering-is-back
260•alainrk•9h ago•433 comments

France's homegrown open source online office suite

https://github.com/suitenumerique
619•nar001•8h ago•275 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

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

Where did all the starships go?

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

We mourn our craft

https://nolanlawson.com/2026/02/07/we-mourn-our-craft/
358•ColinWright•3h ago•430 comments

Show HN: Kappal – CLI to Run Docker Compose YML on Kubernetes for Local Dev

https://github.com/sandys/kappal
35•sandGorgon•2d ago•16 comments

Learning from context is harder than we thought

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

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

https://github.com/valdanylchuk/breezydemo
290•isitcontent•1d ago•38 comments
Open in hackernews

Show HN: Extracting React apps from Figma Make's undocumented binary format

https://albertsikkema.com/ai/development/tools/reverse-engineering/2026/01/23/reverse-engineering-figma-make-files.html
55•albertsikkema•2w ago

Comments

albertsikkema•2w ago
Figma's API returns 400 for .make files, so I dug into the binary. Turns out it's a ZIP with a custom format: Deflate for the schema chunk, Zstandard for the data, then Kiwi binary decoding. Scripts on GitHub if useful: https://github.com/albertsikkema/figma-make-extractor
barnas2•1w ago
I'm curious if you tried binwalk? That's usually my goto for mysterious files.
lights0123•1w ago
I agree. It would likely have identified the separate deflate and zstd chunks automatically.
albertsikkema•1w ago
Never thought about using that, thanks for the tip!
albertsikkema•1w ago
that is a good one. Will try that next time.
vednig•2w ago
I once reverse engineered the Figma .fig file they have utilised quite good compression and data storage techniques for a tech company that uses AWS
albertsikkema•2w ago
That is a funny observation! You are right, that is strange.
voidUpdate•1w ago
> First thing I did was look at the raw bytes: xxd -l 4 "ClientApp.make"

I recommend using the linux "file" command, since it will generally be able to tell you these sorts of things straight away. I've been working on a long-term project to directly import figma design files into Unity, so I've ended up coming across a lot of these things myself

doctorpangloss•1w ago
Tell it to Mr. Claude. Who do you think made all these decisions?
frumplestlatz•1w ago
This is depressing.

We need different language for describing things AI did for us vs things we figured out ourselves. When a human presents work under their own name, there is an unspoken but widely relied-upon assumption that the presenter has exercised judgment over the space of possible choices and can explain why these ones were taken.

In other words, we naturally assume they engaged with the problem space deeply enough to justify the decisions made.

I think AI-produced code and investigation needs a disclaimer, and I say that as someone who uses vibe coding a lot to produce tooling used in our development process.

If you didn’t do it or write it yourself, you don’t understand it as well as if you had. If you didn’t look at the output in great detail and understand every choice made, you really shouldn’t be putting your name on it — or staking your reputation on it — without a pretty clear disclaimer.

And if you present an investigation done by AI as something done by yourself, you’re not really providing human insights. (Almost) anyone can drive an AI, and there’s not a lot of value there for your audience if you don’t disclose that’s what you did.

If you attach your name to work, you are asserting that you can meaningfully answer “why this and not something else?” across the decisions that matter. Tools that produce answers faster than humans think require new language, because our old words still imply thought occurred.

doctorpangloss•1w ago
the whole blog post and all the author's replies are authored by an LLM.
frumplestlatz•1w ago
Seems so. It should be much more explicitly disclaimed.
albertsikkema•1w ago
Interesting that you feel this is necessary. Why would a disclaimer be needed? If I read the technical docs for a library and use that in my code, should I explicitly mention that I got this from the docs? I know a lot, but am happy to admit I do not know everything, so I am happy to use tools that help me. And I got what I wanted in the end: being able to continue with my real work: helping a client.
frumplestlatz•1w ago
> When a human presents work under their own name, there is an unspoken but widely relied-upon assumption that the presenter has exercised judgment over the space of possible choices and can explain why these ones were taken.

> …

> If you attach your name to work, you are asserting that you can meaningfully answer “why this and not something else?” across the decisions that matter. Tools that produce answers faster than humans think require new language, because our old words still imply thought occurred.

voidUpdate•1w ago
This felt like an article of "This is how I worked this out". If you found something out through the docs, I'd be interested to know that. If you found it out through asking an LLM, that would be helpful to know as well. Maybe other people would write that kind of article differently, but when I write them, I try to put in as much detail as I can about how I worked something out, in case it's useful to other people
albertsikkema•1w ago
Funny, actually not the case. Co-authored partly yes, mainly to compensate for my lack of knowledge of the intricacies of English (not my native language). Anyway: take from it what you want, if it helps you: nice! Else: have fun doing something else.
voidUpdate•1w ago
(To clarify, all the work I did was me-authored, not LLM authored)
albertsikkema•1w ago
Even if that was the case: is it a real problem? I am not a purist in any sense: whatever tool gets the job done, I am fine with it.
albertsikkema•1w ago
Thanks, will keep that one in mind for next time!
nadis•1w ago
This is fascinating, thanks for sharing! I also appreciated the "when would you need this" section at the end.

> "When Would You Need This? - Client hands you a Figma Make prototype but not the design file - You want to audit AI-generated code before deployment - You need to migrate away from Figma Make to a different stack - You want to extract design tokens for your design system - Pure curiosity about how Figma structures its data"

albertsikkema•1w ago
Thanks!
dfajgljsldkjag•1w ago
It's interesting that the AI tool just writes react rather than creating a figma drawing. All that training on writing code has made it easier for AI to just write the app than make an illustration of it.
estimator7292•1w ago
I mean, it makes sense. In order to sketch out a screen, you need to run (most of) a layout engine in your head. If you're an AI, it's simpler to just... use a layout engine.
albertsikkema•1w ago
It's a pattern I see with more tools (lovable.dev does something similar). However looking at the code produced, lovable seems to be more precise about the code itself: just cleaner even over several iterations. Which is nice because it gives you a decent platform to continue on with your own code.