Niki
@znichola.bsky.social
Aspiring functional programmer, Haskell is the drug of choice.
Student for life at ecole42
Student for life at ecole42
( <- parenthesis
[ <- square bracket
{ <- curly bracket
[ <- square bracket
{ <- curly bracket
October 19, 2025 at 11:26 AM
( <- parenthesis
[ <- square bracket
{ <- curly bracket
[ <- square bracket
{ <- curly bracket
🤣 yes the program’s memory, but I like the idea.
I will say it’s deeply satisfying to unpack and understand how this stuff works.
I will say it’s deeply satisfying to unpack and understand how this stuff works.
August 29, 2025 at 5:30 PM
🤣 yes the program’s memory, but I like the idea.
I will say it’s deeply satisfying to unpack and understand how this stuff works.
I will say it’s deeply satisfying to unpack and understand how this stuff works.
It happens all the time when a program runs. Python hides this from a user, in C you need to explicitly manage it. The system will not let a program do anything terrible so it’s safe, but it can be frustrating as you learn how it’s supposed to be done.
August 29, 2025 at 5:25 PM
It happens all the time when a program runs. Python hides this from a user, in C you need to explicitly manage it. The system will not let a program do anything terrible so it’s safe, but it can be frustrating as you learn how it’s supposed to be done.
That depends on what you want to do, a 3D game or a tui adventure game. At least with C you are learning by doing and understand the why, not like python where you’ll just be told to memorise the way of things, imagine trying to understand pointers in python when the syntax obfuscates it on purpose
August 29, 2025 at 3:15 PM
That depends on what you want to do, a 3D game or a tui adventure game. At least with C you are learning by doing and understand the why, not like python where you’ll just be told to memorise the way of things, imagine trying to understand pointers in python when the syntax obfuscates it on purpose
C if you want to learn "programming"
Python if you want to do stuff that requires programming
I want to make a game -> Python
I want to learn how programming works -> C
Python if you want to do stuff that requires programming
I want to make a game -> Python
I want to learn how programming works -> C
August 29, 2025 at 7:26 AM
C if you want to learn "programming"
Python if you want to do stuff that requires programming
I want to make a game -> Python
I want to learn how programming works -> C
Python if you want to do stuff that requires programming
I want to make a game -> Python
I want to learn how programming works -> C
Smells like JAI, man would I love to test this thing
August 25, 2025 at 5:42 PM
Smells like JAI, man would I love to test this thing
Unison lang, it blew my mind to have docs as a type. They are part of a module definition and examples are compiled from code.
share.unison-lang.org/@unison/webs... @unison/website | Unison Share
share.unison-lang.org/@unison/webs... @unison/website | Unison Share
Doc · @unison/website/main | Unison Share
Source code for unison-lang.org
share.unison-lang.org
August 22, 2025 at 9:33 AM
Unison lang, it blew my mind to have docs as a type. They are part of a module definition and examples are compiled from code.
share.unison-lang.org/@unison/webs... @unison/website | Unison Share
share.unison-lang.org/@unison/webs... @unison/website | Unison Share
I see, yeah here it it. It’s a bit long though. youtu.be/sJuKpajV1XI?...
Talking about Stop Killing Games | with @Accursed_Farms
YouTube video by Josh Strife Says
youtu.be
August 10, 2025 at 2:43 PM
I see, yeah here it it. It’s a bit long though. youtu.be/sJuKpajV1XI?...
Let’s say you construct an argument and then say some really logical points showing why it’s bad. Eg retroactively applying. It’s a straw man because nobody on the other side is saying that. So your arguing with an invented opponent (made of straw).
And I saw it in a video.
And I saw it in a video.
August 10, 2025 at 2:29 PM
Let’s say you construct an argument and then say some really logical points showing why it’s bad. Eg retroactively applying. It’s a straw man because nobody on the other side is saying that. So your arguing with an invented opponent (made of straw).
And I saw it in a video.
And I saw it in a video.
It would never be retroactive, never wanted to be and legally cannot be. This point is specifically talked about by Ross, and explain on the initiative website. Complete straw man and bad faith, and I think illustrates why Pirate is so frustrating.
August 10, 2025 at 2:02 PM
It would never be retroactive, never wanted to be and legally cannot be. This point is specifically talked about by Ross, and explain on the initiative website. Complete straw man and bad faith, and I think illustrates why Pirate is so frustrating.
And speaking of the wikipedia page, I've make a mistake.
char s[] is a compile time known value, and so sizeof(s) will return the size of the "string"; string length * char size
char s[] is a compile time known value, and so sizeof(s) will return the size of the "string"; string length * char size
June 8, 2025 at 4:43 PM
And speaking of the wikipedia page, I've make a mistake.
char s[] is a compile time known value, and so sizeof(s) will return the size of the "string"; string length * char size
char s[] is a compile time known value, and so sizeof(s) will return the size of the "string"; string length * char size
`char s[] = "Hello";` s also points to the string "Hello" but this time it's on the stack.
It's copied to the stack from the read-only memory when the function is invoked, the stack is where the other function variables live.
Because it's on the stack you can modify the string.
It's copied to the stack from the read-only memory when the function is invoked, the stack is where the other function variables live.
Because it's on the stack you can modify the string.
June 8, 2025 at 4:34 PM
`char s[] = "Hello";` s also points to the string "Hello" but this time it's on the stack.
It's copied to the stack from the read-only memory when the function is invoked, the stack is where the other function variables live.
Because it's on the stack you can modify the string.
It's copied to the stack from the read-only memory when the function is invoked, the stack is where the other function variables live.
Because it's on the stack you can modify the string.
`char *s = "Hello";` s points to the string "Hello" but where actually is this string?
It's in read-only memory when you program is running, it's in your final binary, along with the machine instructions that are the rest of your compiled program.
It's in read-only memory when you program is running, it's in your final binary, along with the machine instructions that are the rest of your compiled program.
June 8, 2025 at 4:26 PM
`char *s = "Hello";` s points to the string "Hello" but where actually is this string?
It's in read-only memory when you program is running, it's in your final binary, along with the machine instructions that are the rest of your compiled program.
It's in read-only memory when you program is running, it's in your final binary, along with the machine instructions that are the rest of your compiled program.
Both are same size and they are both pointers, they point to things in different places though, the size is the pointer size on your system, probably 4 bytes.
It's like you asked what's the size of a url, but you're actually looking for the length of the document the url **points** to.
It's like you asked what's the size of a url, but you're actually looking for the length of the document the url **points** to.
June 8, 2025 at 4:18 PM
Both are same size and they are both pointers, they point to things in different places though, the size is the pointer size on your system, probably 4 bytes.
It's like you asked what's the size of a url, but you're actually looking for the length of the document the url **points** to.
It's like you asked what's the size of a url, but you're actually looking for the length of the document the url **points** to.
Also, I like the layout and style of your blog. 😄
June 8, 2025 at 5:40 AM
Also, I like the layout and style of your blog. 😄
sizeof is useful if you have a struct and you’d like to know it’s _size_ so you can request the correct number of bytes to store say 10 of them in an array.
June 8, 2025 at 5:39 AM
sizeof is useful if you have a struct and you’d like to know it’s _size_ so you can request the correct number of bytes to store say 10 of them in an array.
sizeof is a compile time helper, not runtime. It could never tell you the length of a string.
Sizeof is used to get the number of bytes the object takes in memory, a string is a pointer, it’s _size_ is will always be the same.
Sizeof is used to get the number of bytes the object takes in memory, a string is a pointer, it’s _size_ is will always be the same.
June 8, 2025 at 5:37 AM
sizeof is a compile time helper, not runtime. It could never tell you the length of a string.
Sizeof is used to get the number of bytes the object takes in memory, a string is a pointer, it’s _size_ is will always be the same.
Sizeof is used to get the number of bytes the object takes in memory, a string is a pointer, it’s _size_ is will always be the same.
Yeah it’s just syntactic sugar, no unique functionality. But it is nice and concise.
April 20, 2025 at 6:50 AM
Yeah it’s just syntactic sugar, no unique functionality. But it is nice and concise.
And Haskell
[i | i <- list]
[i | i <- list]
April 19, 2025 at 9:31 AM
And Haskell
[i | i <- list]
[i | i <- list]
[i for i in range(0,10)]
April 19, 2025 at 9:28 AM
[i for i in range(0,10)]