frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Lovable apps expose passport details and more than 200K private messages

https://www.crissyfield.de/research/lovable-en/
576•armcat•6h ago•234 comments

L3Harris Statement on the Nov. 13 Ground Stop

https://www.l3harris.com/newsroom/press-release/2026/11/l3harris-statement-nov-13-ground-stop
28•taspeotis•54m ago•7 comments

SpaceX Catches the Starship to end Flight 15

https://x.com/i/broadcasts/2brajgZlOKRMka
478•ls612•2h ago•298 comments

A Family Tree of Software Job Titles

https://zwischenzugs.com/2026/11/03/a-family-tree-of-software-job-titles/
176•umerf•6h ago•82 comments

How did Woz write the Apple 1 BASIC before building the computer?

https://retrocomputing.stackexchange.com/questions/17957
21•Skyfall106•1h ago•5 comments

KDE: The documentary [video]

https://tube.kockatoo.org/w/fFinNHfanLT7aBEb2B8y4c
352•mrkn1•10h ago•75 comments

PyPI's redesigned project pages with clearer security signals are now live

https://blog.pypi.org/posts/2026-11-06-ui-updates-complete/
188•rbanffy•8h ago•86 comments

Possible Futures

https://borretti.me/article/possible-futures
51•varjag•2d ago•37 comments

Why get an expensive Pi when I have an old phone?

https://so.long.thanks.fish/why-pi-when-i-have-an-old-phone/
482•casi•4d ago•273 comments

Seagate's new hybrid drive raises some old questions

https://arstechnica.com/gadgets/2026/11/seagate-resurrects-the-ssd-hdd-hybrid-drive/
60•PaulHoule•3d ago•33 comments

Advancing science and engineering with Antigravity's /teamwork

https://research.google/blog/advancing-science-engineering-with-antigravitys-teamwork-feature/
151•acossta•10h ago•34 comments

Nvidia deliberately kept GPU prices high through circular financing deals

https://www.techspot.com/news/114558-nvidia-deliberately-kept-gpu-prices-high-through-circular.html
37•madihaa•1h ago•21 comments

Show HN: DeepSeek V3 in ~200 lines of pure Jax

https://github.com/Vaibhaav-Tiwari/deepseek-v3-jax
140•VaibhaavTiwari•8h ago•7 comments

'Grey Rocking': The Life-Improving Power of Being Really, Really Boring (2021)

https://www.esquire.com/uk/life/a38473153/grey-rock-technique-being-boring/
71•NaOH•2d ago•40 comments

Reverse engineering a vintage diode-transistor logic chip

https://www.righto.com/2026/11/signetics-st680a-dtl-nand.html
84•dverlaeckt80•6d ago•4 comments

Generative AI uses more energy on non-English text

https://news.umich.edu/generative-ai-uses-more-energy-on-non-english-text/
167•DeepLogin•4d ago•93 comments

LinkedIn, Monster take down over 1000 fake job postings after CBC investigation

https://www.cbc.ca/news/canada/linkedin-monster-take-down-over-1-000-fake-job-postings-after-cbc-...
158•gnabgib•4h ago•80 comments

Show HN: A terminal-native idle factory game, written in Rust with ratatui

https://gitlab.com/snipedbywifi/terminactory
125•snipedbywifi•9h ago•25 comments

Write your own kernel optimiser

https://blog.csongor.co.uk/cachet-grids-and-tiles/
3•speckx•4d ago•0 comments

Project Zero will disclose vulnerabilities 90 days after reporting

https://projectzero.google/2026/11/disclosure-policy.html
128•hacb•12h ago•29 comments

The Sicilian Citrus Family Tree

https://www.notesfromtheroad.com/europa/citrus-family-tree.html
16•wmchen•3d ago•2 comments

Tech Companies Are Trying to Shift the Concept of Privacy (Again)

https://www.eff.org/deeplinks/2026/11/tech-companies-are-trying-shift-entire-concept-privacy-again
427•gslin•11h ago•164 comments

Demystifying phone unlocking tools: A technical overview

