HNHacker News
TopNewBestAskShowJobs

phoe-krk

9,382 karma · joined February 10, 2017

Lisp hacker. https://phoe.github.io

Author of "The Common Lisp Condition System", published by Apress. https://www.apress.com/us/book/9781484261330

meet.hn/city/50.0619474,19.9368564/Krakow Socials: - github.com/phoe - functional.cafe/@phoe ---

submissionscomments
phoe-krk··on WASM 3.0 Completed
Speaking for CL, it seems so for me.

The whole magic about CL's condition system is to keep on executing code in the context of a given condition instead of immediately unwinding the stack, and this can be done if you control code generation.

Everything else necessary, including dynamic variables, can be implemented on top of a sane enough language with dynamic memory management - see https://github.com/phoe/cafe-latte for a whole condition system implemented in Java. You could probably reimplement a lot of this in WASM, which now has a unwind-to-this-location primitive.

Also see https://raw.githubusercontent.com/phoe-trash/meetings/master... for an earlier presentation of mine on the topic. "We need means of unwinding and «finally» blocks" is the key here.

phoe-krk··on Generative AI's failure to induce robust models of the world
"Version control systems", in case of AI, mean that their knowledge will stay frozen in time, and so their usefulness will diminish. You need fresh data to train AI systems on, and since contemporary data is contaminated with generative AI, it will inevitably lead to inbreeding and eventual model collapse.
phoe-krk··on Sourcehut Moving to Europe
Dupe: https://news.ycombinator.com/item?id=44365246
phoe-krk··on Harper – an open-source alternative to Grammarly
Which effort? Learning a language is something that can't be eliminated. Everyone needs to do it on their own. Writing grammar checking software, though, can be done few times and then copied.
phoe-krk··on Harper – an open-source alternative to Grammarly
At this point we're already using different definitions of grammar and vocabulary - are they discrete (as in a rule system, vide Harper) or continuous (as in a probability, vide LLMs). LLMs, like humans, can learn them on the fly, and, like humans, they'll have problems and disagreements judging whether something should be highlighted as an error or not.

Or, in other words: if you "just" want a utility that can learn speech on the fly, you don't need a rigid grammar checker, just a good enough approximator. If you want to check if a document contains errors, you need to define what an error is, and then if you want to define it in a strict manner, at that point you need a rule engine of some sort instead of something probabilistic.

phoe-krk··on Harper – an open-source alternative to Grammarly
When you do writing as a form of art, rules are meant to be bent or broken; it's useful to have the ability to explicitly write new ones and make new forms of the language legal, rather than wrestle with hallucinating LLMs.

When writing for utility and communication, though, English grammar is simple and standard enough. Browsing Harper sources, https://github.com/Automattic/harper/blob/0c04291bfec25d0e93... seems to have a lot of the basics already nailed down. Natural language grammar can often be represented as "what is allowed to, should, or should not, appear where, when, and in which context" - IIUC, Harper seems to tackle the problem the same way.

phoe-krk··on Harper – an open-source alternative to Grammarly
Yes, precisely. This "less than a decade" is magnitudes above the hours or days that it would take to manually add those words and idioms to proper dictionaries and/or write new grammar rules to accomodate aspects like skipping "g" in continuous verbs to get "bussin" or "bussin'" instead of "bussing". Thank you for illustrating my point.

Also, it takes at most few developers to write those rules into a grammar checking system, compared to millions and more that need to learn a given piece of "evolved" language as it becomes impossible to avoid learning it. It's not only fast enough to do this manually, it also takes much less work-intensive and more scalable.

phoe-krk··on Harper – an open-source alternative to Grammarly
> Please share your reasoning that led you to this conclusion -- that natural language "evolves slowly".

Languages are used to successfully communicate. To achieve this, all parties involved in the communication must know the language well enough to send and receive messages. This obviously includes messages that transmit changes in the language, for instance, if you tried to explain to your parents the meaning of the current short-lived meme and fad nouns/adjectives like "skibidi ohio gyatt rizz".

It takes time for a language feature to become widespread and de-facto standardized among a population. This is because people need to asynchronously learn it, start using it themselves, and gain critical mass so that even people who do not like using that feature need to start respecting its presence. This inertia is the main source of slowness that I mention, and also and a requirement for any kind of grammar-checking software. From the point of such software, a language feature that (almost) nobody understands is not a language feature, but an error.

