frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

An interactive map of Flock Cams

https://deflock.org/map#map=5/37.125286/-96.284180
266•anjel•2h ago•53 comments

MacBook Neo

https://www.apple.com/newsroom/2026/03/say-hello-to-macbook-neo/
1187•dm•6h ago•1537 comments

Father claims Google's AI product fuelled son's delusional spiral

https://www.bbc.com/news/articles/czx44p99457o
80•tartoran•1h ago•67 comments

Making Firefox's right-click not suck with about:config

https://joshua.hu/firefox-making-right-click-not-suck
169•mmsc•2h ago•107 comments

Something is afoot in the land of Qwen

https://simonwillison.net/2026/Mar/4/qwen/
359•simonw•5h ago•177 comments

Does that use a lot of energy?

https://hannahritchie.github.io/energy-use-comparisons/
18•speckx•31m ago•3 comments

Nobody Gets Promoted for Simplicity

https://terriblesoftware.org/2026/03/03/nobody-gets-promoted-for-simplicity/
732•aamederen•9h ago•421 comments

NanoGPT Slowrun: Language Modeling with Limited Data, Infinite Compute

https://qlabs.sh/slowrun
73•sdpmas•3h ago•8 comments

Moss is a pixel canvas where every brush is a tiny program

https://www.moss.town/
97•smusamashah•10h ago•10 comments

Data Has Weight but Only on SSDs

https://cubiclenate.com/2026/03/04/data-has-weight-but-only-on-ssds-blathering/
26•LorenDB•2h ago•14 comments

“It turns out” (2010)

https://jsomers.net/blog/it-turns-out
192•Munksgaard•6h ago•66 comments

Roboflow (YC S20) Is Hiring a Security Engineer for AI Infra

https://roboflow.com/careers
1•yeldarb•3h ago

Google ends its 30 percent app store fee and welcomes third-party app stores

https://www.engadget.com/apps/google-ends-its-30-percent-app-store-fee-and-welcomes-third-party-a...
77•_____k•1h ago•21 comments

Raspberry Pi Pico as AM Radio Transmitter

https://www.pesfandiar.com/blog/2026/02/28/pico-am-radio-transmitter
41•pesfandiar•3d ago•19 comments

Glaze by Raycast

https://www.glazeapp.com/
159•romac•7h ago•94 comments

Qwen3.5 Fine-Tuning Guide – Unsloth Documentation

https://unsloth.ai/docs/models/qwen3.5/fine-tune
200•bilsbie•8h ago•49 comments

The View from RSS

https://www.carolinecrampton.com/the-view-from-rss/
7•Curiositry•42m ago•1 comments

Faster C software with Dynamic Feature Detection

https://gist.github.com/jjl/d998164191af59a594500687a679b98d
27•todsacerdoti•2h ago•2 comments

Building a New Flash

https://bill.newgrounds.com/news/post/1607118
6•TechPlasma•45m ago•1 comments

Was Windows 1.0's lack of overlapping windows a legal or a technical matter?

https://retrocomputing.stackexchange.com/questions/32511/was-windows-1-0s-lack-of-overlapping-win...
5•SeenNotHeard•46m ago•1 comments

Libre Solar – Open Hardware for Renewable Energy

https://libre.solar
162•evolve2k•3d ago•46 comments

My Favorite 39C3 Talks

https://asindu.xyz/my-favorite-39c3-talks/
21•max_•3d ago•2 comments

MyFirst Kids Watch Hacked. Access to Camera and Microphone

https://www.kth.se/en/om/nyheter/centrala-nyheter/kth-studenten-hackade-klocka-for-barn-1.1461249
84•jidoka•7h ago•21 comments

The Rust Calling Convention We Deserve

https://mcyoung.xyz/2024/04/17/calling-convention/
4•cratermoon•3d ago•0 comments

Agentic Engineering Patterns

https://simonwillison.net/guides/agentic-engineering-patterns/
447•r4um•16h ago•252 comments

The Space Race's Forgotten Theme Park

https://daily.jstor.org/the-space-races-forgotten-theme-park/
12•anarbadalov•2h ago•1 comments

TikTok will not introduce end-to-end encryption, saying it makes users less safe

https://www.bbc.com/news/articles/cly2m5e5ke4o
378•1659447091•19h ago•365 comments