https://osservatorionessuno.org/blog/2026/05/demystifying-phone-unlocking-tools-a-technical-overv...
64•iloveyoutwo•9h ago•3 comments

A visual explanation of reinforcement learning

https://aatishb.com/myriad/how-brains-learn/
111•aatish•10h ago•6 comments

Italy fines Meta $887M over Android users' data access

https://www.reuters.com/world/italy-fines-meta-887-million-over-android-users-data-access-2026-11...
302•giuliomagnifico•9h ago•209 comments

Let's Write a PostScript Interpreter

https://beyondloom.com/blog/postscript.html
99•RebelPotato•1d ago•17 comments

Will we put data centers in space?

https://www.forethought.org/research/will-we-really-put-data-centers-in-space
53•simonebrunozzi•6h ago•154 comments

Show HN: Fursoy – Out-of-order RV64IMAFDV core in SystemVerilog (Linux 6.6)

https://github.com/FURSOY/fursoy-cpu
66•fursoy•9h ago•22 comments

Dartmouth (Guarini) will not admit math PhD cohort this year

https://www.thedartmouth.com/article/2026/11/gandhi-fagell-guarini-will-not-admit-math-ph-d-cohor...
61•sebg•4h ago•17 comments

Show HN: Agweb – a browser for agents that stays out of your way

https://github.com/paul-nameless/agweb
85•paul_nameless•9h ago•22 comments
Open in hackernews

How did Woz write the Apple 1 BASIC before building the computer?

https://retrocomputing.stackexchange.com/questions/17957
21•Skyfall106•1h ago

Comments

WillAdams•26m ago
For the sequel to this, see:

https://www.folklore.org/MacBasic.html

Skyfall106•23m ago
The Sql?

I'll leave now

femto•17m ago
What Woz did was the default way of writing assembly language programs for owners of 8-bit computers (mostly hobbyists). You didn't have money for a second machine, so you wrote your program on paper, you entered it then tested it in situ. Mostly you got it right, as doing it on paper was slow and meant you had the opportunity to put lots of thought into it. 8-bit instruction sets were simple enough that you eventually learned the most common instructions by heart. There was a point where I could mostly translate a Z80 program from assembly to machine code from (my) memory.

Maybe that is part of the nostalgia for the 8-bit days: the practice of "slow programming"? It was relaxing, sort of like those "slow tv" shows.

abecedarius•8m ago
There was a #hexcoders channel on IRC back in the 90s, admittedly very dead, and not just because octal is better for x86 code.
david-gpu•7m ago
I only had to assemble instructions by hand three times in my career. It is not difficult if you are already familiar with the ISA of that particular processor, but it is tedious.

The first time was in my first job writing OpenGL ES 2.0 blending operations for the Imagination Technologies SGX 535, which was a remarkably advanced little GPU for its time. Alpha blending happened through special instructions in the fragment/pixel shader. We did have a compiler, but it didn't handle blending, for whatever reason.

Through testing I noticed that NVidia GPUs performed blending incorrectly, according to the specification, which was a big surprise. Only years later I figured out that the specification had some errors; I now would bet that NVidia was doing the correct thing.

The second time I had to assemble instructions by hand happened while working on a stripped down version of the Radeon 7xxx series that shipped on some mobile phones. I don't recall what the problem was, whether we were adding a feature or optimizing the microcode generated for a particular OpenGL operation, but it involved a rarely-used feature called user-defined clipping planes. We didn't have an assembler for that GPU; all microcode was assembled by hand.

The third time happened at NVidia, and I will be vague, as not enough time has passed for me to be comfortable going into any detail. I had an idea for how to provide hardware acceleration for persistent CUDA kernels, which eventually was marketed as Cluster Launch Control (CLC). In order to quantify the benefit of adding some hardware, when it was possible to approximate that functionality in software, I needed to test the most efficient software implementation that was possible, and the compiler wasn't quite giving the assembly I wanted, so I had to manually patch some instructions post-compilation. Why did I not use the assembler that was available? I couldn't, because the assembly language did not provide a way to express the exact feature I had to patch.