frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Claude Sonnet will ship in Xcode

https://developer.apple.com/documentation/xcode-release-notes/xcode-26-release-notes
285•zora_goron•7h ago•220 comments

Strange CW Keys

https://sites.google.com/site/oh6dccw/strangecwkeys
63•austinallegro•3h ago•18 comments

Make any site multiplayer in a few lines. Serverless WebRTC matchmaking

https://oxism.com/trystero/
69•haxiomic•3d ago•17 comments

Ask HN: The government of my country blocked VPN access. What should I use?

941•rickybule•15h ago•526 comments

The Synology End Game

https://lowendbox.com/blog/they-used-to-be-good-but-now-theyve-turned-to-evil-the-synology-end-game/
19•amacbride•1h ago•2 comments

Lucky 13: a look at Debian trixie

https://lwn.net/Articles/1033474/
81•signa11•5h ago•18 comments

A deep dive into Debian 13 /tmp: What's new, and what to do if you don't like it

https://lowendbox.com/blog/a-deep-dive-into-debian-13s-tmp-whats-new-and-what-to-do-if-you-dont-l...
97•shaunpud•5h ago•60 comments

PSA: Libxslt is unmaintained and has 5 unpatched security bugs

https://vuxml.freebsd.org/freebsd/b0a3466f-5efc-11f0-ae84-99047d0a6bcc.html
45•burnt-resistor•3h ago•11 comments

Some thoughts on LLMs and software development

https://martinfowler.com/articles/202508-ai-thoughts.html
280•floverfelt•12h ago•245 comments

Fuck up my site – Turn any website into beautiful chaos

https://www.fuckupmysite.com/?url=https%3A%2F%2Fnews.ycombinator.com&torchCursor=true&comicSans=t...
237•coloneltcb•10h ago•77 comments

AI adoption linked to 13% decline in jobs for young U.S. workers: study

https://www.cnbc.com/2025/08/28/generative-ai-reshapes-us-job-market-stanford-study-shows-entry-l...
300•pseudolus•17h ago•427 comments

Uncertain<T>

https://nshipster.com/uncertainty/
328•samtheprogram•14h ago•71 comments

My startup banking story (2023)

https://mitchellh.com/writing/my-startup-banking-story
249•dvrp•12h ago•119 comments

The Space Shuttle Columbia disaster and the over-reliance on PowerPoint (2019)

https://mcdreeamiemusings.com/blog/2019/4/13/gsux1h6bnt8lqjd7w2t2mtvfg81uhx
125•scapecast•10h ago•102 comments

Launch HN: Dedalus Labs (YC S25) – Vercel for Agents

68•windsor•15h ago•13 comments

An eyecare foundation model for clinical assistance

https://www.nature.com/articles/s41591-025-03900-7
13•jameslk•9h ago•1 comments

Expert: LSP for Elixir

https://github.com/elixir-lang/expert
124•pimienta•10h ago•12 comments

AI coding made me faster, but I can't code to music anymore

https://www.praf.me/ai-coding
139•_praf•2d ago•137 comments

Python: The Documentary [video]

https://www.youtube.com/watch?v=GfH4QL4VqJ0
199•chmaynard•8h ago•64 comments

How life-size cows made of butter became an iconic symbol of the Midwest

https://www.smithsonianmag.com/smithsonian-institution/how-life-size-cows-made-of-butter-became-a...
11•noleary•3d ago•8 comments

Rupert's Property

https://johncarlosbaez.wordpress.com/2025/08/28/a-polyhedron-without-ruperts-property/
54•robinhouston•9h ago•8 comments

Sometimes CPU cores are odd

https://anubis.techaro.lol/blog/2025/cpu-core-odd/
82•rbanffy•10h ago•101 comments

Building your own CLI coding agent with Pydantic-AI

https://martinfowler.com/articles/build-own-coding-agent.html
149•vinhnx•13h ago•30 comments

Thrashing

https://exple.tive.org/blarg/2025/08/26/thrashing/
63•pch00•1d ago•11 comments

In Search of AI Psychosis

https://www.astralcodexten.com/p/in-search-of-ai-psychosis
132•venkii•2d ago•95 comments

Web Bot Auth

https://developers.cloudflare.com/bots/reference/bot-verification/web-bot-auth/
55•ananddtyagi•13h ago•48 comments

TuneD is a system tuning service for Linux

