frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Toyota, Nissan, and Honda to standardize parts to lower costs

https://www.caranddriver.com/news/a74490092/toyota-nissan-honda-standardize-parts-lower-costs/
453•zdw•5h ago•263 comments

Pill to treat pancreatic cancer hailed as 'biggest breakthrough in decades'

https://www.theguardian.com/society/2026/nov/20/pill-pancreatic-cancer-breakthrough-daraxonrasib
977•rafaelc•1d ago•213 comments

Lean verification of the Riemann Hypothesis

https://leanprover-community.github.io/blog/posts/riemann-hypothesis/
1025•g-b-r•19h ago•841 comments

Show HN: The Riemann Proof Handbook

https://github.com/tamnd/riemann-handbook
43•tamnd•3h ago•13 comments

Inkling-2-Mini in 5.4 GB Memory

https://github.com/ShinMegamiBoson/lookatmyquant
456•k__•15h ago•114 comments

Sandwich Simulator

https://stulle.app/
222•subdomain•9h ago•71 comments

Notes on the discrete Fourier transform (DFT)

https://eli.thegreenplace.net/2026/notes-on-the-discrete-fourier-transform-dft/
23•kouosi•2h ago•4 comments

Data Processing Incidents on Inference Providers

https://openrouter.ai/blog/announcements/data-processing-incidents-on-inference-providers/
141•sdko•7h ago•54 comments

Detonating a pile of lead azide

https://www.science.org/content/blog-post/detonating-huge-pile-lead-azide-really
604•beginning_end•20h ago•386 comments

If tiny 'primordial' black holes exist

https://phys.org/news/2026-11-tiny-primordial-black-holes.html
30•wglb•2d ago•1 comments

87% of the Anthropic power will come from gas and 11% from coal in 2028

https://betterdatacenterproject.com/2026/11/16/how-ai-is-powered-a-breakdown-of-byop-and-grid-power/
6•happosai•44m ago•1 comments

Getting the mind to steer the body to steer you

https://notnottalmud.substack.com/p/getting-the-mind-to-steer-the-body
265•jger15•1d ago•89 comments

Reversing the Next-Page Prefetcher in Skylake-X

https://devsh0.github.io/microarchitecture,/intel,/computer-architecture/2026/11/17/reversing-the...
8•todsacerdoti•3d ago•0 comments

My monitor was cutting my download speed by 75%

https://blog.tymscar.com/posts/studiodisplayethernet/
579•soheilpro•23h ago•270 comments

PcapAnalyzer – self-hosted pcap analyzer with 27 problem detectors

https://github.com/sebaandrada-cell/PcapAnalyzer
112•sebaandrada•11h ago•13 comments

Is 'fork' missing operation in sandboxes?

https://avrea.com/blog/avrea-sandboxes-computers-should-be-forkable
4•damezumari•2d ago•4 comments

The Mythology of Conscious AI

https://www.noemamag.com/the-mythology-of-conscious-ai/
59•Anon84•7h ago•116 comments

Fast-Anything: Don't rewrite it in Rust. Rewrite the 5% that's slow

https://github.com/EL4CTEO/fast-anything
25•BaselAshraf81•5h ago•10 comments

Split Radiance Cascades

https://www.jacktollenaar.top/articles/split-rc.html
31•ibobev•2d ago•0 comments

Pandex – Official European Law for AI Agents, over MCP

https://www.pandex.io
90•vasie•12h ago•21 comments

Advice for the next 100 Rust GUIs

https://linebender.org/blog/next-100-guis/
160•raphlinus•12h ago•59 comments

Upload2Shell (CVE-2026-125396)

https://pwn.ai/upload2shell
116•f311a•15h ago•56 comments

Show HN: Compile the same source for GPUs and CPUs

https://github.com/ThrudTheBarbarian/xc
10•spacedcowboy•1w ago•0 comments

LLMs can read and write executables byte by byte from a hex dump

https://sgiannopoulos.github.io/blog/machine-code-programming/
241•fortran77•3d ago•154 comments

Pion Interceptor: WebRTC for Hackers

https://pion.ly/blog/pion-interceptor-webrtc-for-hackers/
10•Sean-Der•3d ago•1 comments

Reaktiv Workbook – A spreadsheet where every cell is Python

https://workbook.bui.app/
18•buibuibui•3d ago•3 comments

GnuPG Security Advisory for GPGME

https://lists.gnupg.org/pipermail/gnupg-announce/2026q4/000517.html
251•gdgghhhhh•1d ago•101 comments

Shaping the Loops, Closing the Loops

https://revyl.com/blog/pattern-engineering/
25•based0x10•3d ago•9 comments

Hurried Announcement: Alessandro Masullo GRH

https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/
2414•jasondavies•1d ago•1174 comments

Tasklet (YC P26) Is Hiring Product and Agent Infra Engineers

https://tasklet.ai/careers
1•mayop100•12h ago
Open in hackernews

Extending a Language – Writing Powerful Macros in Scheme

https://mnieper.github.io/scheme-macros/README.html
92•textread•1y ago

Comments

