Liked: An Overview of Datalog
How I interact with Micro.blog
As a user of Micro.blog you have a few options to how you read your timeline and post content or replies.
I’m not that worlds best at using so called social apps. The fact is that I forget about them when I have more interesting stuff to do. And the next thing I know is that there have gone hours or even days between looking at them. This is why I almost never read anything in the Micro.blog apps.
What I do is that I read my timeline as a RSS feed, and I re-locate the post in the Micro.blog app if I would like to reply to it.
This works much better for me, because then I can read all the times at a speed that works for me. I started doing this back before the Micro.blog apps supported to go far back in time, and most of the M.B action happened while I was asleep.
Using RSS for this is probably not something most people would want to do. But I love it.
One terms you will hear over and over and over when you start getting into functional programming is the term pure functions.
But they can be a little bit difficult to understand, or difficult to find a clear description.
A pure function is a function that returns a result based on it’s inputs and the inputs alone. The result should be deterministic. This have some consequences for how most programmers write their code. Because a pure function never change anything outside itself.
This mean that it does not use variables that are not defined inside it or are parameters, and it does not change anything outside itself.
If it prints: not pure. If it writes to a file: not pure. If it alters global state: not pure.
I think that using pure functions as much as possible is a good idea, because pure functions are often less buggy and easier to maintain. And it forces you to limit unpure functions to a minimum and really thinking before you deal with unpurity.
Personally I prefer languages like Clojure that are built with this in mind.