home.social

#garbagecollector — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #garbagecollector, aggregated by home.social.

  1. Można by przypuszczać, że zarządzanie pamięcią w dobie nowoczesnych języków z #GarbageCollector mija się z celem. Ale jednak warto wiedzieć, co dzieje się pod kopułą, np. w tak popularnym #JavaScript. Do przejrzenia.

    #programowanie #WebDev #Memory

    javascript.plainenglish.io/how

  2. Oh, look! A toddler's journey into the wild world of memory management 🤯. "Baby's Second Garbage Collector"—because every fledgling coder needs a sequel to their first trash can 🗑️. Apparently, this is where your programming skills go to die of boredom. 💀
    matheusmoreira.com/articles/ba #toddlerCoding #memoryManagement #garbageCollector #programmingHumor #techJourney #HackerNews #ngated

  3. So thinking about asyncronous programming again and how I probably need to ditch #dlang's GC if I want performance and then it hit me:

    Why tf is std.socket.Socket an heap-allocated, gc'd class to begin with?!?!

    It dosn't uses syncronized that would require a classes monitor, nor does it hold any significant amount of data.

    • a socket_t (fancy 32-bit fd)
    • a ushort-enum for the address family (16-bit)
    • and an bool under windows, which in an asyncronous context we could remove since all will always be non-blocking

    So in sum it holds 48-bit of data, while an pointer on modern systems will always be 64-bit (classes are always pointers / by ref in dlang).

    Sure, it "uses" inheritance for 2 wrapper types TCPSocket and UDPSocket, which dont actually do anything other than pre-filling the type/protocol arguments in the constructor, which dont even survive after the call to socket(2)...

    Is the std really that badly engineered at times or am I going crazy???

    #dlang #programming #development #async #networking #garbagecollector

  4. So thinking about asyncronous programming again and how I probably need to ditch #dlang's GC if I want performance and then it hit me:

    Why tf is std.socket.Socket an heap-allocated, gc'd class to begin with?!?!

    It dosn't uses syncronized that would require a classes monitor, nor does it hold any significant amount of data.

    • a socket_t (fancy 32-bit fd)
    • a ushort-enum for the address family (16-bit)
    • and an bool under windows, which in an asyncronous context we could remove since all will always be non-blocking

    So in sum it holds 48-bit of data, while an pointer on modern systems will always be 64-bit (classes are always pointers / by ref in dlang).

    Sure, it "uses" inheritance for 2 wrapper types TCPSocket and UDPSocket, which dont actually do anything other than pre-filling the type/protocol arguments in the constructor, which dont even survive after the call to socket(2)...

    Is the std really that badly engineered at times or am I going crazy???

    #dlang #programming #development #async #networking #garbagecollector

  5. So thinking about asyncronous programming again and how I probably need to ditch #dlang's GC if I want performance and then it hit me:

    Why tf is std.socket.Socket an heap-allocated, gc'd class to begin with?!?!

    It dosn't uses syncronized that would require a classes monitor, nor does it hold any significant amount of data.

    • a socket_t (fancy 32-bit fd)
    • a ushort-enum for the address family (16-bit)
    • and an bool under windows, which in an asyncronous context we could remove since all will always be non-blocking

    So in sum it holds 48-bit of data, while an pointer on modern systems will always be 64-bit (classes are always pointers / by ref in dlang).

    Sure, it "uses" inheritance for 2 wrapper types TCPSocket and UDPSocket, which dont actually do anything other than pre-filling the type/protocol arguments in the constructor, which dont even survive after the call to socket(2)...

    Is the std really that badly engineered at times or am I going crazy???

    #dlang #programming #development #async #networking #garbagecollector

  6. So thinking about asyncronous programming again and how I probably need to ditch #dlang's GC if I want performance and then it hit me:

    Why tf is std.socket.Socket an heap-allocated, gc'd class to begin with?!?!

    It dosn't uses syncronized that would require a classes monitor, nor does it hold any significant amount of data.

    • a socket_t (fancy 32-bit fd)
    • a ushort-enum for the address family (16-bit)
    • and an bool under windows, which in an asyncronous context we could remove since all will always be non-blocking

    So in sum it holds 48-bit of data, while an pointer on modern systems will always be 64-bit (classes are always pointers / by ref in dlang).

    Sure, it "uses" inheritance for 2 wrapper types TCPSocket and UDPSocket, which dont actually do anything other than pre-filling the type/protocol arguments in the constructor, which dont even survive after the call to socket(2)...

    Is the std really that badly engineered at times or am I going crazy???

    #dlang #programming #development #async #networking #garbagecollector

  7. So thinking about asyncronous programming again and how I probably need to ditch #dlang's GC if I want performance and then it hit me:

    Why tf is std.socket.Socket an heap-allocated, gc'd class to begin with?!?!

    It dosn't uses syncronized that would require a classes monitor, nor does it hold any significant amount of data.

    • a socket_t (fancy 32-bit fd)
    • a ushort-enum for the address family (16-bit)
    • and an bool under windows, which in an asyncronous context we could remove since all will always be non-blocking

    So in sum it holds 48-bit of data, while an pointer on modern systems will always be 64-bit (classes are always pointers / by ref in dlang).

    Sure, it "uses" inheritance for 2 wrapper types TCPSocket and UDPSocket, which dont actually do anything other than pre-filling the type/protocol arguments in the constructor, which dont even survive after the call to socket(2)...

    Is the std really that badly engineered at times or am I going crazy???

    #dlang #programming #development #async #networking #garbagecollector

  8. 🤖🎉 Welcome to Fil's Fantastical Fiasco of a Garbage Collector, where incomprehensible jargon meets impractical implementation! 🌪️ FilC's 🤯 mind-bogglingly complex code sits in fugc.c, yet miraculously requires an entire entourage of support logic just to function. 💻 So, grab your favorite debugging tools and a stiff drink, because you'll need both! 🍻😂
    fil-c.org/fugc #FilFantasticalFiasco #GarbageCollector #ComplexCode #DebuggingTools #CodingHumor #HackerNews #ngated

  9. 🚮 Oh joy, yet another groundbreaking GitHub issue about a "green tea" garbage collector that promises to save the world from memory leaks🍵, if only anyone could stay awake long enough to care. Meanwhile, GitHub Copilot is still trying to figure out what to do with all this hot air♨️ and more security holes than a sieve🔍.
    github.com/golang/go/issues/73 #GitHubIssues #GreenTea #GarbageCollector #MemoryLeaks #GitHubCopilot #HackerNews #ngated

  10. 🚮 Oh joy, yet another groundbreaking GitHub issue about a "green tea" garbage collector that promises to save the world from memory leaks🍵, if only anyone could stay awake long enough to care. Meanwhile, GitHub Copilot is still trying to figure out what to do with all this hot air♨️ and more security holes than a sieve🔍.
    github.com/golang/go/issues/73 #GitHubIssues #GreenTea #GarbageCollector #MemoryLeaks #GitHubCopilot #HackerNews #ngated

  11. 🚮 Oh joy, yet another groundbreaking GitHub issue about a "green tea" garbage collector that promises to save the world from memory leaks🍵, if only anyone could stay awake long enough to care. Meanwhile, GitHub Copilot is still trying to figure out what to do with all this hot air♨️ and more security holes than a sieve🔍.
    github.com/golang/go/issues/73 #GitHubIssues #GreenTea #GarbageCollector #MemoryLeaks #GitHubCopilot #HackerNews #ngated

  12. 🚮 Oh joy, yet another groundbreaking GitHub issue about a "green tea" garbage collector that promises to save the world from memory leaks🍵, if only anyone could stay awake long enough to care. Meanwhile, GitHub Copilot is still trying to figure out what to do with all this hot air♨️ and more security holes than a sieve🔍.
    github.com/golang/go/issues/73 #GitHubIssues #GreenTea #GarbageCollector #MemoryLeaks #GitHubCopilot #HackerNews #ngated