neilv•1y ago
A few formatting changes might make this advanced example easier to understand:

    (define-syntax trace-let
      (syntax-rules ()
        [(trace-let name ([var expr] ...) body1 ... body2)
         (let f ([depth 0] [var expr] ...)
           (define name
             (lambda (var ...)
               (f (+ depth 1) var ...)))
           (indent depth)
           (display "(")
           (display 'name)
           (begin
             (display " ")
             (display var))
           ...
           (display ")")
           (newline)
           (call-with-values
               (lambda ()
                 body1 ... body2)
             (lambda val*
               (indent depth)
               (fold-left
                (lambda (sep val)
                  (display sep)
                  (display val)
                  " ")
                "" val*)
               (newline)
               (apply values val*))))]))
The biggest one is to make the rule template pattern variables all-uppercase. I also made a few other tweaks, including using indentation a little more, and naming the named-`let` variable as "loop" (I usually name it `loop` or prefix the name with `loop-` if there's more than one):

    (define-syntax trace-let
      (syntax-rules ()
        ((trace-let NAME ((VAR EXPR) ...) BODY1 ... BODY2)
         (let loop ((depth 0)
                    (VAR   EXPR) ...)
           (define NAME
             (lambda (VAR ...)
               (loop (+ depth 1) VAR ...)))
           (indent depth)
           (display "(")
           (display (quote NAME))
           (begin (display " ")
                  (display VAR)) ...
           (display ")")
           (newline)
           (call-with-values (lambda ()
                               BODY1 ... BODY2)
             (lambda val*
               (indent depth)
               (fold-left (lambda (sep val)
                            (display sep)
                            (display val)
                            " ")
                          ""
                          val*)
               (newline)
               (apply values val*)))))))
Incidentally, all-uppercase Scheme pattern variables is one of the all-time best uses of all-uppercase in any language. Second only to all-uppercase for the C preprocessor, where a preprocessor macro can introduce almost arbitrary text. Using all-uppercase for constants in some language that has constants, however, is an abomination.

(My suspicion of why Java did all-caps is that they were developing a language for embedded systems developers who were currently using C and C++, and they wanted to make it superficially look similar, even though it was an entirely different language. And then, ironically, the language ended up being used mostly by the analogue of a very different developer of the time: corporate internal information systems developers, who, as a field, didn't use anything like C. It's too late to save Java, but to all other language and API developers, please stop the insanity of all-caps constants, enum values, etc. It's not the most important thing that needs to jump out from the code above all other things.)

Y_Y•1y ago
FWIW, all-caps makes this look much worse to me. I understand that people like things like Hungarian notation, arrows over vector names, and shouting Common Lisp symbols. I understand the argument that it can make reading easier. I just can't appreciate that benefit, and it seems to me an ugly hack which obscures the abstract and general symbolic manipulation going on.

This is all highly subjective of course, de gustibus non disputandem.

neilv•1y ago
You mean aesthetically, in that interspersed all-caps makes the code visually less soothingly sensual?

I can sympathize, but let me make a non-aesthetic argument...

In large blocks of code, with all-caps, you can see at a glance where all the template substitutions are happening, and also instantly know as you're reading code what are variables and what are template substitutions?

I'm asking because one of my realizations in recent years is that not everyone reads or sees code the same way.

For example, maybe some people are stronger "visual" and some people are stronger "verbal".

For another example of a different in how people perceive and think, some people can visualize an object in their mind almost as if they're looking at it, but other people can only know and describe what it looks like without bringing a visual of it into their head.

With the benefit of the all-caps, I can glance at this and immediately see much of the structure of the template. Without all-caps, I'd have to work harder to find all the pattern variables, and the structure would be obscured.

For a bit kludgy practical matter, as I'm quickly looking at pieces of code in a template, with all-caps, I can look at a fragment of code in isolation and know what are and aren't pattern variables. Without that, I have to go read the top of the template clause (and read through any syntactic scopes of `let-syntax`) and get that in my head, until I get to the fragment of code I originally wanted to look at.

IDE support can make this unnecessary, with a hypothetical great IDE, with familiar syntax coloring. But still, if there is one thing that all-caps should be reserved for, it's something like this.

With all-caps, your code can be sensual, and the jolting all-caps bits are look out, potentially arbitrary code gets pasted into here.

mnemenaut•1y ago
https://github.com/rogerturner/scheme-macros/blob/main/examp... shows stepwise development of a trace-let [the `(example: (fn arg) => result)` forms are tests - see check-examples library]
Y_Y
•
1y ago
Since you asked, my objection is both aesthetic and semantic, though I was really referring to the semantic part above.

I think you've hit the nail on the head with this visual vs. verbal distinction.

I can add a few clarifying details. I don't use IDEs as much as basic text editors maybe with highlighting, and I try not to rely on any fancy features. It does worry me that the allcaps use you describe is (afaik) not known to the editor or interpreter, so if you make a mistake or the symbol gets out of sync with its meaning (re: pattern variables) you may have a false signal. Finally I'll say that in the end I can't suggest a good way to treat these special variables, and so maybe I don't get it, or tastes like mine would be better served by a different formalism for macros.