Yes! Just started reading the table of contents, and already I'm feeling that joy of old-school creative computing. Revival of the culture of personal computers and programming as a technology of liberation. A better future is possible and the power is in our hands.
I like this magazine vibe, it reminds me of the good ol' l33t zines from the late '80s and '90s. However, if I can offer a suggestion, I'd also pair the technical articles with a little more punky, down-to-earth stuff. They were cheerful, informal, and full of that cheeky, irreverent, cocky smart-ass humor, plus this mysterious edge that made them absolutely magnetic to me. Life just wasn’t so heavy back then.
Thanks for the suggestion! I wouldn't mind having such articles in PO! tbh - let me think what can we do about it (or rather: let me pass this to the rest of the team so they think about it too).
like Mondo 2000 :)
I still have my Mondo 2000 zine. It was literally a futurist guidebook for cyberpunk of today.
Better living through chemistry, memes, cybernetics were all predicted by Mondo.
Wow cool. I have not heard of Mondo 2000 reading hn for almost 20 years. And did not realize Boing Boing was so old. Makes me wonder what else existed.<p>My family had a bunch of "Dr. Dobb’s Journal of Computer Calisthenics & Orthodontia"[0] and similar things (BYTE, COMPUTE!). (Which seem slightly dryer, but maybe more like Paged Out.)<p>[0]:<a href="https://archive.org/details/dr_dobbs_journal_vol_01/mode/2up" rel="nofollow">https://archive.org/details/dr_dobbs_journal_vol_01/mode/2up</a>
TIL :D
Sadly I don't know if that kind of 80s/90s irreverence would go well with today's sensitivities.
> Query based compilers are all the rage: Rust, Swift, Kotlin, Haskell, and Clang all structure their compilers as queries.<p>I've never heard of this. It's a pity the article doesn't go into details.
It is a double edged sword of the single page layout that you really have to make one point briefly and get out of there. I had to pare down many details to fit the layout.<p>If you want to learn more about query based compilers as a concept, I highly recommend ollef's aritcle: <a href="https://ollef.github.io/blog/posts/query-based-compilers.html" rel="nofollow">https://ollef.github.io/blog/posts/query-based-compilers.htm...</a><p>If you want to learn how to implement a query based compiler, I have a tutorial on that here: <a href="https://thunderseethe.dev/posts/lsp-base/" rel="nofollow">https://thunderseethe.dev/posts/lsp-base/</a> (which I also highly recommend but that might be more obvious since I wrote it)
Old discussion: <a href="https://news.ycombinator.com/item?id=23644391">https://news.ycombinator.com/item?id=23644391</a>
Finding this one-page was great! It gave me a new term I didn't have before that leads to all sorts of new materials to go rifling through.
From PO's submission FAQs and policies:<p>> Obviously the used fonts should be readable (and ideally their name shouldn't start with "Comic" and end with "Sans", though there might be some article topics that justify even that!), and while almost any font meets this requirement, please be careful when selecting a non-standard font.<p>I kinda want to see such an article, but taken seriously discussing the history of the font, its design and purpose, evolution, and purpose-related/derivative font families.
I have the printed versions of issue #6 and #7, I highly recommend them!<p><a href="https://www.lulu.com/spotlight/pagedout" rel="nofollow">https://www.lulu.com/spotlight/pagedout</a>
They've got a new web viewer in this issue that can be used to link to individual articles and might be nicer than reading a PDF on some screens: <a href="https://pagedout.institute/webview.php?issue=8&page=1" rel="nofollow">https://pagedout.institute/webview.php?issue=8&page=1</a>
The article I submitted has an HTML tag in the title, and seems to have broken the web viewer :(<p>Note that you can link to pages in a PDF with a hash like #page=64 (for example) in the URL.<p><a href="https://pagedout.institute/download/PagedOut_008.pdf#page=64" rel="nofollow">https://pagedout.institute/download/PagedOut_008.pdf#page=64</a>
Still would like a straight html version for reading on a phone. One with resizable text and proper reflow.
Awesome! Was looking forward to the next issue. <i>Paged Out</i> reminds me a lot of the old-school 2600 Hacker Quarterly periodical back in the 80s.<p><a href="https://en.wikipedia.org/wiki/2600:_The_Hacker_Quarterly" rel="nofollow">https://en.wikipedia.org/wiki/2600:_The_Hacker_Quarterly</a>
I love Paged Out -- it's basically the only modern equivalent to 1980s <i>BYTE</i> or <i>Dr. Dobbs Journal</i> today.
I enjoyed writing an article for this issue.<p>I highly recommend it if you enjoy writing. It was painless and fun.<p>A nice break from writing blogs.
[re: page 40 NTP-over-HTTP] ooh i've heard of this! it's being used in real life by Whonix (sdwdate) and Tails (tails-htp/htpdate)<p><a href="https://www.kicksecure.com/wiki/Sdwdate" rel="nofollow">https://www.kicksecure.com/wiki/Sdwdate</a>
<a href="https://tails.net/contribute/design/Time_syncing/" rel="nofollow">https://tails.net/contribute/design/Time_syncing/</a>
Creative Computing
BYTE
MICRO
Nibble
Dr. Dobb’s Journal
Compute!
InfoWorld<p>So great to find that spirit again!
Thank you. I love the wallpapers of Paged Out and always set it as my default wallpaper on MacOS.
I feel like this tweet suggests that the PDF is a polyglot or an embedded second PDF.<p><a href="https://x.com/gynvael/status/2024180784064598134" rel="nofollow">https://x.com/gynvael/status/2024180784064598134</a>
Initial impressions says no about being that file a polyglot.<p>If you like polyglot files, see <a href="https://www.alchemistowl.org/pocorgtfo/" rel="nofollow">https://www.alchemistowl.org/pocorgtfo/</a>
Ah, no, sorry, no polyglots there yet. We'll get there one day, but so far our tooling doesn't allow for it yt.
Some nice art in there too.
It has a little bit of a "2600 vibe" but with a more modern look and feel. This is the first issue I've read, and I like it.
this is absolutely magnificent, and exactly the kind of thing i wish there were more of in the world.
It's a great day every time one of these hits the RSS reader. Great work as always Paged Out team!
Just learned about the project, looks really interesting.
A couple of the stories where I feel I have expertise I found to be a bit objectionable. The title/headline was some clever or unexpected thing, but upon reading it turns out there is nothing supporting the headline.<p>E.g. "Integer Comparison is not Deterministic", in the C standard you can't do math on pointers from different allocations. The result in the article is obvious if you know that.<p>Also, in the Logistic Map in 8-Bit. There is a statement<p>> While implementing Algorithm 1 in modern systems is trivial, doing so in earlier computers and languages was not so straightforward.<p>Microsoft BASIC did floating point. Every 8-bit of the era was able to do this calculation easily. I did it on my Franklin ACE 1000 in 1988 in basic while reading the book Chaos.<p>I suppose what I'm saying is the premise of the articles seem to be click-baity and I find that off putting.
You're right.<p>In general when selecting articles we assume that the reader is an expert in some field(s), but not necessarily in the field covered by this article. As such, things which are simple for an expert in the specific domain, can still be surprisingly to learn for folks who aren't experts in that domain.<p>What I'm saying is, that we don't try to be a cutting edge scientific journal — rather than that, we publish even the smallest trick that we decide someone may not know about and find it fun/interesting to learn.<p>The consequence of that is that, yeah, some article have a bit clickbaity titles for some of the readers.<p>On the flip side, as we know from meme-t-shirts, there are only 2 things hard in computer science, and naming is first on the list ;)<p>P.S. Sounds like you should write some cool article btw :)
For what it's worth, I am only a mid-tier nerd and after reading this issue, I feel like I am your target audience. Nothing deep or overly-detailed, just lots of jumping-off points for me to learn more. Thanks!
I noticed that as well. Also misleading titles like “Eliminating Serialization Cost using B-trees” where the cost savings are actually for <i>de</i>serialization (from a custom format), and neither the self-balancing nature of B-trees isn’t actually relevant, as no insertion/deletion of nodes occurs in the (de)serialization scenario, so a single tree level is sufficient. It’s a stretch to refer to it as a B-tree.
I took a peak at "Compiler Education Deserves a Revolution" and thought, wtf is this talking about?<p>It claims clang is NOT "a pipeline that runs each pass of the compiler over your entire code before shuffling its output along to the next pass."<p>What I think the author is talking about is primarily AST parsing and clangd, where as "any compiler tome" is still highly relevant to the actual work of building a compiler.
<a href="https://learn.microsoft.com/en-us/shows/seth-juarez/anders-hejlsberg-on-modern-compiler-construction" rel="nofollow">https://learn.microsoft.com/en-us/shows/seth-juarez/anders-h...</a><p><a href="https://news.ycombinator.com/item?id=11685317">https://news.ycombinator.com/item?id=11685317</a><p><a href="https://lobste.rs/s/dwf2yn/sixten_s_query_based_compiler" rel="nofollow">https://lobste.rs/s/dwf2yn/sixten_s_query_based_compiler</a><p><a href="https://ericlippert.com/2012/06/08/red-green-trees/" rel="nofollow">https://ericlippert.com/2012/06/08/red-green-trees/</a><p>Rust's salsa, etc.<p>Related search terms are incremental compilation and red-green trees. It's primarily an ide driven workflow (well, the original use case was driven by ides), but the principles behind it are very interesting.<p>You can grok the difference by thinking through, for example, the difference between invoking `g++` on the command line - include all headers, then compile object files via includes, re-do all template deduction, etc. and one where editing a single line in a single file doesn't change the entire data structure much and force entire recompilation (this doesn't need full ownership of editing either by hooking UI events or keylogging: have a directory watcher treat the file diff as a patch, and then send it to the server in patch form; the observation being that compiling an O(n) size file is often way more expensive than a program that goes through the entire file a few times and generates a patch)<p>AST's are similar to these kinds of trees only insofar as the underlying data structure to understand programming languages are syntax trees.<p>I've always wanted to get into this stuff but it's hard!
OK, but that is distinctly NOT what clang does... incremental compilation with clang is handled at the build system level. I can't speak for rustc, but I do know that it typically ends up going through llvm, which, contrary to the author's claims, is exactly a pipeline.
The vibe is flawless.
This is so awesome, do you have a mailing list, RSS, etc?
[dead]