Don't know anything about misunderstandings, but the symbol in question is https://en.m.wikipedia.org/wiki/Looped_square

Native 1440p, never used retina nor 4k.

(not parent commenter, but hold same opinion)

Same here... 1440p 32" is optimal for me, the only improvement I'd consider right now is 1600p equivalent.

Biggest draw for me with 1440p 32" is being the same DPI as a 1080p 24". I like to have one big monitor and then 2 small flank vertical monitors and having them all be the same DPI just makes headaches go away on every operating system I use them with.

Damn. I am so happy with my old 17" monitor and 1280x1024 resolution here. :D

I would go for "writing style" or "behavior", but would almost be okay with "personality"

Inanimate objects are said to have personality, too. This is certainly true for clothing and decor.

Rust has error handling personality.

Oh no it's the bouncy ball chart.

Please, if you have enough time, watch this https://youtu.be/EH12jHkQFQk

and avoid making any decisions using this chart.

> and avoid making any decisions using this chart.

I did not mention that chart at all in the blog post. I just used this as a nice illustration.

Honestly yeah

It's an artificial benchmark that means nothing in production

Also the article does not bring much to the table except of python whining

"Oh the Go dockerfile is smaller" Yes you compiled it and is running a binary. Big woop. Funny how the author not doing the same comparison with node

> "Oh the Go dockerfile is smaller" Yes you compiled it and is running a binary. Big woop. Funny how the author not doing the same comparison with node

If I did that with Node, you would say what about Ruby. If I did that with Ruby, you would say what about Zig. There is no end to the list of languages.

> It's an artificial benchmark that means nothing in production

It was a cover illustration, I did not mention that at all. In fact, I demonstrated the resource consumption of Python's docker image. If you have suggestions to make the Python one, I am all ears.

> If I did that with Node, you would say what about Ruby.

No, because the comparison here is runtimes of interpreted languages

Comparing a compiled binary to the python/node/ruby runtime is comparing Apples to Oranges

Why do I have to restrict myself to interpreted languages only?

Can you share what was the problem, just in case we have it too?

We had little strings that encoded call signatures, like "iiff" for int int float float. Someone cooked up a way to have typescript validate the strings at build time, but the way it does typechecks against string literals like that seems to cause every string literal in your entire compilation to get validated in advance to figure out whether it could possibly be that specific type. Each possible value - let's say we had 'f', 'i', and 'l' originally and then we added a fourth option for 'd' - caused the typecheck time to magnify by increasing the possible options. IIRC.

I'd bet it had to do with complex templates.

I've had typescript break on me when using libraries like elysia that go full send on their templates.