Desktop OSes just assume the vertical subtiles (at best with an option between RGB and BGR). TVs and mobile devices don't generally support subpixel rendering at all.
Actually the title is what doesn't change, not the page number. I.e. the object manager has a mapping where a given object (article) is in memory (on what page, pun intended). So you have to go through the object manager to resolve the mapping each time you want to interact with the object... or at least that's how we have it implemented in the web viewer ;)
I've never seen this before, it's like a modern 2600 - deeply technical, scattered topics and depth, all very hacker-curious - and beautifully designed to boot.
Wait, you're getting blocked trying to download Paged Out!? This most likely is a problem with your ISP, not with the zine's server. Check with them first.
Fun fact - the computiles piece is an uncredited rediscovery of Wang's work from the 1960's on computable tilings. Specifically, he went as far to show that the halting problem is equivalent to the 'domino problem' - can we tile the plane using a given finite set of dominoes (aka tiles) where we have infinitely many copies of each and the tiling must preserve edge-meet criteria. Every tiling is a computer program, every computer program is a tiling.
What do you mean? It's just simple beginner's examples in C. Should be easy enough to understand, C is famously very simple ('portable assembler' as they say!).
> In our experience, C has proven to be a pleasant, expressive and versatile language for a wide variety of programs. It is easy to learn, and it wears well as one's experience with it grows.
(1) is equivalent to "typedef long* $(void*, ...)". '$' is the name of the defined function type.
it's obfuscated as follows:
- typedef is a specifier and can go on either side of the type, same as int const/const int
- [[ ]] is an empty list of attributes
- "void*($)" is an argument named '$' of type void*, but parameter names are ignored in declarations.
- you can put parens in declarations since sometimes you need to group prefixes and postfixes in a different order
- dollar signs in names are allowed in many c compilers (and some other c-like languages)
- "..." are variadic arguments. puts doesn't have those, but the first argument uses the same register either way so it happens to work out in this case
(4) declares a function named '$' of type '$', shadowing the type, and links it to the assembly label "puts". calling $ calls puts.
normally it looks like `int call_foo(void) asm("foo");`
(5) is parsed as: "label $: address-of-label $ and function $ called on str. the address of a label is truthy, so the function also gets called.
unary && looks for the argument in the label namespace, but other operators don't, so the two dollars refer to different things.
that's about it. if you're familiar with the c standard and some common gnu extentions, you can deconstruct the examples into their basic elements easily enough
I like page 30: The Subpixel Zoo. It must be hell for text rendering:
https://en.wikipedia.org/wiki/Subpixel_rendering
Desktop OSes just assume the vertical subtiles (at best with an option between RGB and BGR). TVs and mobile devices don't generally support subpixel rendering at all.
Sorry, we moved this. It's on page 37 now - "Hardware" section works better for this one than "Food for thought".
https://pagedout.institute/webview.php?issue=9&page=37&artic...
> Sorry, we moved this.
Isn't the borrow checker supposed to prevent these things? I was still holding an immutable reference.
Actually the title is what doesn't change, not the page number. I.e. the object manager has a mapping where a given object (article) is in memory (on what page, pun intended). So you have to go through the object manager to resolve the mapping each time you want to interact with the object... or at least that's how we have it implemented in the web viewer ;)
I've never seen this before, it's like a modern 2600 - deeply technical, scattered topics and depth, all very hacker-curious - and beautifully designed to boot.
For those interested, anyone can write a (one-page) article:
https://pagedout.institute/?page=cfp.php
And it blocks IP ranges it doesn't like, so who knows what's in it?
Wait, you're getting blocked trying to download Paged Out!? This most likely is a problem with your ISP, not with the zine's server. Check with them first.
Yep they seem to be hard-blocking Tor users.
That might be something at Google Cloud ingress then. We're not blocking on IP level (we have some other stuff, but it shouldn't interfere with Tor).
> Google Cloud
Ew. Do you need hosting donations?
Hahaha thank you, if needed we have a few more options. For now I'm sticking to it since it's familiar territory for me.
`Baby Steps in C` is hilarious lol. I'll be buying the print editions going forward. They hooked me right in with that.
That article triggered me to send it to my friends. C be crazy.
It's not standard conforming C. asm() is an extension.
Simultaneously triggered my PTSD and made me laugh
It reminds me a little bit of a Phrack textfile, but if Phrack had raster image art advertising in it.
What you've described is the printed version of Phrack!
Fun fact - the computiles piece is an uncredited rediscovery of Wang's work from the 1960's on computable tilings. Specifically, he went as far to show that the halting problem is equivalent to the 'domino problem' - can we tile the plane using a given finite set of dominoes (aka tiles) where we have infinitely many copies of each and the tiling must preserve edge-meet criteria. Every tiling is a computer program, every computer program is a tiling.
It’s credited in section 3
Michał Zalewski's article on page 42 is very funny.
Would someone be interested in explaining what in the world is going on in that article?
What do you mean? It's just simple beginner's examples in C. Should be easy enough to understand, C is famously very simple ('portable assembler' as they say!).
> In our experience, C has proven to be a pleasant, expressive and versatile language for a wide variety of programs. It is easy to learn, and it wears well as one's experience with it grows.
The C Programming Language K&R
I'll try to do the first one since I think it's the most illustrative:
(1) is equivalent to "typedef long* $(void*, ...)". '$' is the name of the defined function type.
it's obfuscated as follows:
- typedef is a specifier and can go on either side of the type, same as int const/const int
- [[ ]] is an empty list of attributes
- "void*($)" is an argument named '$' of type void*, but parameter names are ignored in declarations.
- you can put parens in declarations since sometimes you need to group prefixes and postfixes in a different order
- dollar signs in names are allowed in many c compilers (and some other c-like languages)
- "..." are variadic arguments. puts doesn't have those, but the first argument uses the same register either way so it happens to work out in this case
(4) declares a function named '$' of type '$', shadowing the type, and links it to the assembly label "puts". calling $ calls puts.
normally it looks like `int call_foo(void) asm("foo");`
(5) is parsed as: "label $: address-of-label $ and function $ called on str. the address of a label is truthy, so the function also gets called.
unary && looks for the argument in the label namespace, but other operators don't, so the two dollars refer to different things.
that's about it. if you're familiar with the c standard and some common gnu extentions, you can deconstruct the examples into their basic elements easily enough
When does the Printed edition go on sale? Lulu doesn't have the 9th edition listed yet.
It should be available on lulu until the end of the week. We're running QA on it still.
The anime avatar twitter people have finally created something beautiful.
Ahaha thank you for this comment, it's peak internet meme culture. Made my day :D
My fav zine