frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Codex CLI installs a persistent, self-updating background daemon by default

https://github.com/openai/codex/issues/48195
125•whimblepop•57m ago•69 comments

GLM-Legal

https://z.ai/blog/glm-legal
266•ilreb•3h ago•156 comments

A Modern Web App in C

https://prophitt.me/writing/a-modern-web-app-in-c
187•prophittcorey•3h ago•79 comments

AI coding agents generate more code, but not more software

https://arstechnica.com/ai/2026/10/ai-coding-agents-generate-more-code-but-not-more-software/
134•gumby•2h ago•103 comments

Launch HN: Agent37 (YC F26) – Low-cost agent sandboxes for running agents

50•vishnukool•2h ago•36 comments

Citroen revives the 2CV for an electric age

https://www.bbc.com/news/articles/c620r33plgppo
169•scrlk•7h ago•196 comments

Muse Wonder

https://research.meta.ai/blog/muse-wonder
308•meetpateltech•2h ago•140 comments

Hackers activate automatic defrosting accross European supermarket fridges

https://www.tomshardware.com/tech-industry/cyber-security/unprecedented-cyberattack-cripples-supe...
169•Zeekaas•7h ago•334 comments

Turn a WiFi 7 Router into a 320Msps Software Defined Radio Receiver

https://github.com/h0m3us3r/w1700k-sdr
130•djfergus•6h ago•43 comments

Thinking will become a hobby

https://www.spinellis.gr/blog/20261008/?li261008
100•pranitha_m•2h ago•119 comments

The Making Of Super Mario 64 – full Giles Goddard interview (2001)

https://pixelatron.com/blog/the-making-of-super-mario-64-full-giles-goddard-interview-ngc/
177•gregsadetsky•1d ago•67 comments

Kevin Kelly's 2016 AI Predictions, 10 Years Later

https://taylor.town/kk-ai-2026
68•surprisetalk•4h ago•13 comments

Secret of Orange Cats Revealed After 60-Year Search

https://www.sciencealert.com/secret-of-orange-cats-finally-revealed-after-60-year-search
177•bookofjoe•1d ago•153 comments

Publishers Killed the Paperback, Then Blamed Readers

https://jacobin.com/2026/10/books-publishing-reading-mass-market-paperback
27•PaulHoule•58m ago•11 comments

Fingerprints are the new cookies

https://royfish.dev/fingerprints-are-the-new-cookies
663•royfish•20h ago•316 comments

Show HN: PS2 games statically recompiled to WebAssembly

https://github.com/snuri00/ps2-web-recomp
218•deadxwarrior•12h ago•116 comments

Fridges in French supermarkets hit by cyber attack

https://www.bbc.com/news/articles/crq5nzxv9q4yo
117•cataflam•4h ago•71 comments

The gap in shared understanding of LLM capability is widening

https://twitter.com/karpathy/status/2109361546505966046
647•albertzeyer•23h ago•941 comments

Type-safe HTML templating in Zig

https://lalinsky.com/2026/10/11/type-safe-html-templating-in-zig.html
215•lukaslalinsky•14h ago•78 comments

Feds Got Warrants to Use Fake Cell Towers to Hunt Down Don Lemon's Producer

https://www.wired.com/story/feds-got-warrants-to-use-fake-cell-towers-to-hunt-down-don-lemons-pro...
54•rndsignals•2h ago•30 comments

My Reddit AMA on the Law of Web Scraping

https://blog.ericgoldman.org/archives/2026/10/my-reddit-ama-on-the-law-of-web-scraping.htm
21•speckx•1h ago•2 comments

I Found a $90k Remote Code Execution Vulnerability in Google

https://simonkoeck.com/writeups/google-devsite-flask-session-pickle-rce
133•soeckly•11h ago•58 comments

Total Annihilation, rebuilt for modern computers

https://nanolathe.gg
643•jttnr•1d ago•246 comments

Calculus with Julia

