Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
phoe-krk
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
82 ms
·
541.
▲
Show HN: Utility for creating, accessing, and managing namespaces in Common Lisp
(github.com)
4 points
by
phoe-krk
5y ago
|
0 comments
542.
▲
by
phoe-krk
5y ago
Yes, that too! I'd like to see how different Postgres techniques compare in general.
543.
▲
by
phoe-krk
5y ago
Just a fun question: is there a comparison that compares how well a simple PostgreSQL-based queue[0] fares against these specialized solutions? [0] https://blog.crunchydata.com/blog/message-queuing-using-nati...
544.
▲
by
phoe-krk
5y ago
Sure, that's always an option - same as Dylan, in a way!
545.
▲
by
phoe-krk
5y ago
As always, I'm very glad to see that structural, Common Lisp-style macro systems with the whole language available for macro construction, have been successfully adopted in other languages to the point where it's possible to expla
546.
▲
by
phoe-krk
5y ago
Alive. https://github.com/nobody-famous/alive https://marketplace.visualstudio.com/items?itemName=rheller....
547.
▲
by
phoe-krk
5y ago
Author here, it's a duplicate. The whole issue has already been on the front page and discussed extensively, including this article. See the comments at https://news.ycombinator.com/item?id=30017919
548.
▲
by
phoe-krk
5y ago
The "I'm sure it'll be fine in the end" tends to happen because people often do invisible but crucial work in hope to make it fine in the end.
549.
▲
by
phoe-krk
5y ago
In case of SectorLisp, that's good ol' BIOS I/O for interacting with the keyboard and screen. Having any other interface would require implementing it first - remember that SectorLisp is meant to run on bare hardware.
550.
▲
by
phoe-krk
5y ago
Quote from the article: > Others like the 5:2 diet (in which dieters eat a normal amount of food for five days before two days of eating only 25% of their usual calorie intake) focus more on the amount of food consumed, rather than the
551.
▲
by
phoe-krk
5y ago
How do you efficiently compile a language where the lexical environment must be fully available at runtime in order to be fully accessible by an F-expression? Having any Fexpr in a form to be compiled seems to prevent a lot of possible opti
552.
▲
by
phoe-krk
5y ago
As long as there is illegal content on the blockchain, they can simply state that you are hosting a node connected to a network that downloads and shares illegal content, which will be true, and therefore that you possess it, which will als
553.
▲
by
phoe-krk
5y ago
* The SICP chapter describing the use of the ambiguous operator: https://mitpress.mit.edu/sites/default/files/sicp/full-text/... * AMB manual: https://github.com/phoe/amb/b
554.
▲
Show HN: Implementation of John McCarthy's AMB operator in Portable Common Lisp
(github.com)
5 points
by
phoe-krk
5y ago
|
2 comments
555.
▲
by
phoe-krk
5y ago
You don't need hygiene (WITH-GENSYMS and so on) in Common Lisp macros in two situations: when you do not introduce any new bindings and when you only introduce bindings that the user is allowed to name themself. That's why the f
556.
▲
by
phoe-krk
5y ago
Author here. The repo link and simpler implementations were linked in sibling comments, so I'll just add a bit more explanation. The whole thing relies on the idea that Lisp macros can communicate: the outer macros can, via their expan
557.
▲
by
phoe-krk
5y ago
So do countless aeons of immeasurably heavenly and pleasurable experiences. It's hard to try and pick just a chunk out of something that's, for all practical purposes, infinite; even harder to try to judge it out of that infinite
558.
▲
by
phoe-krk
5y ago
International Communia Association ( https://www.communia-association.org/ ) is one group that I am aware of.
559.
▲
by
phoe-krk
5y ago
Lack of macros makes nothing impossible, but also makes many things harder. I think of them as code generators, tiny compilers on a micro scale; they are invoked by the proper compiler during compilation phase, as opposed to runtime, allo
560.
▲
by
phoe-krk
5y ago
> Hey, I didn't even realize who I was answering to. The best kind of comments are the ones which respond to the what as opposed to the who . :D
561.
▲
by
phoe-krk
5y ago
TIL. This is cursed. Have an upvote.
562.
▲
by
phoe-krk
5y ago
The thing is that trying to understand "the power of Lisp" via the toy interpreter from The Roots of Lisp[0] is like trying to understand "the beauty of the sea" after seeing a single five-minute YouTube video explaining
563.
▲
by
phoe-krk
5y ago
That's centralization, just replicated for redundancy.
564.
▲
by
phoe-krk
5y ago
So, in other words, unless you and everyone else uses a specially prepared and non-FOSS web3 browser which employs NFT DRM, there's no enforcement.
565.
▲
by
phoe-krk
5y ago
No idea, honestly. I think I am lucky and I do not get targeted by many phishing mails. (Let's see how much things will change now that this comment is public.)
566.
▲
by
phoe-krk
5y ago
Props for pass. (Is it GNU pass though? I can't see a mention of it being a GNU utility anywhere on https://www.passwordstore.org/ - I only see it's a "Unix" password manager.) I have a rented VPS whose
567.
▲
by
phoe-krk
5y ago
> The 3% of Linux desktop users would disagree. If we consider this statistic to be meaningful in this case, then 97% of people don't care. That's enough to be able to generalize. > What I really fail to understand is why pe
568.
▲
by
phoe-krk
5y ago
> I think most of the points about IRC are solvable See - it's "solvable" versus "solved". People seek solutions, not possibilities.
569.
▲
by
phoe-krk
5y ago
Yep, I agree. I simply wanted to notice that user inflation is also a problem on IRC, even though it's a smaller one - now even more so after Freenode is gone.
570.
▲
by
phoe-krk
5y ago
Yes, that's one other point that inflated the statistics a little bit - still, on the channels I was a part of, I kind of knew which names belonged to people who were active lurkers and which ones were names that I hadn't ever see
More ›