frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Amateur armed with ChatGPT solves an Erdős problem

https://www.scientificamerican.com/article/amateur-armed-with-chatgpt-vibe-maths-a-60-year-old-pr...
149•pr337h4m•10h ago•80 comments

Why has there been so little progress on Alzheimer's disease?

https://freakonomics.com/podcast/why-has-there-been-so-little-progress-on-alzheimers-disease/
124•chiefalchemist•4h ago•60 comments

USB Cheat Sheet (2022)

https://fabiensanglard.net/usbcheat/index.html
201•gwerbret•6h ago•48 comments

Flickr: The first and last great photo platform

https://petapixel.com/2026/04/22/flickr-the-first-and-last-great-photo-platform/
83•Nrbelex•3d ago•42 comments

OpenAI Privacy Filter

https://openai.com/index/introducing-openai-privacy-filter/
141•tanelpoder•3d ago•24 comments

The Free Universal Construction Kit

https://fffff.at/free-universal-construction-kit/
288•robinhouston•3d ago•56 comments

1-Bit Hokusai's "The Great Wave" (2023)

https://www.hypertalking.com/2023/05/08/1-bit-pixel-art-of-hokusais-the-great-wave-off-kanagawa/
536•stephen-hill•3d ago•88 comments

Using coding assistance tools to revive projects you never were going to finish

https://blog.matthewbrunelle.com/its-ok-to-use-coding-assistance-tools-to-revive-the-projects-you...
224•speckx•12h ago•121 comments

Mahjong: A Visual Guide

https://themahjong.guide/
6•iamwil•2d ago•1 comments

The Joy of Folding Bikes

https://blog.korny.info/2026/04/19/the-joy-of-folding-bikes
110•pavel_lishin•3d ago•68 comments

America's Geothermal Breakthrough

https://oilprice.com/Alternative-Energy/Geothermal-Energy/Americas-Geothermal-Breakthrough-Could-...
89•sleepyguy•8h ago•101 comments

Math Is Hard – OpenBSD Stories

http://miod.online.fr/software/openbsd/stories/vaxfp.html
59•signa11•2d ago•1 comments

The George Business, by Roger Zelazny (1980)

https://www.eternal-flame.org/library/oldlibrary/georgebusiness.html
14•xeonmc•2d ago•0 comments

Optimizing Datalog for the GPU

https://dl.acm.org/doi/10.1145/3669940.3707274
30•tosh•2d ago•3 comments

New 10 GbE USB adapters are cooler, smaller, cheaper

https://www.jeffgeerling.com/blog/2026/new-10-gbe-usb-adapters-cooler-smaller-cheaper/
558•calcifer•22h ago•334 comments

DeepSeek-V4 on Day 0: From Fast Inference to Verified RL with SGLang and Miles

https://www.lmsys.org/blog/2026-04-25-deepseek-v4/
15•mji•4h ago•0 comments

Reviving BrowserID in 2026

https://wakamoleguy.com/p/reviving-browserid-in-2026
5•wakamoleguy•1h ago•0 comments

Simulacrum of Knowledge Work

https://blog.happyfellow.dev/simulacrum-of-knowledge-work/
110•thehappyfellow•10h ago•41 comments

The Long Reply

https://ironicsans.ghost.io/the-long-reply/
20•NaOH•2d ago•0 comments

Does Internet Advertising Work?

https://freakonomics.com/podcast/does-advertising-actually-work-part-2-digital-ep-441/
6•hackthemack•2h ago•9 comments

What async promised and what it delivered

https://causality.blog/essays/what-async-promised/
177•zdw•3d ago•202 comments

Mine, an IDE for Coalton and Common Lisp

https://coalton-lang.github.io/mine/
79•varjag•10h ago•32 comments

Desmond Morris has died

https://www.bbc.com/news/articles/c51y797v200o
113•martey•5d ago•20 comments

The Super Nintendo Cartridges

https://fabiensanglard.net/snes_carts/
9•offbyone42•3h ago•1 comments

How Hard Is It to Open a File?

https://blog.sebastianwick.net/posts/how-hard-is-it-to-open-a-file/
68•ffin•2d ago•11 comments

Martin Galway's music source files from 1980's Commodore 64 games

https://github.com/MartinGalway/C64_music
169•ingve•17h ago•25 comments

Tell HN: An app is silently installing itself on my iPhone every day

45•_-x-_•3h ago•32 comments

Discret 11, the French TV encryption of the 80s

https://fabiensanglard.net/discret11/
158•adunk•17h ago•27 comments

GPT‑5.5 Bio Bug Bounty

https://openai.com/index/gpt-5-5-bio-bug-bounty/
138•Murfalo•13h ago•98 comments

Colorado Adds Open-Source Exemption to Age-Verification Bill

https://fosstodon.org/@carlrichell/116460505717380644
78•terminalbraid•5h ago•26 comments
Open in hackernews

RSC for Astro Developers

https://overreacted.io/rsc-for-astro-developers/
43•feross•11mo ago

Comments

brudgers•11mo ago
Astro is The web framework for content-driven websites.

https://github.com/withastro/astro

betterThanTexas•11mo ago
> The web framework for content-driven websites.

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

ameliaquining•11mo ago
I think this means, as opposed to rich interactive web apps where everything interesting happens after the initial page load.
betterThanTexas•11mo 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•11mo 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•11mo 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•11mo 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/

betterThanTexas•11mo 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•11mo 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.
naet•11mo 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•11mo 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•11mo 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•11mo 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•11mo 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•11mo 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•11mo ago
> share context between islands

This is extremely easy to solve with Astro:

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

skeptrune•11mo 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•11mo ago
You're right. Sorry I misunderstood. For some reason instead of "context" I read "state".
danabramov•11mo 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.
skeptrune•11mo 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•11mo 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).

flashblaze•11mo 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.