devs struggle to write code for unity because they usually lack previous programming skill
devs struggle to write code for unity because they usually lack previous programming skill
Mthat's not a slight
Mthat's just unity being good for first timers
L(or because unity is a complete and utter mess)
Tunity is not fine, and probably never will be
KI think unity is just a bit crippled due to the company constantly ripping out and shoving in things because they're desperate to show investors they're worth the effort
Kyeah
Lunity is filled with promotion chasing
Asolution to the problem: they should actually make a game with it
Ashows the investors its actually usable to make a game
Mthey do that shit all the time... i mean tech demos
Kalso im an aggressive hater of the sort of gameobject tree setup that unity uses just on a personal stylistic basis
KI think basically every feature in unity atm is like.... the functional stuff is (DEPRECATED) meanwhile the replacement lacks like 50% of the featureset of the old version
Lits just project managers making something because "oh jeez i need to prove my job actually matters"
Aand maybe they'll accidentally create a huge success like forknife 2 or whatever the heck kids are into nowadays
Mi love the gameobject entity-component setup it's lovely
KOh they did that, their dogfood project, and then they randomly fired that entire department because... reasons
Ka lot of people do like it and i understand why but i hate it
Mi have ten years coding my own engine experience under my belt and i don't ever want to go back
Aoh yeah they did start making one didnt they lmao
Ki hate assembly-scanning garbage collection type stuff for the same reason
Kanything i should expect to magically work i hate on principle
Ai try to design my stuff to work like this and it causes some real issues during development leading me to procrastinate and never get anything done
Kdependency 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?