RFC 9849. TLS Encrypted Client Hello

https://www.rfc-editor.org/rfc/rfc9849.html
246•P_qRs•13h ago•121 comments

Emails to Outlook.com rejected due to a fault or overzealous blocking rules

https://www.theregister.com/2026/03/04/users_fume_at_outlookcom_email/
111•Bender•9h ago•70 comments

Government grant-funded research should not be published in for-profit journals

https://www.experimental-history.com/p/the-one-science-reform-we-can-all
302•sito42•6h ago•131 comments
Open in hackernews

Typed Lisp, a Primer

https://alhassy.com/TypedLisp.html
140•todsacerdoti•10mo ago

Comments

codr7•10mo ago
The main issue I have with CLs type checking is the clunky syntax and the fact that it looks different in different contexts.

I made an attempt to fix that for eli: https://github.com/codr7/eli#type-checking

rjsw•10mo ago
Your eli looks clunky to me.
codr7•10mo ago
Well, use something else.

And maybe ask yourself why you felt saying so was important to you.

dokyun•10mo ago

    (the number (+ 35 7))
is a lot less clunky than

    (+ 35 7)@Numeric
codr7•10mo ago
That's your opinion, I don't agree. And the other reason is I can use the same syntax wherever I want type checking.
epgui•10mo ago
Opinions aside, it is objectively an increase in syntactical complexity, and many people who love lisp enjoy its relative syntactical simplicity.

Whatever is gained in exchange for this additional syntactical complexity may not be valued in the same way by everyone.

So that almost certainly explains that reaction.

