dependency injection not garbage collection
dependency injection not garbage collection
Ki cant fuckin type tonight
Ai like my stuff to just work but that can sometimes cause design annoyances
Mmost normal people hate full assembly DI
Cdesign your engine for your game/project
Kand yet the people who make the stuff keep adding scanning di to things and trying to enforce it
Mppl who make what stuff
Kdi frameworks and stuff that adds on top of it
Moh
Mdi frameworks have to have it because they have to support every stupid ass use case
Kso many add<interface>fromassembly shit
Mit doesn't mean it's a good use case
Kside note i fuckin HATE that in hosted webassembly blazor it just detects the webassembly thing from referenced projects and you cant make it explicit
Mthe library isn't meant to tell you how to code it's meant to be a vessel to let you code how you want to
KI just want unreal engine with C# and like... crash logs that's not 90% C++ nonsense
Aisn't there a C# UE plugin?
Mwe need to let people do stupid shit because that lets people come up with clever shit
Mmono-ue and it's a whole engine fork
AMoh
Kmost of the libraries ive seen that use assembly scanning either dont support not doing it or make it way harder and i hate it. might be just the stuff ive been looking at though
Mwhat libraries have you been looking at
Mi have tried DI frameworks like clothes and they all have assembly scanning under a footnote
Mthere are some usecases for it like if you are writing a plugin system and you're containerizing everything under multiple assemblies
Myou should never immediately dismiss something as bad
Mexcept for singletons
Msingletons are always bad
Awhy so?
Mthey have all the advantages and drawbacks of static, except with the extra drawback of they're confusing and verbose to use
Aeeehhhhh fair ig
Myou never get anything out of using singleton unless there's a specific thing that requires you to like unity scriptableobjects
Msingletons caught on as a cargo cult thing
Ai use them a lot but sometimes i do question why i don't just make everything static instead
since with a singleton there can ofc only be one instance anyway
since with a singleton there can ofc only be one instance anyway
Mit's just one of those weird enterprise programming patterns that made their way into the real world because people didn't really think about the fact nobody actually needs them
Tunity is just bad at state. not to mention the editor being so cursedly integrated
KI had never heard of singletons before I got into unity
KAnd everyone and their grandma was recommending them for everything
Kand i looked into them and it was like... "Wait why not just use a static class?"
Msingletons in unity are just static but you can save them
KNever found the answer
Myou can save them in the editor
Myou can save them at runtime
Mand you can load them at will
Mwhich you can't do with static unless you do some cursed bullshit
Ai just personally like that i can do
new Texture2D(path) instead of new Texture2D(renderer, path)Athat's why i use singletons
KSerialize into json 
Acause the constructor internally gets the singleton instance
Abut i have been tempted to go the second route cause i have increasing dislike for singletons too
Tdevice.CreateTexture my beloved
Myeah i think techpizza is cooking here
