hackernews VS endbasic

this might help a little: https://github.com/wting/hackernews

I think it's a ratio of votes to time. I think as little as 4 votes can get something on the homepage if they come in fairly quickly.

The source code for hn is available if you want to go and look up the specifics. I'm not sure if this is the most up-to-date mirror, but the site doesn't change that often: https://github.com/wting/hackernews

Might not count as modern, but the original Reddit and HackerNews codebases:

- https://github.com/reddit-archive/reddit1.0

- https://github.com/wting/hackernews (actually news.arc, based on old hn)

There's also this https://github.com/wting/hackernews -- which is a version of the source code to the site from sometime in the past.

"Otherwise" was the operative word in my (slightly sarcastic) example. :)

Avoiding all caps words means you sometimes have to go back and change "FAA" back from "Faa".

HN's software is no longer open source, but at one time, this is how it processed titles on initial submission: https://github.com/wting/hackernews/blob/master/news.arc#L15...

And at any rate, #1 on HN is not the product of any simple rule like "most upvotes per unit time with some decay function applied." There is significant judgment in expressed in the way that stories are ranked. The sourcecode as of 2012 was enough to demonstrate this, but in my understanding yet more judgment has been applied since then.

https://github.com/wting/hackernews/blob/master/news.arc

"ad-hoc filesystem based solution" is the closest of your definitions, I think. Last time I saw/heard, HN was built in Arc, a Lisp dialect, and use(s/d) a variant of this (mirrored) code: https://github.com/wting/hackernews

Check out around this area of the code to see how simple it is. All just plain files. A database, of sorts, but not in the way you might be expecting: https://github.com/wting/hackernews/blob/master/news.arc#L16...

There is a modern maintained variant at https://github.com/arclanguage/anarki/tree/master/apps/news as well.

File syncing between machines is pretty much an easily solved problem. I don't know how they do it, but it could be something like https://syncthing.net/ or even some scripting with `rsync`. Heck, a cronned `tar | gzip | scp` might even be enough for an app whose data isn't exactly mission critical.

The old version in arc, mirrored at https://github.com/wting/hackernews/blob/5a3296417d23d1ecc90..., uses the file system as a database.

https://github.com/wting/hackernews/blob/5a3296417d23d1ecc90... shows the monotonically increasing number:

  (def new-item-id ()

I can confirm that writing a terminal is fun, for the reasons mentioned in the article: it’s easy to get “self-hosting”, but then the possibilities are endless :)

In my case, this was about creating the terminal for EndBASIC (https://www.endbasic.dev/). I wanted to mix text and graphics in the same console, so I had to ditch Xterm.js and create my own thing. It was really exciting to see graphics rendering mix with text “just fine” when I was able to render the first line.

I tried to set up a Raspberry Pi and configured it to boot into a simple window manager with DosBox full screen by default. I taught my kids to launch games within that and they learned the very basics… but it didn’t stick: they haven’t really gained any interest in how to do other stuff in the shell.

Anyway: check (my own) https://www.endbasic.dev/ which I’ve written precisely for the situation you describe :) You would actually have to /write/ the games first though!

Slightly buried: Apache 2.0, written in Rust, https://github.com/endbasic/endbasic/

Definitely an interesting attempt to cut through layers of abstraction and make something that lets people make the computer do useful/interesting things. No idea how well they realize that vision, of course, but good idea.

Or you could use https://www.endbasic.dev/

Somebody else brought it up in a separate comment, but because you specifically ask about the Raspberry, I'll mention EndBASIC (https://www.endbasic.dev/) here again :)

Supporting this platform has been a primary goal of mine, and in fact, one of the features (GPIO) only works on the Raspberry Pi today :) But there is a long road ahead. My vision is to create a minimal Linux image that boots straight into EndBASIC, and extend EndBASIC to give you more control of the Pi's hardware. The idea is to truly mimic the old C64 experience, but leveraging the power of modern hardware / infrastructure.

Agree with the author’s thesis of how the folks that “grew with computers” have an advantage over those approaching them now, in terms of understanding the inner workings. I’m not sure that this matters much in terms of solving actual problems though, which is probably a good thing.

But I somehow find it a little bit sad that this is the case, so I’ll plug my own https://www.endbasic.dev/ because it’s very fitting in this context :) I’ve been building it precisely as a way to understand everything that’s going on (although it’s still far from fulfilling that promise).

Also, buried in the article is a reference to the https://10print.org/ book. I recently came across it at HPB and it has been a pretty entertaining read. Couldn’t believe there was so much to write about such a simple little program!