lisper

40 ms·

391.
by lisper 1y ago
I have a patent on a faster-than-light communications system: https://patents.google.com/patent/US7126691B2/en Obviously it doesn't actually work. I submitted the application as an experiment to see how hard
392.
by lisper 1y ago
Environmentally-sensitive garbage disposal is expensive. Not everyone can afford it.
393.
by lisper 1y ago
Yeah, that was meant to be a joke. Even if we were to collide, it wouldn't happen for a few billion years. Our sun will be a red giant by then. Earth will no longer exist.
394.
by lisper 1y ago
Damn, I was really looking forward to seeing Andromeda up close. Oh well.
395.
by lisper 1y ago
Not for me. No idea why. Maybe this doesn't play well with NoScript or AdBlock.
396.
by lisper 1y ago
I'm using Firefox on a Mac.
397.
by lisper 1y ago
Aargh! I hate it when people quote text as images because it makes it impossible to cut and paste. > Jet black/Jet Blue ... catnap/dognap My favorite examples are how prepositions can change the meanings of idioms. For exampl
398.
by lisper 1y ago
I know very little about Julia. It is on my list of Things To Look Into Some Day. > type stability [is] not stupid ideology unless you consider high-performing numerical code stupid ideology. "Stupid ideology" may have been pu
399.
by lisper 1y ago
> you want to say "my program is correct, now run it for me" No. I want to say "Run this program whether or not it is correct because I just want to see what it does in its current state." Sometimes I know that it
400.
by lisper 1y ago
You are correct. I was talking about writing compilers in CL in general, not specifically for the 6811.
401.
by lisper 1y ago
> Lean and Rocq Yep, I get that. But I don't think of these as programming languages, I think of them as proof assistants. Related for sure, but different enough that IMHO it is unwise to conflate them. > SQL Again, a whole dif
402.
by lisper 1y ago
> ERROR: DomainError with -1.0: > sqrt was called with a negative real argument but will only return a complex result if called with a complex argument. Try sqrt(Complex(x)). This is the sort of thing that drives me absolutely nuts
403.
by lisper 1y ago
That's what Common Lisp itself is: one Lisp to rule them all. And it actually works pretty well. There are libraries that work across a wide variety of CL implementations.
404.
by lisper 1y ago
> Fowler said he didn't know if the database was created legitimately and then accidentally exposed or intentionally used for malicious reasons. Seriously? In what possible world can a collection of plain-text login credentials exi
405.
by lisper 1y ago
> your compiler has to handle each type of expression sooner or later, so this isn't as big a deal as it might sound It's a bigger deal than you think. Not only can you leverage the CL parser on the front end so that you can c
406.
by lisper 1y ago
I think we are more or less in violent agreement here. Our disagreements are on the fringes, and could well just be a result of my ignorance or misunderstanding. That said... > invoking incompleteness is like invoking Russell’s paradox
407.
LLM-based programming tool figures out how to improve its own code(twitter.com)
1 points by lisper 1y ago|0 comments
408.
by lisper 1y ago
Thanks for the kind words!
409.
by lisper 1y ago
> Specifically, the two views of typing. That was in the other article, the one I didn't comment on at all. There are two reasons I didn't comment on it. First, I don't actually understand what the author means by things
410.
by lisper 1y ago
Heh, thanks! But it really was a bit of whinging when I wrote it. Lisp in space was ultimately a failure, and I've always had very mixed feelings about telling the story. But I'm glad it resonates.
411.
by lisper 1y ago
Wow. I never imagined that this bit of whinging would end up being my ticket to immortality. :-/
412.
by lisper 1y ago
It's a little more complicated than that, and I can't fully explain it in an HN comment. I'd have to give you a crash course in compiler design. But the TL;DR is that if you're building a custom language, Lisp gives yo
413.
by lisper 1y ago
Of course! :-)
414.
by lisper 1y ago
> arguably achieves the worst of both worlds The author makes a number of unfounded claims, including: > there is huge benefit in throwing away the prototype This is at odds with: https://en.wikipedia.org/wiki/Sec
415.
by lisper 1y ago
I'm not sure what you mean by "compiling down Lisp code." Can you elaborate? That phrase doesn't appear in either article.
416.
by lisper 1y ago
Type declarations in ANSI CL are promises you make to the compiler in order to allow it to generate faster code. The compiler can also use this information to generate compile-time warnings and errors, but it is not required to. This make
417.
by lisper 1y ago
I left JPL in 2004, never to return :-) I'm mostly retired now but I have a part-time consulting gig that uses CL for developing a bespoke custom chip design tool.
418.
by lisper 1y ago
We used Forth back in the day as well, running on 6811 microcontrollers. Forth was also used on the Galileo Magnetometer, and we used Lisp to develop a patch for it in flight. https://github.com/rongarret/gll-mag-patch
419.
by lisper 1y ago
Author here. This pops up on HN regularly, which I'm happy to see, but it's pretty dated at this point. Here is a more recent update: https://blog.rongarret.info/2023/01/lisping-at-jpl-revisited... And
420.
by lisper 1y ago
I think there may be a terminological disconnect here. S-expressions and canonical S-expressions are not the same thing. S-expressions (non-canonical) are a comparable to JSON, intended to be read and written by humans, and actually muc

More ›