home.social

#garbagecollector — Public Fediverse posts

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

  1. 🚮 Python 3.14's garbage collector was such a "hit" that the team had to yank it out faster than you can say "incremental memory mismanagement." 🤦‍♂️ Apparently, the only thing it collected was complaints. 🙄
    theconsensus.dev/p/2026/06/06/ #Python314 #GarbageCollector #MemoryManagement #TechNews #ProgrammingFails #HackerNews #ngated

  2. 🚮 Python 3.14's garbage collector was such a "hit" that the team had to yank it out faster than you can say "incremental memory mismanagement." 🤦‍♂️ Apparently, the only thing it collected was complaints. 🙄
    theconsensus.dev/p/2026/06/06/ #Python314 #GarbageCollector #MemoryManagement #TechNews #ProgrammingFails #HackerNews #ngated

  3. Ah, the dream of a garbage collector that doesn't implode without a safety net. 🤡 Rust devs swoon over the #fantasy of avoiding 'unsafe', writing libraries that *almost* hide their unsafe code... except where it counts. 🚀 Good luck enumerating those GC edges; it's like herding cats blindfolded! 🐱‍👤
    fitzgen.com/2024/02/06/safe-gc #RustLang #GarbageCollector #UnsafeCode #Programming #HackerNews #ngated

  4. Ah, the dream of a garbage collector that doesn't implode without a safety net. 🤡 Rust devs swoon over the #fantasy of avoiding 'unsafe', writing libraries that *almost* hide their unsafe code... except where it counts. 🚀 Good luck enumerating those GC edges; it's like herding cats blindfolded! 🐱‍👤
    fitzgen.com/2024/02/06/safe-gc #RustLang #GarbageCollector #UnsafeCode #Programming #HackerNews #ngated

  5. 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

  6. 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

  7. 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

  8. 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

  9. 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

  10. 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

  11. 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

  12. 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

  13. 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

  14. 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

  15. 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

  16. 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

  17. Tambaram mornings are a spiritual blend of Margazhi kolams, bhajans, and… suspense thrillers. Forget @Netflix—our true cliffhanger is waiting for the #GarbageCollector, the area’s unofficial mascot of unpredictability. Will he arrive at 6 AM? 9 AM? Or just when you’ve stepped out for work?