frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Framing suffering and loss after the Great 1934 earthquake [pdf]

https://www.cambridge.org/core/services/aop-cambridge-core/content/view/13436B7E14A3484EB7615E15E...
1•joebig•32s ago•0 comments

The tech powering ICE's deportation crackdown

https://techcrunch.com/2026/01/26/heres-the-tech-powering-ices-deportation-crackdown/
1•cdrnsf•41s ago•0 comments

Harnessing Plasmons for Alternative Computing Power

https://spectrum.ieee.org/plasmon-computing-device
1•rbanffy•1m ago•0 comments

LocalStack to unify Community and Pro images, require account for use

https://blog.localstack.cloud/the-road-ahead-for-localstack/
1•rroblak•1m ago•0 comments

I have no mouth and I must scream at Black people: Scott Adams, 1957-2026

https://www.tcj.com/i-have-no-mouth-and-i-must-scream-at-black-people-scott-adams-1957-2026/
2•CharlesW•4m ago•0 comments

Chainguard EmeritOSS backs MinIO, other orphaned projects

https://thenewstack.io/chainguard-emeritoss-backs-minio-other-orphaned-projects/
1•CrankyBear•5m ago•0 comments

Show HN: Artemis – A proactive AI that you can literally call to get work done

https://www.artemsagent.com/
1•yoitsmanan•5m ago•0 comments

Thankful for Memory Managed Languages (2025)

https://www.mooreds.com/wordpress/archives/3720
1•mooreds•6m ago•0 comments

54 Years of Fiat Debasement: Comparing a steak dinner in 1971 vs. 2024

https://www.equitileconversations.com/2459100/episodes/18567958-let-s-get-physical
1•Incerto•7m ago•0 comments

More invoker commands, and more reasons not to use JavaScript please

https://pawelgrzybek.com/more-invoker-commands-and-more-reasons-not-to-use-javascript-please/
1•ulrischa•7m ago•0 comments

Ask HN: What is no longer worth learning in programming due to AI?

1•radicalethics•7m ago•0 comments

Schrödinger's cat just got bigger: physicists create largest ever superposition

https://www.nature.com/articles/d41586-026-00177-9
1•rbanffy•8m ago•0 comments

Reflections of a Developer on LLMs in January 2026

https://rmoff.net/2026/01/27/reflections-of-a-developer-on-llms-in-january-2026/
1•mooreds•9m ago•0 comments

Ask HN: What is no longer worth learning in programming?

2•radicalethics•9m ago•0 comments

2025/26 State of Mozilla report is finally here

https://stateof.mozilla.org/
2•mzlaai•10m ago•0 comments

Khipu Field Guide

https://www.khipufieldguide.com
2•vopi•10m ago•1 comments

Clawdbot Renames to Moltbot

https://github.com/moltbot/moltbot/commit/6d16a658e5ebe6ce15856565a47090d5b9d5dfb6
1•philip1209•10m ago•0 comments

Century-old solar records refine future cycle forecasts

https://www.spacedaily.com/reports/Century_old_solar_records_refine_future_cycle_forecasts_999.html
1•mooreds•11m ago•0 comments

World's Fastest Commodore PET Using The MCL65+

https://hackaday.io/project/204693-worlds-fastest-commodore-pet-using-the-mcl65
1•oldnetguy•13m ago•0 comments

Social Media Giants Face Landmark Legal Tests on Child Safety

https://www.nytimes.com/2026/01/27/technology/social-media-addiction-trial.html
1•JumpCrisscross•13m ago•0 comments

Type Narrowing Patterns in Pyrefly That Make Type Checking More Intuitive

https://pyrefly.org/blog/type-narrowing/
3•ocamoss•13m ago•0 comments

Nitrate source and dementia risk: vegetables-dec. risk; water, animal foods-inc

https://medicalxpress.com/news/2026-01-nitrate-linked-dementia-vegetables.html
1•bikenaga•15m ago•1 comments