https://jverzani.github.io/CalculusWithJuliaNotes.jl/
239•subset•2d ago•46 comments

Introducing OpenFatigue

https://openfatigue.ai/
20•ajcp•17m ago•1 comments

(Post-Quantum) Cryptographic Right Answers

https://words.filippo.io/right-answers/
51•gavide•6h ago•6 comments

Incident with Actions, Pull Requests and Issues

https://www.githubstatus.com/incidents/93njd414rpbx
142•dkpk•7h ago•128 comments

Reverse engineer anything with agents, from app behavior down to native binaries

https://github.com/morluto/rea
29•taytus•2h ago•6 comments

French supermarkets suffer refrigerator shutdown after unprecedented cyberattack

https://www.rnz.co.nz/news/world/1865776/french-supermarkets-suffer-refrigerator-shutdown-after-u...
16•billybuckwheat•1h ago•7 comments

Running the unmodified Linux amdgpu driver on an iPad

https://github.com/Geramy/LemonSeed-Studio
79•joshcsimmons•1d ago•19 comments
Open in hackernews

RSC for Astro Developers

https://overreacted.io/rsc-for-astro-developers/
43•feross•1y ago

Comments

brudgers•1y ago
Astro is The web framework for content-driven websites.

https://github.com/withastro/astro

betterThanTexas•1y ago
> The web framework for content-driven websites.

As opposed to those driven by, what, random-number generators?

ameliaquining•1y ago
I think this means, as opposed to rich interactive web apps where everything interesting happens after the initial page load.
betterThanTexas•1y ago
I have no clue how you discerned this from the description, but I'd like to understand more. What can you point to on your computer that isn't "content"?
pcthrowaway•1y ago
Interactive UI components aren't content, though they might affect content delivery.

For example, a Javascript+HTML game might be itself considered content, but within the game the game elements and controls (mouse, player characters, NPCs, keyboard bindings) wouldn't be considered content, whereas images and dialog text might reasonably considered content again.

betterThanTexas•1y ago
I don't see why interactive UI is any less content than anything else delivered over the wire. How would you express a website without it?

it almost seems like the word "content" is intended to connote "profitable and dynamically-loaded assets". Why you would not use that phrase is a mystery.

I suppose that "dynamically-loadable asset creator" isn't a great marketing pitch from the perspective of artists.

azangru•1y ago
> I have no clue how you discerned this from the description, but I'd like to understand more.

One way of understanding the meaning of a dubious phrase is examining its use in context. For example, one of the pages of the Astro docs begins as follows:

"Astro is the web framework for building content-driven websites like blogs, marketing, and e-commerce" [0]

Ok; so we have our prototypes — or, as Jason Miller would call them, holotypes — of the mysterious "content-driven websites". They are blogs, marketing sites, or e-commerce sites.

Another way of understanding the meaning of a confusing phrase is hearing the distinction explained by the creator of the framework. In early podcasts, when Astro was still mostly unknown, Fred Schott explained that it was not intended for building something like Figma, or Photoshop, or Facebook, or Youtube; but rather something like blogs or magazines; although primarily he was probably targeting the creators of e-commerce websites, because those were the ones that could bring in money.

[0] https://docs.astro.build/en/concepts/why-astro/

naet•1y ago
There are "content" driven websites which are things like blogs, marketing / brochure style sites, documentation sites, etc. They are driven by content that is authored by the website owners that can then be cached or is not frequently updated by end users or external data.

Then there are sites that are more application driven or service driven. Stuff like a messaging client, social media, streaming service, eCommerce, or other full on interactive web app. They tend to be more data driven or dependent on end users, and less static content.

That is frequently how the word content is used in the context of web development. You might have heard of a CMS or content management system. It's not the same as someone using the word content like social media "content creator".

insin•1y ago
Former Gatsby users know where they were on the day they freed themselves from that flaky image processing pipeline piped through GraphQL (they were at their computer).

There's no evidence for this, but it's a scientific fact that Astro has five 9s... in its net promoter score.

