It's weird how today we have memory in gigabytes and multiple core but we try to avoid virtual calls, care about object sizes and stack allocate, but the everything virtual, everything on the heap, refcounting everything designs were made with megabytes of RAM and a single core.https://twitter.com/kneecaw/status/970842293837103104 …
-
-
The only alternatives I can think of are Rust and C++11, which are obviously both relativly new. Was there older ways to deal with memory without either GC overhead or risking breaking something because the human got it wrong?
-
Stack allocation, avoidance of virtual and using something like QScopedPointer (like std::unique_ptr that you can't move) were all possible in 90s C++.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.