Conversation

Notices

1. Embed this notice
   Mek101 (mek101@fosstodon.org)'s status on Tuesday, 13-Feb-2024 07:11:56 JST Mek101

   Why Singletons are Evil
   https://web.archive.org/web/20090803101519/http://blogs.msdn.com/scottdensmore/archive/2004/05/25/140827.aspx #programming

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Tuesday, 13-Feb-2024 07:11:55 JST iced depresso

     in reply to
     @Mek101 i usually try to see if i can find any reason somebody might ever create two of a thing before deciding on a singleton. even if that reason is slightly contrived.
     
     i know janet uses thread-local variables so avoid having to pass state variables around commonly as lua does. not a decision i'm super thrilled with at times but i get why calvin did it.
     
     there's a lot of that you can design the singleton as though there could be more than one, and the add a facade that just communicates with the "default" instance of the class, which might even just be a thread local variable, since i think what people mostly want out of singletons is to primarily have everyone talk to the same object (with rare edge cases, like when you get in to a multi tenant scenario, where you might actually have some reason for having a second Application instance)
   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Tuesday, 13-Feb-2024 07:13:11 JST iced depresso

     in reply to

     • iced depresso
     @Mek101 basically singletons seem to me like when you forced someone to use oop boxing and then they don't want to do that and are just being maliciously compliant about it. lol