frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Carnegie Mellon is putting computer science courses on YouTube for free

https://www.cs.cmu.edu/learn/
1687•pcompeau•15h ago•228 comments

VisualBasic.World: A gallery of Planet Source Code programs from 1997 to 2012

https://visualbasic.world/
68•broast•1d ago•25 comments

Japan's Hometown Tax (2018)

https://www.kalzumeus.com/2018/10/19/japanese-hometown-tax/
69•waximabbax•1d ago•33 comments

BugMeNot has closed

https://www.bugmenot.com/
590•lode•14h ago•269 comments

Optimizely compromised, served malware on Zoom, GitLab

https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/
416•kristjansson•13h ago•168 comments

Nimony: A New Compiler for Nim

https://nimony.org/
89•Fervicus•1d ago•32 comments

Rows vs. Columns: How different are they, really?

https://spiraldb.com/blog/rows-vs-columns
15•eatonphil•4d ago•5 comments

If an App Asks for Full Disk Access or System and App Protection Override

https://support.apple.com/en-us/149699
150•jshier•10h ago•84 comments

How the Claude Code team thinks about verification

https://claude.dev/blog/how-the-claude-code-team-thinks-about-verification/
52•craigmart•2h ago•65 comments

Why 3dfx 1 cards had such a washed out color output?

https://twitter.com/id_aa_carmack/status/2122478083319992513
178•mfiguiere•12h ago•53 comments

New Evidence Shows School Phone Bans Are Gradually Improving Test Scores

https://www.nytimes.com/2026/11/17/upshot/school-phone-bans-study-scores.html
20•donohoe•44m ago•0 comments

Chemistry is Actually Geometry

https://chillphysicsenjoyer.substack.com/p/chemistry-is-actually-geometry
254•sebg•16h ago•117 comments

OpenCode Browse

https://opencode.ai/product/browse
291•mfiguiere•15h ago•165 comments

Turbo Pascal Compiler Written in Turbo Pascal

https://turbo51.com/compiler-design/tpc16-turbo-pascal-compiler-written-in-turbo-pascal
9•andsoitis•1d ago•0 comments

Frame – 31.5" color ePaper display

https://trmnl.com/blog/introducing-frame
446•geerlingguy•20h ago•314 comments

Jiff 1.0: A datetime library for Rust

https://burntsushi.net/jiff/
402•burntsushi•19h ago•88 comments

Comcast's "fiber-powered Wi-Fi" is cable, AT&T says in false advertising case

https://arstechnica.com/tech-policy/2026/11/comcast-falsely-advertises-cable-internet-as-fiber-po...
160•jaredwiener•15h ago•134 comments

What is w2rt6byl5nf1opmc-a.com?

https://jack.cab/blog/siterate
367•dverlaeckt80•22h ago•154 comments

The Fossils That Haunted Lovecraft

https://paleonerdish.wordpress.com/2026/10/30/halloween-special-xiv-the-fossils-that-haunted-love...
47•BigTTYGothGF•1d ago•14 comments

Microsoft blames monster email outage on software defect introduced in July fix

https://www.theregister.com/saas/2026/11/16/microsoft-blames-monster-email-outage-on-software-def...
352•Bender•23h ago•262 comments

Grazing sheep in fields with solar arrays

https://news.cornell.edu/stories/2026/10/sheep-grazing-solar-fields-offers-farmers-economic-ecolo...
284•PaulHoule•19h ago•287 comments

Test/verification technique effectiveness with Astra

https://danluu.com/astra-testing/
59•luu•1d ago•9 comments

Stop Filming in Log?

https://digitalfilms.wordpress.com/2026/11/15/stop-filming-in-log/
81•dabinat•1d ago•82 comments

Formal Verification Is Not Verifiable

https://alperenkeles.com/posts/formal-verification-is-not-verifiable/
131•zdw•2d ago•42 comments

Do Repeat Yourself

https://arcentry.com/blog/do-repeat-yourself/
107•max_sendfeld•1d ago•36 comments

Windows 11 is collecting data on which coding agents and developer tools you use

https://xusheng.dev/posts/windows-coding-agent-telemetry/
643•cwaffles•13h ago•497 comments

Launch HN: Axonnic (YC F26) – Sleeves that track fingers and estimate force

47•arshpatankar•16h ago•24 comments

Squircles

https://linebender.org/wiki/curves/squircle/
199•raphlinus•1d ago•54 comments

Technical issue at JPMorgan Chase triggers online banking delays for US banks

https://apnews.com/article/bank-outage-chase-wells-fargo-truist-50fee2693c22f597fa6ca51a97ef2cda
788•samk3nny•17h ago•658 comments

Spamhaus new email sender requirements in November

https://www.spamhaus.org/sender-guidelines/
121•computer23•14h ago•116 comments
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.