3 ms·
"Less is More" works when you have fewer components but you can assemble them together in various combinations to do everything you could otherwise do with more
by bloodorange 13y ago
"Less is More" works when you have fewer components but you can assemble them together in various combinations to do everything you could otherwise do with more components.
However, when you have fewer components which can't be combined to achieve certain things that you could do earlier, it is hard to see how you can then say "Less is More".
Coming from game development RAII is a blessing. Not having control of memory deallocation is will not sell. This is definitely not a case of "Less is More", it's a case of "Less is Less".
- dbcfd 13y agoNo RAII is one of the things that really bugs me about go. I can't just construct an object and have it be ready, I have to remember to call some other method. Rust's memory model is also better, since it's akin to shared pointers (which you know the lifetime of) rather than garbage collection.
- bloodorange 13y agoWhat I meant was that the way RAII works in C++ is a blessing and it can't work the same way in Golang since it doesn't give us control of when the object is destroyed. So, we are actually in agreement here.