The reporting of a message's timestamp really depends on the system you are working on. And the key aspect is to genuinely think how the users think about that timestamp.
I recently implemented it in a real time system where I write things like
"just now" (within the last 10 seconds)
"more than 10 seconds ago" (between 10 seconds and less than a minute)
"more than a minute ago" (between 1 one minute and less than 10 minutes)
"more than 10 minutes ago" (between 10 minutes and less than 1 hour)
... (I think you get the gist)
After it say more than a day... then that's it the message is considered very old
Like many, I have stumbled on tons of articles on the blockchain. Some very good, some not so good.
But I never stumbled on some easy blockchain simulator where I could try things out.
So if you are like me, and you don't like being told things as much as you like coming to the conclusion yourself then you really need to give blockchaincalm a chance.
So Javelin is written in Java, not in Kotlin.
I don't mean to sound unfair
but isn't it that saying "a Java/Kotlin blah blah" just a kind of marketing trick ?
If I get Kotlin right every Java solution is also Kotlin compatible.
We built an inmemory map and we were using String.intern
for both keys and values. We could see that we were saving lots of memory but we had the problems described in the article.
We then built our own 'String.intern' by using yet another static HashMap. It worked.
It was the simplest alternative and it just did the job.
Thanks alekskey for the nice article.
Good article.
I am unsure about point 7 "Consider changing where you live"
I accept that for some careers this might be inevitable but in a truly connected world it's also nice to follow the opposite advise and spot opportunities where you are