The posts are text only so the memory usage doesn't grow very fast. You can post images using Markdown but the images themselves have to be hosted elsewhere. I've created a few million posts on a development laptop and the memory usage was not bad (can't remember the exact number).
Right now there is no memory limit or handling for when memory reaches a certain point. Pruning based on FIFO or fewest replies could work, or OS level techniques to handle memory limitations like swap.
I will add some screenshots to the repo. Thanks for the suggestion.
You can post images using Markdown but the images themselves have to be hosted elsewhere.
Ah I see. That's easy enough, though I have found people nowadays find that to be too much friction. Old timers are good with it as that is all they had on IRC assuming DCC was disabled as it should be. The current generation expects files to be hosted by the same platform.
In terms of memory the one thing I would want to avoid is swap. Slowness aside it is on disk and data can be recovered from it and automating mounting encrypted swap adds a weakness as well. ZRAM can add some compression to memory. [1] I think your idea of pruning replies matches the current pattern used by sites with space restrictions. Great work, I hope more people follow in your footsteps and also contribute to your code.
The bigger problem is that the amount of information you can consume using RSS feeds is declining. Most sites don't publish RSS feeds of their content any more.
Sadly RSS is left over from a time when things were more open. Now everything is an app and everyone wants you to stay in their walled garden.
There seem to be many services for addressing this. I wonder if anyone has recommendations about which one to use? Searching for "auto generate rss" returns at least a screenful of these.
Having a baby caused me to transition to this style for personal projects. I spend a lot less time in front of the computer now and when I do it's for shorter times.
I've found this approach does give a better result and eliminates false starts. When I'm at the computer now I have already thought through what I'm going to do completely and writing the code is just a minor detail.
Open source router firmwares like DD-WRT or Android handsets would be good platforms for some kind of mesh network.
Having a wireless AP with a webserver and forum software would be a simple option for communicating with your immediate neighbors (who could communicate with theirs).
I'm one of those haters who thinks Java IS kind of corporate and boring. On the other hand, it's just a programming language, and it's what you do with it that counts. You could write enterprise CRUD apps in Lisp if you wanted to.
I think it's more interesting that Minecraft is a Java APPLET. (at least the free version I played was)
Once you click that "allow permissions" button, an applet is pretty much exactly like any other Java application. It has all the permissions it wants, up to and including running native code.
The paid version gives you the option to run it either as an applet or a downloadable auto-updating jar.
CPAN is large and comprehensive but every time I've had to use it I've had to watch a minimum of 20 minutes of scrolling compilation, installing dependencies and running tests. Ruby and python install what I need in a few seconds so I can get back to work.
Maybe it's a question of perl putting a lot of things in CPAN versus other languages putting more in the standard library?
Maybe it's a question of perl putting a lot of things in CPAN versus other languages putting more in the standard library?
Swings and roundabouts really because there is no definitive advantage in either approach.
Advantage in CPAN approach: Its more darwinian. Your libraries are more up-to-date (stdlibs often get stale)
Advantage in stdlib approach: Less dependencies. Batteries included out of the box.
After installing Perl first thing I do is load a few important CPAN modules (like Moose, AnyEvent, Coro, Devel::Repl, DBIx::Class) and then all your big loads are pretty much done.
Right now there is no memory limit or handling for when memory reaches a certain point. Pruning based on FIFO or fewest replies could work, or OS level techniques to handle memory limitations like swap.
I will add some screenshots to the repo. Thanks for the suggestion.