Here’s the Deal
Slant is powered by a community that helps you make informed decisions. Tell us what you’re passionate about to get your personalized feed and help others.
Arguments to a function call can be specified in an order that is different from the default order of the function's parameters. It is possible to pick parameters by name irrespective of their declaration order, which produces succinct code in case the function has many parameters with default values. See More
You have to write more lines of code, to declare the interface or abstraction and then the implementation of such abstraction. So the project increases in number of files and lines of code to write. But after this is done the payoff later is well worth it See More
Function/method arguments with default/typical values can be omitted, resulting in a more concise call and hence improved readability. Combined with named arguments/parameters, it negates the need for function/method overloading. See More
If your GC is a black box that can run whenever it wants/needs to and you don't know all of what it does, it's not great for real-time high applications. The GC should be predictable, you should know when it's going to run, for how long, and what's it's going to be doing (destroying objects, freeing memory, defragmenting, etc.). Frankly, a GC isn't entirely needed with a well designed engine/program. See More