LATEST CHATTY HEADER
Subscribe to Shacknews Mercury starting at $1/month!
Chrome Shack Community Guidelines Chatty Search
Scroll down to join the conversation.
New to Shacknews? Signup for a Free Account
Already have an account? Login Now
Subscribe to Shacknews Mercury starting at $1/month!
Chrome Shack Community Guidelines Chatty Search
Scroll down to join the conversation.
Thread Truncated. Click to see all 145 replies.
As the system evolves, if that bottleneck is ever:
1. routed around when new features are introduced
2. eliminated by a more efficient implementation
3. retired
The entire system that was behind it remains as horseshit, and any new entry point is an entry point into horseshit, and it can't handle the future as well as it could have if someone had just made that right choice way back when and gone down the other path.
There is still something worthwhile in making a good choice over a bad one, all things considered, because it's more efficient even if it's not going to have immediate benefits.
I try to tell new programmers that when people make their designs and include "nobody is ever going to want to do that" as a reason to take a sloppy path, they've made an error.
The post has been reported. Thank you!
You must be logged in to post.
You must be logged in to post.