GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Embed Notice

HTML Code

Corresponding Notice

  1. Embed this notice
    Björkus "No time_t to Die" Dorkus (thephd@pony.social)'s status on Friday, 17-Oct-2025 05:03:19 JSTBjörkus "No time_t to Die" DorkusBjörkus "No time_t to Die" Dorkus
    in reply to

    YEEEAH TALK YO SHIT, MALLOC SUCKS, CALLOC IS AWFUL, REALLOC IS GARBAGE, NO ALIGNMENT NO SIZES IT'S A "REALLY BAD API" THAT'S RIGHT BILL TALK TO 'EEEEEEEEEEEEM!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    Everyone is agreeing that the whole C standard library design is shit. Good.

    There's hope for the youth yet.

    "Memory management in C is not actually hard, NO! It's malloc that's hard!"

    Half-agree. Like, this is a complete true statement, but it's missing the "and we don't have good slices and everything's still a pointer".

    "Start with the most descriptive name, THEN compress it later." Bill and Ryan will be happy to know that we've adopted this policy! ... But mostly for very new features/headers. Old stuff will still probably have the compressed names! <stdbit.h> has descriptive names, though, as a recent example.

    "We would remove most stuff from C23, and only work from C11 or C99/89" I've talked about this a lot previously, but honestly it's fine. This is how most C developers are; they consider the things they care about to be the holy grail, and then EVERYTHING else is FOR LOSERS.

    In conversationabout 8 months ago from pony.socialpermalink
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.