frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Nvidia announces native GPU programming in Rust

https://developer.nvidia.com/blog/introducing-cuda-rust-two-tracks-for-writing-gpu-kernels/
598•nonmaskable•20h ago•219 comments

Keys Not Included: recovering the signing keys for US driver's license barcodes

https://ryan.science/blog/keys-not-included
142•Ryan5453•4h ago•53 comments

My temporary PHP fix from 2014 has nearly 20M installs. Today I'm deprecating it

https://jakeasmith.com/blog/http-build-url/
58•jakeasmith•1d ago•7 comments

Training a 4B model to produce 81% faster query plans than Postgres

https://rohanbansal.com/qorl
523•polyphilz•13h ago•108 comments

The Relation Between Mathematics and Physics by Paul Dirac

https://www.damtp.cam.ac.uk/events/strings02/dirac/speach.html
13•rramadass•3d ago•2 comments

Comparison of Malloc() Algorithms

https://egbert.net/blog/articles/comparison-of-arena-architecture-in-malloc.html
49•egberts1•1d ago•3 comments

Xiaomi Mimo 2.6 live post-training dashboard

https://mimo.xiaomi.com/rl/
416•krackers•11h ago•100 comments

Backups Aren't Simple

https://filipovski.net/2026/09/16/backups-arent-simple.html
212•afilipovski•11h ago•122 comments

Cloudflare/Security-Audit-Skill

https://github.com/cloudflare/security-audit-skill
31•donk8r•3h ago•4 comments

Small programming tricks

https://will-keleher.com/posts/small-programming-tricks-matter/
496•signa11•15h ago•219 comments

Developing provably correct Rust code with Verus

https://www.amazon.science/blog/developing-provably-correct-rust-code-with-verus
96•Betelbuddy•2d ago•12 comments

Breaking the 1.58-bit Barrier for Ternary LLMs

https://arxiv.org/abs/2609.16338
193•matt_d•10h ago•29 comments

A 32-year-old bug walks into a Telnet server

https://labs.watchtowr.com/a-32-year-old-bug-walks-into-a-telnet-server-gnu-inetutils-telnetd-cve...
51•paimapi•1d ago•16 comments

The engineering behind the US Strategic Petroleum Reserve

https://johnjwang.com/post/2026/09/15/engineering-behind-us-strategic-petroleum-reserve
189•johnjwang•1d ago•74 comments

The Return of Sail Power: Cargo Ships Are Turning Back to the Wind

https://gcaptain.com/the-return-of-sail-power-cargo-ships-are-turning-back-to-the-wind/
82•gumby•7h ago•47 comments

OpenSpec – A lightweight and configurable AI spec framework

https://openspec.dev/
134•etoxin•8h ago•53 comments

PCB is brought to you by Fable 5

https://a6mzero.com/posts/this-pcb-is-brought-to-you-by-fable-5/
86•jasonpeacock•2d ago•36 comments

AWS says it can't restore some data from mideast facilities struck by Iran

https://www.wsj.com/world/middle-east/aws-says-it-cant-restore-some-data-from-mideast-facilities-...
367•berkeleyjunk•1d ago•305 comments

Show HN: An e-ink frame that hears birds and draws them as 1800s illustrations

https://github.com/arnegiacomo/fugleramme
2145•arnemunthekaas•1d ago•243 comments

Performance Improvements in .NET 11

https://devblogs.microsoft.com/dotnet/performance-improvements-in-net-11/
275•soheilpro•1d ago•56 comments

HarnessTax: How Much Does the Harness Matter for Coding Agents?

https://harnesstax.github.io/
109•matt_d•9h ago•46 comments

Reversing Factorio's RNG

https://gegell.github.io/posts/factorio-rng/
196•jheitmann•4d ago•26 comments

Japan's book scene is moving from bookstores to libraries

https://untranslatedjp.substack.com/p/japans-book-scene-is-quietly-moving
175•herbertl•4d ago•72 comments

Part-human part-mouse brain developed in science breakthrough

https://www.bbc.com/news/articles/c60m3k28j81mo
34•marc__1•6h ago•22 comments

Jev Ultrafast: A browser agent with a dynamic, indexed action space

https://github.com/browser-use/jev-ultrafast
41•rahimnathwani•4h ago•4 comments

US interest rates raised for first time in three years

https://www.bbc.com/news/articles/cw4gmlyvj422o
39•higginsniggins•8h ago•8 comments

Anecdotally, programmers dislike "reduce"

https://evanhahn.com/posts/2026-09-13-programmers-dislike-reduce/
144•vinhnx•3d ago•221 comments

Reverse-engineered Jev-like model

https://github.com/vinnylarouge/jevlike
117•rochansinha•13h ago•17 comments

Dream-RSI: Recursive Self-Improvement through Evolving Worlds

https://arxiv.org/abs/2609.14858
199•bananaflag•18h ago•49 comments

Anatomy of a Texture

https://agentlien.github.io/texture/
90•Agentlien•17h ago•15 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).