Programming thread

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
i got to thinking and i think josh probably pronounces sql as "squill"
I think SQL should be pronounced "skull", and GUI should be pronounced "gwee", while GIF should be spelled out as "jee eye eff".

Also, character should be pronounced with a "tsh" sound at the start but only when used in a programming context.
 
I have a pathological need to mispronounce GIF as 'ghife' as in 'strife'.
SQL is 'sequel.'
GUI is 'gooey'.
I started calling gifs "yif"s. It pisses off everyone.
For me SQL is es ku ell. (Seems fairly common in the german speaking parts)
Also, character should be pronounced with a "tsh" sound at the start but only when used in a programming context.
As in the "char" data type? That's how it's pronounced already.
 
I know that this isn't the place for tech help, but I'm completely stumped by this. I committed a <10Kb Python file to GitHub, but it refuses to display the code, only showing the option to download it (View Raw). 1752290244764.webp
Is it because committing with Git LFS flags the files? It didn't do this with other files I committed, just the most important one...

Edit: Recommitting after untracking the file with Git LFS fixed it, had to edit .gitattributes, my jeetcode can show up now
 
Last edited:
I think SQL should be pronounced "skull", and GUI should be pronounced "gwee", while GIF should be spelled out as "jee eye eff".

Also, character should be pronounced with a "tsh" sound at the start but only when used in a programming context.
I have a pathological need to mispronounce GIF as 'ghife' as in 'strife'.
SQL is 'sequel.'
GUI is 'gooey'.
i dint know so many people didnt refer to gui by its individual letters... moreover i think if gui was to be pronounced as a word it should be treated as a homophone to guy. since i and y make the same sound with these letters
 
Decided to start reading SICP as a consequence of the discussion ITT. I've made it almost through Ch. 1, and I find the meticulous approach the author takes really engaging. I oddly find Scheme not super alienating, having been doing a lot of Elisp lately, it's actually kind of a breath of fresh air, because things are lexically scoped without prodding. Gonna take my time with this, I'm enjoying the process of reading the book, and I think doing it in bits and pieces will help with retention and not burning out.
 
I oddly find Scheme not super alienating, having been doing a lot of Elisp lately, it's actually kind of a breath of fresh air, because things are lexically scoped without prodding.
also try syntax-rules if you get a chance
it's like defmacro but it can't pollute the scope without using another kind of syntax transformer
 
do you guys recommend the javascript version of sicp (i fw procedural languages more than functional) or should i man up and read the original?
I've worked professionally in Javascript. My academic language of choice has always been Prolog, but SICP grows my respect for and appreciation of Scheme. You're not going to get anywhere near as much out of it by using Javascript. They really lean on Scheme's capacity to mimic the actual mathematics underlying the programming. Javascript is in no way comparable.
 
What resources would you guys recommend for learning Prolog? This thread seems to host a rare concentration of Prolog appreciators.

do you guys recommend the javascript version of sicp (i fw procedural languages more than functional) or should i man up and read the original?
I'd recommend the original. A lot of the "big ideas" of the book are much clearer/cleaner when working with a LISP than they would be in JS. I didn't know Scheme before reading, but I didn't find it too difficult to learn.
 
Just do it with Scheme. I'm confident you'll learn a lot more going outside your comfort zone by using it.
I've worked professionally in Javascript. My academic language of choice has always been Prolog, but SICP grows my respect for and appreciation of Scheme. You're not going to get anywhere near as much out of it by using Javascript. They really lean on Scheme's capacity to mimic the actual mathematics underlying the programming. Javascript is in no way comparable.
I'd recommend the original. A lot of the "big ideas" of the book are much clearer/cleaner when working with a LISP than they would be in JS. I didn't know Scheme before reading, but I didn't find it too difficult to learn.
alright, thank you guys :)
maybe kiwifarms isnt an evil tranny murder website after all.......
 
What resources would you guys recommend for learning Prolog?
A psychiatric evaluation. If Prolog is a good fit for you, the SWI Prolog documentation should be adequate. Learning materials for it are sparse, and you're going to be learning from incredibly technical angles anyhow, because I don't know any language as full of creative ways to shoot yourself in the foot. Prolog, as a language, was roughly incepted as such: "Huh. This metaprogramming capacity in Lisp is pretty neat, but if we shackle it to Horn clauses and variable unification, we can retain Lisp's metaprogramming facilities (albeit with substantially more complexity) while providing an interface that helps code look vaguely imperative so new users aren't as mindraped by the complexities of metaprogramming, and they get a basic proof engine as an added bonus."

Learn Prolog Now isn't bad. https://lpn.swi-prolog.org

There's surely nothing as glorious as SICP in this field anyhow.

Edit:Best upper-level resource is "The Craft of Prolog" by O'Keefe. It is dated, but so is Prolog.
 
Last edited:
Back