News for hackers. Stuff that matters.

A comment on The lost cause of the Lisp machines. Parent comment

Re:The lost cause of the Lisp machines by iLemming on Thursday November 20, 2025 @11:12AM (#45994205)
> you're not very good at computers.

Yup, I guess I am not. Been coding for over 20 years, went through over a dozen different PLs and only Python - the best fucking friend who doesn't sugar coat it, tells you without stuttering - "you suck at this, buddy"

     # PEP 9001: Constructive Computing Feedback

     ## Abstract

     This PEP proposes a standardized error message for situations where Python interpreters shall inform the user of insufficient computational competence.

     ## Specification

     When a user attempts to execute Python code that supposedly should work but it doesn't, the interpreter shall emit:

         You're suck at computers
[ Parent | on HN ]
Re:The lost cause of the Lisp machines by ErroneousBosh on Thursday November 20, 2025 @02:31PM (#45996632)
> Yup, I guess I am not. Been coding for over 20 years

Wow, nearly as long ago as my first kernel module.

Then you ought to be able to figure out how to install one thing then, eh?

Just out of interest, what was it that was causing such a hassle? I expect it's not really relevant now, but it would be interesting to see how hard it would be to fix.

[ Parent | on HN ]
Re:The lost cause of the Lisp machines by iLemming on Thursday November 20, 2025 @02:40PM (#45996739)
It's not hard. It's just annoying to deal with this shit on constant basis. Like just the other day, the tests wouldn't pass locally, while they're passing on CI. I was scratching my head for sometime, turns out there was breaking change in csv.QUOTE_STRINGS or something, between 3.12 and 3.13 of Python. How the fuck did they manage to fix/improve fucking csv logic introducing a breaking change?
[ Parent | on HN ]
Re:The lost cause of the Lisp machines by whstl on Friday November 21, 2025 @10:06AM (#46005253)
I'm always suspicious of people who go "this is easy" as a way to put others down.

...especially when it's about problems that are universally accepted as not being trivial, and often require entire teams and ecosystems (Docker, Poetry, uv) to solve in scale.

[ Parent | on HN ]