frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Who are we willing to exclude?

https://design.scotentblog.co.uk/who-are-we-willing-to-exclude/
1•robin_reala•19s ago•0 comments

The Human Timeline

https://mg-crea.com/blog/the-human-timeline/
1•olouv•45s ago•0 comments

Human TPS: How fast can your fingers generate tokens?

https://homoagens.github.io/human-tps/
1•cmrdporcupine•3m ago•0 comments

That First and Last Question

https://brianschrader.com/archive/that-first-and-last-question/
1•sonicrocketman•4m ago•0 comments

Show HN: Cordum Edge – A local firewall to sandbox AI coding agents

https://github.com/cordum-io/cordum](https://github.com/cordum-io/cordum)
1•yaront111•5m ago•0 comments

Reduced-Round SHA-256 Compression Preimages

https://github.com/kamb-code/sha256-r19-preimage
1•wslh•8m ago•0 comments

Ex-ARRR: Sailing the 0-click Seas

https://ironpeak.be/blog/ex-arrr-sailing-the-0-click-seas/
1•ibobev•8m ago•0 comments

Show HN: Low Poly Earth – The whole planet in 3D, built from OpenStreetMap data

https://lowpolyearth.pages.dev/
2•blueblazin•9m ago•0 comments

Detect when elements overlap with CSS

https://ishadeed.com/article/css-detect-overlap/
1•ibobev•9m ago•0 comments

What I believe about the future of software development

https://thorstenball.com/blog/2026/09/19/what-i-believe-about-the-future-of-software-development/
2•ibobev•9m ago•0 comments

Dual-Syncopation Meet-in-the-Middle Attacks: New Results on SHA-2 and MD5

https://eprint.iacr.org/2026/353
1•wslh•9m ago•0 comments

Ask HN: How is code review holding up at your company?

1•lackoftactics•10m ago•0 comments

Phyllotaxis: An audio-reactive LED display

https://jagi.studio/posts/phyllotaxis/
1•evakhoury•11m ago•0 comments

privacyguides.org

https://github.com/privacyguides/privacyguides.org
1•saikatsg•12m ago•0 comments

The large robotic arm on the International Space Station has stopped working

https://arstechnica.com/space/2026/09/the-large-robotic-arm-on-the-international-space-station-ha...
2•robin_reala•12m ago•0 comments

Opus 5.5 showcasing: Liquid Glass-like elements for the web

https://tomacco.github.io/amazing-glass/
2•drinkcocacola•13m ago•1 comments

Infinitrance [video]

https://www.youtube.com/watch?v=uUNnd3uI37M
1•jsemrau•13m ago•0 comments

How to reduce token usage in Claude Code, Codex, and Cursor

https://www.avanderlee.com/ai-development/reduce-token-usage-claude-code-codex-cursor/
1•meetpateltech•16m ago•0 comments

Recursive Self-Improvement via On-Policy Distillation for Reasoning

https://arxiv.org/abs/2609.30652
1•simonpure•17m ago•0 comments

The problem is not the AI code, but nobody knows anything anymore

https://www.ssp.sh/brain/the-problem-is-not-the-ai-code-but-nobody-knows-anything-anymore/
44•zazuke•19m ago•12 comments

13 Months Sober (2025)

https://www.bobbytables.io/p/13-months-sober
2•btables•19m ago•0 comments

Active, in-the-wild exploitation of CVE-2026-88771 with IoCs

https://twitter.com/LupovisDefence/status/2104595071362326680
1•noktec•19m ago•0 comments

Congress is considering giving doctors automatic annual pay raises in Medicare

https://www.statnews.com/2026/09/24/patients-first-act-congress-moves-on-doctor-pay-medicare-reform/
2•brandonb•21m ago•0 comments

Show HN: Assay – a QA CLI that finds bugs with no LLM and no tests written

https://github.com/awss1i/assay
1•awss1i•21m ago•0 comments

Nero

https://storia-e-libri.fandom.com/it/wiki/Nero
1•ArthurFischerp•23m ago•0 comments

AI-guided optimization for thermostable mRNA vaccines

https://www.nature.com/articles/s41587-026-03330-x
1•sbulaev•23m ago•0 comments

Should I Stay or Should I Go?

https://www.newyorker.com/magazine/2026/10/05/should-i-stay-or-should-i-go
1•tacon•24m ago•0 comments

Daily Logic Puzzles

https://logicpuzzles.io/
1•andrewmcm•25m ago•1 comments

APOD's main NASA site is moving

https://asterisk.apod.com/viewtopic.php?t=45023
2•pndy•25m ago•1 comments

Open-source Python simulation benchmarking rainbow gravity against NGC 3198

https://domushorizon.vercel.app/teoria-del-todo.html
1•rovettabenvenut•27m ago•0 comments
Open in hackernews

What makes Lisp difficult to read?

https://paultm.nl/paren-thesis
2•ibobev•1h ago

Comments

perrygeo•1h ago
> I have not yet encountered a fully satisfying explanation as to why Lisp is perceived as being less readable.

Difficulty is, by definition, relative to one's skill. You cannot so quickly discount the fact that 99% of programming is taught in Java/C style language syntax. If you've had lifelong exposure to Lisp, you might feel exactly the opposite. The author does a poor job of justifying why these pop-cognitive-psych theories should have more weight than prior exposure.

Personally, as someone with decades of exposure to both styles, I look at the factorial example and see everything I love about Lisp syntax - consistent, no magic keywords and syntax to memorize, it represents a tree just like my mental model of code, there's no way to fall through and forget an else, expressions instead of statements, no early returns ... literally everything about the Lisp example is more readable to me. YMMV.

PaulHoule•54m ago
I tend to struggle with other people's indentation rules for code and other programming languages, like nobody liked my article that said you should carry indentation into embedded strings that represent other programming laguages like SQL

   result = sql.execute("""
      SELECT someColumn
      FROM thatTable
      WHERE anotherValue>55
        AND state='pending'
      ORDER BY createdDate
   """)
Ultimately the idea is that indentation should be influenced by semantics, the intention of the code, and not just the syntax. Of course that is against the "one way to indent" philosophy of Go, Biome, and such... But I might accept less than optimal indentation to put an end to tab wars once and for all.

I find indentation of Lisp always seems to fail at communicating in the semantics, much worse than other languages. Things like

   (if condition truePath falsePath)
are scrambled when your eye skips over something. If the Lisp community got over its respect for tradition perhaps they'd develop some kind of syntax highlighting or tooltips or something that would clarify this sort of structure.

About 90% of real language have subject-verb-object or subject-object-verb orders

https://en.wikipedia.org/wiki/Subject%E2%80%93object%E2%80%9...

verb-subject-object and verb-object-subject are more Lisp-like and represent 10% of languages including Standard Arabic, Finnish and Fillipino.

I like extreme parsimony, like I'd love to write stuff like

   format = lambda: `%1-%2`
but I think as complexity goes up depending on the meaningful order of elements breaks down in many ways and you need to give things meaningful names.