Re:Comparing C and C++ usage and performance with a real wor...
by userbinator on Sunday September 03, 2017 @11:53AM
(#15162072)
That's the classic KISS/YAGNI vs. (not sure if there is an initialism for it) robust extensible modular best practices etc. debate, for which there has been much bikeshed from both sides.
Re:Comparing C and C++ usage and performance with a real wor...
by lmitchell on Sunday September 03, 2017 @06:02PM
(#15164191)
You might be looking for the term 'SOLID' ;)
e: it may be worth noting that I can't for the life of me remember what the I and D stand for... clearly I am much more of a KISS kind of programmer.
Re:Comparing C and C++ usage and performance with a real wor...
by coldtea on Sunday September 03, 2017 @01:35PM
(#15162670)
>This makes sense, and then somebody has a vision for a use case beyond the original imagination, goes to turn the code into a library and spends countless hours smartening up lazy resource management.
That's THEIR problem then.
Why should the original author care for that?
Re:Comparing C and C++ usage and performance with a real wor...
by bch on Sunday September 03, 2017 @02:43PM
(#15163067)
> That's THEIR problem then.
It is their problem, clearly.
> Why should the original author care for that?
That's the question. Don't you think it's easy to think of reasons, though? What if the person porting the code to a library was a later version of the original author?
Re:Comparing C and C++ usage and performance with a real wor...
by coldtea on Sunday September 03, 2017 @06:27PM
(#15164330)
>What if the person porting the code to a library was a later version of the original author?
Then they know what they need to add, and can add it now that they need it -- instead of having it slowing them down when they didn't need it
This makes sense, and then somebody has a vision for a use case beyond the original imagination, goes to turn the code into a library and spends countless hours smartening up lazy resource management. Whether the original author should be "more responsible" is open for debate, but I've personally run into the above situation, and only mention for another perspective on The Life of Code.
Edit: s/coffee/code/