> You also seem to be making an assumption that natural languages (English, I'm assuming) can be well defined by a simple set of rigid patterns/rules?

Yes, that set of patterns is called a language grammar. Even dialects and slangs have grammars of their own, even if they're different, less popular, have less formal materials describing them, and/or aren't taught in schools.

phoe-krk··on Harper – an open-source alternative to Grammarly
Natural languages evolve so slowly that writing and editing rules for them is easily achievable even this way. Think years versus minutes.
phoe-krk··on A different take on S-expressions

    (fst-atom """   trd-atom frt-atom
      """     00001
      asdf    00002 """    fth-atom)
      qwer    00003 hahaha
      zxcv      """ hehehe
      """           hohoho
                    """
I'm not sure I'd like the above to be parseable.
phoe-krk··on A different take on S-expressions
Truth be told, you can intercept the reader in Common Lisp, too, and here it actually makes some sense since the 2D value is immediately visually grokkable as an ASCII-art table. The proposed 2D sexpr notation does not have this.
phoe-krk··on A different take on S-expressions
Lisp programmer here.

Traditional S-expressions, by their definition, ignore most of whitespace; additionally, reading sexprs is always a linear operation without the need to backtrack by more than one character.

The suggestion from this post violates both assumptions by introducing a 2D structure to code. To quote this post's examples, it requires the multiline string in

    (fst-atom """   trd-atom)
              00001
              00002
              00003
                """
to be fully read before TRD-ATOM. It also forces the reading function to jump up and down vertically in order to read the structure in

    * (                               )  
    *   e (           ) (           )    
    *   q   m (     )     p (     )     *
            u   a a       o   a 2       *
            l             w             *
The author also states that

    (eq (mul (a a)) (pow (a 2)))
is less readable than

    * (                                                  )  
    *   *eq* (                   ) (                   )    
    *          *mul* (         )     *pow* (         )     *
                       *a* *a*               *a* *2*       *
                                                           *
Then there's the ending passage:

> we hope that the introduced complexity is justified by the data readability expressed this way.

I cannot force myself to read this post as anything but a very poor Befungesque joke.

phoe-krk··on Medical aid in dying, my health, and so on
Yes, it is indeed a risk. It is much better to only allow people "not of sound mind" to kill themselves the way they currently do - via brutal, goresome, and unexpected methods, which also often endanger others as well.

/s

phoe-krk··on Why is PS3 emulation so fast: RPCS3 optimizations explained [video]
It's unbelievable that over the whole course of PS3's lifespan we've gone from "we will never be able to emulate this at full speed, the hardware is too slow and the Cell architecture too alien" to "why is PS3 emulation so fast, optimizations explained". I've been loosely tracking various emulators' progress and it's hats off with regards to the ingenuity behind all of the mechanisms that make it possible to emulate things fast enough.
phoe-krk··on Trump administration backtracks on Harvard foreign student policy
If we have a Google Graveyard [0], perhaps we need a Trump Policy one - showing how many days his various survived before being reverted or struck down by courts.

[0] https://killedbygoogle.com/

phoe-krk··on Study finds a 50% decline in the use of semicolons over the last two decades
It's certainly a crisis in the Lisp world; everyone seems to be writing fewer comments.
phoe-krk··on Why does Debian change software?
Any such leftover behavior is going to be a reportable and fixable bug then.
phoe-krk··on Unauthenticated Remote Code Execution in Erlang/OTP SSH
CWE-306, Missing Authentication for Critical Function, linked in the report seems to suggest the same. The score of 10.0 is damn spicy, too - you just ask the server to execute something for you, and it does so, no questions asked.
phoe-krk··on Autology: A Lisp with access to its own interpreter
Thanks! I hope it serves you well.
phoe-krk··on Autology: A Lisp with access to its own interpreter
https://pvk.ca/Blog/2014/03/15/sbcl-the-ultimate-assembly-co...
phoe-krk··on Posthog/.cursorrules
The prayers and vigorous side-smacking are already here; only incenses and sanctified oils remain to be seen.

Praised be the Omnissiah.

phoe-krk··on LeetCode but You Can Force People to Code in Light Mode
Going for "deletio" too many times causes the JS to go into a loop.

Still, fun.

phoe-krk··on Multiple Russia-aligned threat actors actively targeting Signal Messenger
As someone living in Poland and tracking the developments in the US, when I used the word "plausible", I meant it.
phoe-krk··on Multiple Russia-aligned threat actors actively targeting Signal Messenger
> I heard he also blames Poland for being invaded and starting WWII.

This one is fake, even if plausible. https://www.der-postillon.com/2025/02/ueberfall-auf-polen.ht... - Der Postillon is equivalent to US's The Onion.

phoe-krk··on Mass market non-fiction has bad incentives
Reading this most made me immediately think that there's more than just misalignment of the writer and the reader: there's also the incentive of the publisher, which might be misaligned with either, or both, or simply utterly puzzling and confusing.

Anecdata: as glad as I am for Apress for working with me and releasing my own book about a part of Common Lisp (which is, technically, non-fiction!), I still cannot fathom their re-release of "Interpreting LISP" [1] - a book that I hated to give a zero-star rating on Reddit [2] but that I can only warn people about, if I am to be acting in good faith.

[1] https://link.springer.com/book/10.1007/978-1-4842-2707-7

[2] https://www.reddit.com/r/lisp/comments/6qc61v/second_edition...

phoe-krk··on [dead]
He's not the Justice Minister of Poland, he's the former Justice Minister of the previous government of the previous ruling party. He isn't and hasn't been Justice Minister since 2023.

Plus, he wasn't arrested, only detained so that he could answer before a commission of Polish parliament.

Techdirt, please get your journalism together. These details are important.

phoe-krk··on Practical use of the null garbage collector (2018)
(2018)
phoe-krk··on Maxima in the browser using Embedded Common Lisp on WASM
It's called "Embeddable Common Lisp", not "Embedded Common Lisp".

https://ecl.common-lisp.dev/

phoe-krk··on New speculative attacks on Apple CPUs
> We disclosed our results to Apple on May 24, 2024. Apple’s Product Security Team have acknowledged our report and proof-of-concept code, requesting an extended embargo beyond the 90-day window. At the time of writing, Apple did not share any schedule regarding mitigation plans concerning the results presented in this paper.

The vulnerability is over half a year old and over a quarter over the embargo window.

phoe-krk··on Ask HN: Why buy domains and 301 redirect them to me?
They'll weaponize them at some point. How exactly is to be seen, but if people associate your product with domains you do not control (e.g. via SEO searches and hyperlinks left in public places), then everyone is on the hook the moment these domains stop redirecting to your service.
← PreviousPage 3 of 34Next →