Moin
I really don’t like comparing languages by Hello World complexity. You could use a lang which needs 3 chars to print it but sucks at everything else but it would still look better at first glance.
As for this specific comparison: let the project grow to only midsize and you will crave for static types and well separated classes.
The application was MPV. At random time it started consuming 100% of one core for a long time. I could track it down to the clipboard thread where a loop polls Wayland to get the latest content of the clipboard (selected text). Seems like a bug in some other application spamms this clipboard buffer from time to time and so caused the MPV loop to run continously.
This way I learned about that Wayland API and as MPV can emit logs whenever the poll loop got new data, I was able to see that it fired whenever I selected text in some application.
Good to know the name of this feature; primary buffer. Now I need to find a way to disable it.
@nephew@lemmy.ca what is your license for this image? I would like to use it in my university.
Counterarguments:
All wellknown programs or services where the name has no relation to the purpose.
Maybe not peak performance but heigh CPU efficency, it’s load ist mostly 0.
fish shell and you can type the first chars of the command and it will show an autocompleate.
A good question, as I like it and don’t like it. It is without a doubt better than dynamic types.
On the pro side it removes redundant writing the type again and again. On the con side it is almost impossible to see what type with what functions the variable in front of you has without an IDE (which you don’t have without cloning the repo) or without an already deep knowledge of the code.
Same with extension functions (free functions which can be added to a type almost anywhere in the codebase). Very useful (Kotlin is a great example for this) but also confusing when you want to hunt down where this piece of code is coming from.