Ask HN: Will AIs Need Psychiatrists?

1•toddh•16m ago•0 comments

Prism

https://openai.com/index/introducing-prism
3•meetpateltech•16m ago•0 comments

Methods for protecting yourself against an LRAD system – Tech Ingredients (2020) [video]

https://www.youtube.com/watch?v=CXKTBQBugIA
2•goda90•16m ago•0 comments

Forever Overhead – David Foster Wallace

https://welcometotheloonybin.wordpress.com/2008/09/17/forever-overhead/
1•ofalkaed•17m ago•0 comments

MCP Apps

http://blog.modelcontextprotocol.io/posts/2026-01-26-mcp-apps/
1•sanj•19m ago•0 comments

Ask HN: How to avoid skill atrophy in LLM-assisted programming era?

3•py4•20m ago•0 comments

Pretty much 100% of our code is written by Claude Code and Opus 4.5

https://twitter.com/bcherny/status/2015979257038831967
1•sysoleg•20m ago•0 comments

Stanford scientists reveal oldest map of the night sky

https://www.kqed.org/news/12070647/stanford-scientists-reveal-oldest-map-of-the-night-sky-previou...
1•dr_dshiv•22m ago•0 comments
Open in hackernews

Show HN: Goldenthread – Compile Go to TypeScript Zod for type-safe validation

https://github.com/blackwell-systems/goldenthread
1•daynablackwell•2h ago
Hi HN,

I kept shipping features where the frontend accepted data the backend rejected. Validation rules lived in two places (Go struct tags and TypeScript Zod schemas), and they'd drift.

I built goldenthread to solve this. It's a build-time compiler that generates TypeScript Zod schemas from Go struct tags. Write validation once, use it everywhere.

Example:

    // Go backend
    type User struct {
        Username string `json:"username" gt:"required,len:3..20"`
        Email    string `json:"email" gt:"email"`
        Age      int    `json:"age" gt:"min:13,max:130"`
    }
Run `goldenthread generate ./models` and you get:

    // TypeScript (auto-generated)
    export const UserSchema = z.object({
      username: z.string().min(3).max(20),
      email: z.string().email(),
      age: z.number().int().min(13).max(130)
    })

    export type User = z.infer<typeof UserSchema>
The compiler uses go/packages and go/types for accurate type resolution. It handles nested objects, enums, maps, embedded structs, and 37+ validation rules.

The best feature: drift detection. Run `goldenthread check` in CI - it computes SHA-256 hashes of your schemas and fails the build if generated TypeScript doesn't match Go source. No more "frontend works locally but breaks in production because someone changed the backend struct."

Before releasing v0.1.0, I ran continuous fuzzing (10 targets, hourly in GitHub Actions). It found two bugs my test suite missed:

  1. UTF-8 corruption: Japanese field names with empty JSON tags triggered byte-slicing bugs in camelCase conversion. Took 444,553 executions to discover.

  2. Regex escaping: Patterns with newline characters produced broken JavaScript output. Found in 180 executions.
Both required specific intersections of conditions that manual testing wouldn't cover. I wrote up the full fuzzing setup here: https://blackwell-systems.github.io/blog/posts/continuous-fu...

The tool is production-ready:

Zero runtime dependencies (generated code only imports Zod) Generates readable TypeScript (looks hand-written) Complete Go type support (primitives, arrays, maps, nested objects) Works with any Go project structure MIT OR Apache 2.0 dual licensed

I built this because I was tired of frontend/backend validation bugs in my day job (hospitality platform with booking/payment APIs). We use it internally now.

Real-world example in the repo: 9-schema e-commerce system with Customer records (E.164 phone validation), Product SKUs (regex patterns), and Order workflows (nested objects + array constraints).

GitHub: https://github.com/blackwell-systems/goldenthread Docs: https://github.com/blackwell-systems/goldenthread/blob/main/... Tag syntax: https://github.com/blackwell-systems/goldenthread/blob/main/...

Would love feedback

Thanks for looking!