News for hackers. Stuff that matters.

A comment on The Windows malloc() implementation from MSVCRT is slow. Parent comment

Re:The Windows malloc() implementation from MSVCRT is slow by mananaysiempre on Saturday July 02, 2022 @08:51PM (#31963997)
So a vscode thingie uploads a newer binary to an older host, tries to run it there, and fails? Because the people who built said binary did not care to make it backwards compatible (or better yet, statically linked)?

... Duh?

(I’m not an expert in VSCode DRM, to put it mildly, so I might be misinterpreting this discussion, but that’s what it looks like to me. Also, isn’t it referencing GLIBCXX i.e. libstdc++, which not even a part of Glibc?)

[ Parent | on HN ]
Re:The Windows malloc() implementation from MSVCRT is slow by password4321 on Saturday July 02, 2022 @09:30PM (#31964216)
> referencing GLIBCXX i.e. libstdc++, which not even a part of Glibc

You're right, so not an example of a glibc failure, but rather another standard library. Thanks!

[ Parent | on HN ]