trfzx
Re:Heslington Brain
on Thursday October 26, 2023 @07:41AM (#38024261)
"Jim cleaned it up and recorded it but had a dentist's appointment that afternoon (for a filling) [...]" Sometimes Wikipedia really tries to relay all of the most important information.
Re:Ain't It Funny How the Knight Moves?
on Friday January 20, 2023 @06:38PM (#34461767)
The history is irrelevant here as well, you just need to know the next goal, which is always indicated.
Re:Wikipedia’s Redesign Is Barely Noticeable. That’s the Point.
on Thursday January 19, 2023 @12:58PM (#34443348)
I think they might mean most-frequently used of that user (I think the "suggested languages" already are supposed to work like that.) But that presumably requires an account.
Re:Wikipedia’s Redesign Is Barely Noticeable. That’s the Point.
on Thursday January 19, 2023 @12:45PM (#34443189)
The extra click is an inconvenience that they also noted themselves. But it definitely was designed with multilingual use in mind, see here https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improveme...
Re:Wikipedia’s Redesign Is Barely Noticeable. That’s the Point.
on Thursday January 19, 2023 @12:11PM (#34442760)
Because filling the space with overly long lines, as it used to do, makes for a horrible reading experience.
Re:The Problem with Macros
on Monday January 09, 2023 @02:33AM (#34307784)
Fascinating read.
I would have loked to see a quotation from the parts of the standard that are referred to here: "Although few implementations support its full generality in file compilation, a strict reading of the Common Lisp specification seems to imply that writing the following should be acceptable".
Re:Read this post ‘unless’ you’re not a Ruby developer
on Tuesday December 13, 2022 @04:45AM (#33966619)
I think the author would probably be fine with an if-not. It doesn't hide the double negation like unless.