chadsix

Hi HN,

This is more or less a fun experiment that I thought was worth sharing.

Using Daniel J. Bernstein's [1] djb2 hash that he made when he was only 20 years old in 1991, we map names to hashes and provide reverse mappings using an english word list from dwyl [2].

You can see it here: https://github.com/ipv6rslimited/hamon

Hamon (ハモン not 刃文) is derived from HAsh MOdulo Name.

I hope you like it [3]!

[1] The Cypherpunk Super Hero, https://cr.yp.to/

[2] https://github.com/dwyl

[3] Probably minimal real life use cases. ¯\_(ツ)_/¯

I think it's time we have a discussion about the "best" languages.

Any seasoned/senior developer knows that there are real differences between languages, and that a measured approach to choice of language to develop and deploy a specific application is the best approach.

However, lately I have seen suggestions that any language is the "best" language so long as you love that language. This is false and will lead many junior developers to unnecessary headache and technical debt in the future.

Let's take, for example, speed. If speed is a factor, the lower level the language, the more optimized the application can become. If you need concurrency at a higher level, Go or Erlang would be the answer. Fast prototyping, node or ruby.

There are in fact differences in the application and efficiency of languages, and its best we don't ignore this.

There is no best language, only a best language at _________.

What are HN's thoughts on this? What languages are the best for what purposes? Would love to hear about some of the mistakes and improvements learned through experience that I know many on HN have to share, and I think openly sharing these experiences will really help strengthen the developers of tomorrow!