codr7•10mo ago
Yes, and a lot of people recognize the value of having a little bit of syntax in their Lisp.
klibertp•10mo ago
Yup. Somehow, I prefer[1]:

    (funcall #~s:gi/abc/def/ "Testing abc testing abc")
to the five lines of the equivalent made with macros, function calls, and keyword arguments.

I know all the problems with reader extensions, really. I understand being cautious. But at some point, you gotta wonder: what's the point of the programmable reader when you're unwilling to add programs to it?

[1] Let over Lambda: https://letoverlambda.com/index.cl/guest/chap4.html

kazinator•10mo ago
I'm reasonably happy with:

  1> (regsub #/abc/ "def" "Testing abc testing abc")
  "Testing def testing def"
HexDecOctBin•10mo ago
One problem with Lisp is everything, including variable bindings, increases the nesting level making the code illegible. Last thing you want is for the type declaration to have their own nesting.
zarathustreal•10mo ago
This is not necessarily true, you can pretty easily implement just about any syntax you want
dokyun•10mo ago
If you hate nesting, just do this

    (defun foo (&aux bar baz)
      (setq bar (quux)
            baz (xyzzy))
      ...)
epgui•10mo ago
The nesting level doesn’t necessarily impair legibility, it depends how it’s done. Nesting levels in homoiconic & referentially transparent languages have an impact more comparable to nesting levels in yaml or json than nesting levels in a language like python or javascript. The tradeoff weighs in a completely different way.

First you will usually want to write small chunks of code, instead of a large soup.

Second, you can make intentional decisions with your use of newlines in order to highlight specific aspects of the code.

I find clojure more readable than most other languages… However, bad code stands out horribly (which is actually great if you have at least one experienced engineer in the team- I’d argue there’s nothing worse than bad code that looks normal). Just like anything else, writing good lisp takes some skill.

Your specific editor and its configuration will also have a big impact on your experience.

sdsd•10mo ago
You'd love threading macros in Racket: https://docs.racket-lang.org/threading/index.html

It's like Unix pipes for functions:

  (~> "hello"
    (string-ref 1)
    (char->integer))
klibertp•10mo ago
Obviously, also available in CL, in Serapeum library[1]. Racket is credited in the docstring (since it's ~> instead of ->). Also, `nest` works very well for unnesting forms[2]

[1] https://github.com/ruricolist/serapeum/blob/master/control-f...

[2] https://github.com/ruricolist/serapeum/blob/master/REFERENCE...

sham1•10mo ago
Aside from the points that others have raised already, this sort of deep nesting can be seen as a feature instead of as a bug, since it can force you to think about refactoring the code into being less nested.
recursivecaveat•10mo ago
Are those compile-time type checks or runtime assertions?
codr7•10mo ago
Mix, similar to CL but slightly more runtime atm.
norman784•10mo ago
I don't particularly like the syntax for the types, but I can't also think of a better way to implement it without adding a special case in the parser/compiler for it, right now with your syntax I believe, correct me if I'm wrong, it can be implemented with a macro in any Lisp
NikkiA•10mo ago
praising 'loop' in the same post as describing lisp as 'elegant' shakes head
codr7•10mo ago
Some people seem to like it, and be very effective using it.

The problem is it's a walled garden, with its own quirky syntax; nothing that happens inside of loop is applicable outside, and the other way around.

shawn_w•10mo ago
I feel bad for people who haven't discovered ITERATE yet.
Jtsummers•10mo ago
ITERATE still breaks when you use `count` inside it, the built-in CL function. If they ever address that problem I'll get back to use it but having a time bomb in my programs isn't something I like.

Trivial example of breakage:

  (iter (for i from 1 to 10)
    (print (count i some-sequence)))
shawn_w•10mo ago
Breaks how? I'm on my phone, not a computer right now and can't test, but that should call the CL function - ITERATE uses `counting` for that particular operation to avoid conflicts; see https://iterate.common-lisp.dev/doc/Gathering-Clauses.html

Or is the documentation wrong?

Jtsummers•10mo ago
Apparently this is a quicklisp problem, they haven't updated the release since 2021 when it was still broken.
shawn_w•10mo ago
I just grabbed the latest ITERATE source off of its gitlab repository, and, yeah, that bit is still giving an error:

      Iterate, in (COUNT I SOME-SEQUENCE): Missing value for SOME-SEQUENCE keyword
as well as

    WARNING:
       COUNT appears to be used as an ITERATE clause keyword, in this sexpression: (COUNT I SOME-SEQUENCE).
       This use is now deprecated and will cease to be supported in a future version. Please use the alternative keyword COUNTING instead. If you intended COUNT to be interpreted as a function call, instead of an ITERATE clause, you must find an alternative way of calling it, at present, perhaps by using FUNCALL or APPLY.
Have to use

    (iter (for i from 1 to 10)
        (print (funcall #'count i some-sequence)))

Guess the documentation /is/ wrong (for now, until the code finishes catching up)
Jtsummers•10mo ago
Well, some-sequence was obviously an example, you'd have to fill it in with an actual sequence. Put in '(1 2 3) instead or assign something to it.

But yeah, that's still not something I intend to use if they make you work around what should be plain Common Lisp.

shawn_w•10mo ago
I had a some-sequence variable defined.

(Using a literal list or vector gives a different error)

BoingBoomTschak•10mo ago
It's been marked as deprecated for some time, but still needs manual removal as of now: https://gitlab.common-lisp.net/iterate/iterate/-/blob/master... (removing https://gitlab.common-lisp.net/iterate/iterate/-/blob/master... should work, I think).

Still better than the loop abomination, IMO.

kazinator•10mo ago
I made a loop macro using the C preprocessor, for the Awk language.

I had to rub my own eyes to believe that such a thing is possible.

It comes with over twenty useful clauses. Clauses are programmer-definable.

Clauses can combine in parallel or nested/cross-product iteration.

https://www.kylheku.com/cgit/cppawk/about/

Jach•10mo ago
I'll never understand the love for iterate. Look at these comparisons: https://github.com/sabracrolleton/sabracrolleton.github.io/b... For almost all of them, it's the same guy, just more parens. Nothing to love/hate for one or the other, it's just preference, though one is built-in.
shawn_w•10mo ago
Looks more lispy because the parens. Plus it's extendable unlike LOOP, so you can make it work with your own data types. And a few other nice features like being able to collect into a vector or other sequence, not just lists.
BoingBoomTschak•10mo ago
The big plus for me is that the ad-hoc if/when/do are removed in favour of the standard operators, without the horrible then/else/end/and dance.

Then you got all the life-improving goodies (in-{sequence,string,file,stream}, index-of-*, previous, etc...) that really add up to something.

kagevf•10mo ago
My opinion of LOOP started to change when I read (the much maligned) "Land of Lisp" and went over that "periodic" diagram in TFA. Seeing the elements of LOOP broken down like that went a long way to get me to overcome my original aversion to it.
Jach•10mo ago
Who is maligning Land of Lisp?
kagevf•10mo ago
Here's an example: http://metamodular.com/Books/land-of-lisp.html
Jach•10mo ago
Huh, didn't realize that beach didn't like it so strongly. Still, hardly "much maligned"... My impression was that most people enjoyed it, even though it definitely has some weaknesses and could (especially now 15 years later) use a second edition, if for no other reason than to move off CLISP to SBCL. This seems supported by its high reviews on Amazon and GoodReads. (Of course overall I liked it too, and we got the best music video about lisp out of it.) FWIW my own criticisms were largely style-based: too much of it felt like Scheme code rather than Lisp code, even outside of emphasizing/educating about the more primitive features, with lots of things like inner functions, recursion where looping would have IMO been clearer, and so much use of raw car/cdr/caadr/caddr/whatdr instead of more clearly structured structs or classes or just helper functions called intuitive things like get-foo. (The book Calendrical Calculations: The Ultimate Edition uses lists for all its data structures but helpfully creates many functions to both construct and access their parts. e.g. generic dates are a (year month day) list, but the definition and exclusive use of standard-year, standard-month, and standard-day for getting at them would let one refactor it into a class. There are also functions like gregorian-date, julian-date, and egyptian-date that have exactly the same implementation (making a list of the 3 passed params) but serve as 'typed' list constructors, and indeed could be refactored into something that carried along type information without changing other code.)
kagevf•10mo ago
I like LoL alright too. I was only maybe a year or so into CL when I read it, so I didn't really notice a lot of what it's criticized for. On the one hand, I'm a little sad that I see it bagged on so much (that link from beach's site, IRC, reddit) since I felt I got decent enough value out of it, but OTOH it's good and healthy to point out problems.

The abstractions used in Calendrical Calculations sound good - and echo what I've seen elsewhere - so, based on your comment I'm now more likely to read it, so thank you for that.

Jtsummers•10mo ago
https://www.cambridge.org/us/universitypress/subjects/comput...

The source code is available there.

kagevf•10mo ago
Thank you, I'll check it out!
breadchris•10mo ago
I have really fallen in love with LISP recently, specifically clojure. A strong type system is really needed for it to make me feel like I can confidently develop with it.
vindarel•10mo ago
just get Common Lisp with this new Clojure collection and sequence API! https://github.com/dtenny/clj-coll
nextos•10mo ago
A modern CL that borrows ideas from Clojure, and with a strongly typed language (Coalton) also available is indeed very appealing!
vosper•10mo ago
Have you (or anyone else reading this) used Coalton? What's your experience been like? Seems quite appealing to me.
Y_Y•10mo ago
The language looks amazing on paper, the install process (last I tried) was a nightmare of fighting quicklisp.
klibertp•10mo ago
That's on quicklisp, not Coalton. Honestly, quicklisp is one of the worst parts of CL nowadays (right after the lack of coroutines[1], which is by far the worst offender.) It should have been replaced a long time ago. ASDF3 provides a lot of flexibility, and quicklisp uses maybe 15% of its capabilities. There are reasons why it's still so bad, but it gets less and less excusable each year :(

[1] Does anybody know how to ping Kartik Singh about the coroutines implementation in SBCL? Apparently, he made an experimental port of the green threads implementation from CMUCL, but I can't find it anywhere online, nor any obvious way to catch anyone involved. Is the mailing list the only way?

boogsbyte•10mo ago
From what I heard he's not working on it anymore but the code can be found here:

https://github.com/kartik-s/sbcl/blob/coroutines/src%2Fcode%...

klibertp•10mo ago
Thank you!! I was very interested in `convert-thread-to-coroutine` - I saw it on the ELS presentation, and when I went spelunking in the CMUCL codebase, I found the prototypes for `fork` and `resume`, but (probably because CMUCL is single-threaded?) nothing that would suggest how that `convert...` should look like.

Why is there so little interest in green threads/coroutines in CL community? cl-cont really isn't something to point to when asked about C10K problem... or yield/yield*... or async/await...

boogsbyte•10mo ago
There's great interest for it, not little. The challenge is who can do compiler programming, add a production ready implementation as contrib SBCL package, and maintain it?
klibertp•10mo ago
Hm, my impression is based on the lack of posts or articles with people demanding this to be a feature. I searched, and it just doesn't seem to come up in discussions, and when it does, it's invariably about cl-cont and problems with it.

The first implementation doesn't need to be production-ready. And the maintenance burden (along with polishing the implementation and porting to other architectures) could be shared by a few people and done over time. Having a starting point in the form of CMUCL code (already adapted to SBCL!) is the perfect opportunity for everyone interested to chime in: enough voices in favor could convince someone capable to continue the work. Yet, there are literally just 3 comments under the ESL presentation video, and it's not mentioned anywhere else...

boogsbyte•10mo ago
It's mentioned on X and Discord plenty, but you're right about cl-cont.

The first few steps would be building on top of this work and reaching out to the SBCL maintainers via the mailing list to see what it takes to get this merged in.

nextos•10mo ago
My experience is good, but I have only written smallish programs. Documentation is pretty polished.

Installation-wise, NixPkgs is fairly straightforward.

lucyjojo•10mo ago
there is typed clojure out there if you want

https://typedclojure.org/

bmitc•10mo ago
There is Typed Racket.
jodleif•10mo ago
You could also consider getting into pre/post conditions and specs - helps a lot especially at points with user/data input
gitroom•10mo ago
honestly i kinda love when deep dives like this pop up, makes me rethink stuff i thought i'd settled on - you think things ever get simple with lisp or it always stays quirky no matter how you do it
wizzard0•10mo ago
of all things, this is the most beautifully formatted and organized LISP guide i've ever met.
eggy•10mo ago
You should check out Shen[1]. It is a portable functional programming language. Optional type checking and it solves my affair with Lisp and Haskell. It is a Lisp.

[1] https://shenlanguage.org/

klibertp•10mo ago
It needs a lot more good tutorials about its type system. Lacking the background in whatever subfield of math that would help here, I couldn't type my way out of a wet paper bag in it. I'd love a concise, down-to-earth, exposition of the type system "for the working programmer". It's just so different than anything else I know (from Haskell to Prolog) that I had a really hard time understanding Shen's type system.
eggy•10mo ago
You're right: Shen's mathematical underpinnings (sequent calculus, dependent type theory) can intimidate programmers without a formal logic background. I bought the "The Book of Shen" (TBOS) revision 1 and revision 3. Revision 4 is available on the website. It's a great book with some CS history, logic, and development of Shen from Qi as well as how everything works in Shen including the type system.

Shen uses a dependently typed Sequent-Calculus based Type System (SCTS). It uses type rules vs. type classes, and type checking is optional, you can turn it on or off. Haskell's type inference makes things a bit simpler, and is a battle-tested static type system with excellent type inference which lends itself better for functional programming and large-scale software engineering (for the moment). Shen's TC is more expressive, but requires more effort.

Aditya Siram has some old but goody YT videos on Shen.

klibertp•10mo ago
I wanted to buy it - I don't remember exactly, but I think I couldn't find an e-book version, and the paper one was expensive and didn't even ship to my country :( I hope to be wrong on that, though, do you know if there's an ebook available from somewhere?
eggy•10mo ago
Other than the online version (4th edition), I don't know of any other place to get it. Yes, the paperback was expensive, but I bought it anyway. It proved to be very informative and more substantive than I had thought. I believe the 5th edition is almost ready for publication.
klibertp•10mo ago
> Other than the online version

I'm an idiot. I looked at this page: https://shenlanguage.org/TBoS/tbos.html many times, tried clicking on the table of contents, realized that chapter titles are not links, and went away thinking it's only the ToS for promotional purposes. I only realized that the page numbers are links just now. To my defense, they don't differ in color that much and lack the underline that often marks links. Still, a HUGE facepalm :D Thanks for mentioning this and making me realize my own stupidity :)

eggy•10mo ago
Glad you found it. I've done much worse, believe me!

If you have any questions check out the Google Groups (no Groups comments!) for Shen. I am eager to see the 5th edition, and I will probably buy the print version.

droideqa•10mo ago
I had such high hopes for Shen but the licensing shenanigans at the beginning prevented it from having a great, large open source community.
eggy•10mo ago
It's resolved. I helped support it for a brief time for the SP version, which is now integrated into the latest version. You're right though, that this put many people off.