News for hackers. Stuff that matters.
Re:Understanding Glibc Malloc by lionkor on Saturday March 25, 2023 @05:04AM (#35300829)
Not sure if the author is here, but I recommend the author install LangaugeTool in their browser, or whichever editor they use - the amount of mistakes makes it a bit confusing to read.
Re:Understanding Glibc Malloc by benj111 on Saturday March 25, 2023 @05:50AM (#35301086)
>I recommend the author install LangaugeTool in their browser

Touche.

I get the impression that the author isn't a native speaker. And as you yourself demonstrate, these things are hard for the best of us.

Ultimately though they're presumably proficient at the intricacies of malloc rather than writing, and have taken the time to share what they've learnt. Better writing will hopefully come with practice

Re:Understanding Glibc Malloc by KronisLV on Saturday March 25, 2023 @04:51PM (#35307206)
> LangaugeTool

Out of curiosity, I went to the page of the tool and input the comment contents, which correctly caught the mistake, although tools typically miss various compound names in my experience, due to their dictionaries being limited: https://languagetool.org/

For example, I proofread my own blog posts by using the built in LibreOffice spellcheck (offline dictionary) and that has actually been useful in catching a typo or two in most of my writing. Personally, I probably wouldn't use a browser plugin due to concerns over data privacy and not caring much beyond the browser's built in spellcheck, but I personally support the overall spellchecking suggestion, as long as the tone is positive!

For some folks, the style and punctation suggestions in some of the tools out there might also be useful.

Re:Understanding Glibc Malloc by keithalewis on Saturday March 25, 2023 @11:38AM (#35303736)
I had no trouble understanding the author's intent. Guess where I would recommend installing your condescending suggestion of LanguageFool.
Re:Understanding Glibc Malloc by lionkor on Sunday March 26, 2023 @10:09AM (#35314623)
Thats nice, but I did have trouble understanding it, as it distracted me. Im not a native english speaker, so maybe its easier for you, no idea.

You can't invalidate my experience by just saying "works for me", though that would be nice and easy.