https://tuned-project.org/
63•tanelpoder•3d ago•19 comments

Powerful GPUs or Fast Interconnects: Analyzing Relational Workloads

https://vldb.org/pvldb/volumes/18/paper/Powerful%20GPUs%20or%20Fast%20Interconnects%3A%20Analyzin...
3•matt_d•3d ago•1 comments

You no longer need JavaScript: an overview of what makes modern CSS so awesome

https://lyra.horse/blog/2025/08/you-dont-need-js/
194•todsacerdoti•11h ago•111 comments

RSS is awesome

https://evanverma.com/rss-is-awesome
205•edverma2•8h ago•84 comments
Open in hackernews

Speed-coding for the 6502 – a simple example

https://www.colino.net/wordpress/en/archives/2025/08/28/speed-coding-for-the-6502-a-simple-example/
42•mmphosis•10h ago

Comments

rbanffy•10h ago
What a delightful short read.

They could go one step further and calculate the table as needed and use it as a cache.

For an single image scaling it might get a little bit better.

spc476•8h ago
If you read the entire article, they do that at the end of the article.
anyfoo•8h ago
Not quite. They build the entire table upfront, whether any individual entry is needed or not.

Making it an on-demand cache instead is a neat next step. Whether it helps or hurts depends on the actual input: If the input image uses every pixel value anyway, the additional overhead of checking whether the table entry is computed is just unnecessary extra with no value.

But if a typical image only uses a few pixel values, then the amortized cost of just calculating the few needed table entries may very well be significantly below the cost of the current algorithm.

If images are somewhere in between, or their characteristics not well known, then simply trying out both approaches with typical input data is a good approach!

Unless you’re perfectly happy with 0.2 seconds, for example because the runtime of some other parts take so long that dwarfs those 0.2s, then why bother.

egypturnash•7h ago
Even if you could get the "is this cell of the table calculated?" check down to one cycle (which you can't, 6502 branch instructions take 2-4 cycles, plus a few more operations to check the table calculation status), it's still gonna add one cycle to a hot loop that's done 43k times. Pre-calcing the entire table only burns 6k cycles, and can probably be done while displaying some transitional effect that requires very little CPU.

If we presume this scaling operation will be done more than one time (which it probably will be if it's getting this level of optimization) then it gets even worse.

anyfoo•2h ago
Good analysis. I guess I lost my cycle-counting foo, because on modern CPUs cycle-counting is a) infeasible on a superscalar, speculative, out-of-order CPU, and b) even if you did manage to do it, it hardly matters when a CPU cycle is less than a nanosecond, but any memory access that slips through the caches means many orders of magnitude higher latency.

Of course none of that applies here, but it colors the way you think about things…

Joker_vD•8h ago
I wonder if building this table can be sped up by noticing a recurring pattern?

    x    0  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 ... 254 255
    f(x) 0  0  1  2  3  3  4  5  6  6  7  8  9  9 10 11 12 12 ... 190 191
So something like

    sta table,y
    iny
    sta table,y
    adc $0
    iny    
    sta table,y
    adc $0
    iny    
    sta table,y
    adc $0
    iny    
used as the loop body that should be repeated 64 times, should work. Will it take less than 6000 cycles total?
FatalLogic•3h ago
I didn't check your code worked.. just copied it and ran the inner part of the loop once, but according to https://www.masswerk.at/6502/

It's about 2x faster. Your code uses 44 CPU cycles x 64

Edit: plus a branch instruction, maybe that adds 3 cycles x 64 I guess

anyfoo•8h ago
Very neat. Breaking up multiplications and divisions into bit shifts, and lookup table to trade off memory for runtime, are indeed nothing new to engineers working on the low level, but this paints a very pretty picture of how this looks in practice.
JKCalhoun•7h ago
Games that needed trig in the 90's often used SIN/COS lookup-tables. To keep memory down:

1) you only need the first 1/4 of the Sine table since the remaining 3/4 are either the first 1/4 in reverse and/or with the sign flipped.

2) and of course Sine can also be used as a Cosine lookup if you add pi/2 radians to the cosine angle (wrapping around of course).

3) to avoid the size needed for a table of floats you can of course use integers (scaled by some factor) or fixed-point values.

4) and simple interpolation would get you seemingly more precision.

(Combining all the above was a bit gross so documentation and a good SPI helped.)