swyx•1y ago
fellow gatsby refugee here but i'd be fair to gatsby that i dont think the flakiness of the image processing is gatsby's fault, it's `sharp`, its just a very cpu heavy workload and for large sites it's gonna choke. graphql had nothing to do with this one
pier25•1y ago
Astro is great.

It became my default SSG a couple of years ago and now I'm seriously considering using it for apps too. Anyone has experience with that?

I'm thinking I could just use Astro for rendering the HTML with islands but still use a non-JS backend.

flashblaze•1y ago
If you're planning on using any framework (like React), I won't recommend it. The reason being, if you're using any library from React which depends on the Context API, it will cause issues since you'll have to wrap your respective pages/components with it and handle navigation on the client side to preserve any global "state" if any. At which point, you're better off using a fullstack framework.
skeptrune•1y ago
Only reason why I would use RSC's over Astro is to share context between islands. There's no other major benefit.

Also, nit, but I wish this article explicitly mentioned and explained Astro's "code fence" idea. It's demarcates the boundary between server and client much more clearly than React's 'use client'.

pier25•1y ago
> share context between islands

This is extremely easy to solve with Astro:

https://docs.astro.build/en/recipes/sharing-state-islands/

skeptrune•1y ago
>In Astro, you can nest Astro Components inside Client Islands, but if those include more Client Islands, they’ll still be seen as separate roots by your framework (e.g. React). This is why nesting interactive behavior doesn’t compose as naturally as in client apps, e.g. React or Vue context can’t be passed between Astro islands.

I agree with what the link author wrote here. Nanostores is great (s/o EvilMartians), but it's not as natural or easy to use as each respective framework's context solution.

pier25•1y ago
You're right. Sorry I misunderstood. For some reason instead of "context" I read "state".
danabramov•1y ago
I slightly disagree with your nit. I don’t think code fence really demarcates the boundary because the code below the fence definitely does run on the server — otherwise, referencing other Astro components wouldn’t work there. The fence represents the “bindings vs template” separation but not “server vs client” in my reading.
flashblaze•1y ago
Love love love Astro. Been using it since it was launched. My personal site and 1st product's landing page both are built using Astro. Builds fast, has the ability to ship 0 JS and allows to any frontend libarary makes it a killer framework imo.
betterThanTexas•1y ago
> "Astro is the web framework for building content-driven websites like blogs, marketing, and e-commerce" [0]

Ok, but opposed to what? What does a non-content oriented website look like? Is a website itself not simply content?

> Fred Schott explained that it was not intended for building something like Figma, or Photoshop, or Facebook, or Youtube

Perhaps their tagline should be "we aren't oriented around building single page websites unlike all those other frameworks". I never would have understood that Figma, Photoshop, and Youtube were not content-oriented websites otherwise. "Content" is mostly not a meaningful phrase outside of a context which gives it meaning (i.e. it is a floating signifier).

azangru•1y ago
Sure, content is anything a container contains :-) My point was though that when a dictionary definition gives an unsatisfactory reading of a sentence, then perhaps other, indirect methods should be employed to tease the meaning out.
skeptrune•1y ago
Fair point, you've convinced me on the "bindings vs template" distinction.

However, from a developer's perspective, the ability to securely make backend requests with secrets in the top fenced area and pass results to the template still feels like a clear "server-side execution context" boundary.

danabramov•1y ago
Yeah. Not saying it’s the same thing but the conceptual equivalent to this boundary is

import "server-only"

This causes a build error if imported from a client environment. So the intended usage is that you put that into your secrets (and maybe even in your data layer entry point) and you’re golden. It will poison any transitive import that eventually imports that thing.

The developer wouldn’t necessarily “see” where they are at any given moment but importing the “wrong thing” would give them a module stack trace so they can decide where to “make the cut”. It takes a bit to embrace this workflow but it’s productive once you “mark” what’s server-only.

The enforcement of “can’t use state on the client” is built on the same mechanism but inverse (client-only).