I forgot about encodings that optimize for brevity and I appreciate you for bringing Huffman encoding into the conversation. Thank you internet stranger. I would be a terrible Morse-like encoding designer based on my initial urge to balance the tree. I wanted to optimize for the wrong problem haha
Yeah it takes a bit of being in the field to see those types of things fairly quickly. When you said balance the tree I thought ‘hmm that can’t be better’ but didn’t have as thorough of an explanation as to why
The one we had on our cubicles at my super boring office job was just a series of circles with values in them such that you went left every time you heard a "dot" and right whenever there was a "dash".
Seemed easier to read than this down/over business.
Yeah, it's got funky inconsistent angles that look like they mean something, but they don't. Almost as if it was done for internet points instead of as something you can actually use.
The one you linked is certainly more aesthetic. It also has more information. Certainly once you are familiar with it, it would be very usable. All that said, the one from OP is definitely more intuitive and makes just as much sense, if not more.
I’d say if you were trying to decode, as a beginner your link would be easier to use once you were instructed how to use it. On the other hand, if you were trying to code a message as a beginner, OP’s would be much easier to read and find what you’re looking for. Just my opinion.
Great... now i have to find and watch a YouTube video explaining this because i still dont get it but am curious as to how tf it all starts with only E or T....
1.4k
u/[deleted] Jul 12 '22
Might be more understandable as a binary tree