- Joined
- Oct 19, 2023
on that note, the little schemer is also basedvery small subset of the language because it treats fundamental concepts
This space reserved for JELLY STAINS! |
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
on that note, the little schemer is also basedvery small subset of the language because it treats fundamental concepts
This space reserved for JELLY STAINS! |
There are several others based on programmed learning like The Seasoned Schemeron that note, the little schemer is also based
This space reserved for
JELLY STAINS!
I think SQL should be pronounced "skull", and GUI should be pronounced "gwee", while GIF should be spelled out as "jee eye eff".i got to thinking and i think josh probably pronounces sql as "squill"
you absolute degenerate that's fucking disgusting. it's how they say it in england!GIF should be spelled out as "jee eye eff".
I have a pathological need to mispronounce GIF as 'ghife' as in 'strife'.you absolute degenerate that's fucking disgusting. it's how they say it in england!
I started calling gifs "yif"s. It pisses off everyone.I have a pathological need to mispronounce GIF as 'ghife' as in 'strife'.
SQL is 'sequel.'
GUI is 'gooey'.
As in the "char" data type? That's how it's pronounced already.Also, character should be pronounced with a "tsh" sound at the start but only when used in a programming context.
bad idea because a lot of furries probably think it's hilariousI started calling gifs "yif"s. It pisses off everyone.
That's why I use a long i instead of a short one.bad idea because a lot of furries probably think it's hilarious
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 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 lettersI have a pathological need to mispronounce GIF as 'ghife' as in 'strife'.
SQL is 'sequel.'
GUI is 'gooey'.
also tryI 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.
syntax-rules
if you get a chancedefmacro
but it can't pollute the scope without using another kind of syntax transformerJust do it with Scheme. I'm confident you'll learn a lot more going outside your comfort zone by using it.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.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.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?
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.
alright, thank you guysI'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.
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."What resources would you guys recommend for learning Prolog?