4 ms·
I actually see that as an advantage: instead of reinventing the wheel, you're using others work as a basis of something that has probably got more functionality
by pm90 12y ago
I actually see that as an advantage: instead of reinventing the wheel, you're using others work as a basis of something that has probably got more functionality and is more useful.
I do agree that this does mess with tinkering with the fundamentals and stuff. But here's my thesis: when you work with a technology for a long time, after a while you will naturally be curios about how the lower level stuff is working. I think this is why a lot of application developers still find systems programming exciting. And also why the hacker news audience is also keenly interested in stuff besides the very narrow focus of cs/ee.
- AnthonyMouse 12y ago> I actually see that as an advantage: instead of reinventing the wheel, you're using others work as a basis of something that has probably got more functionality and is more useful. It's really both. The trouble is you want e.g. a protocol to secure your communications, and designing one yourself while making it secure is a huge ordeal, whereas you could just use TLS for free even though it's full of warts. So everybody uses TLS. Which then snowballs into everyone using OpenSSL for TLS even though it's ancient and full of cruft. The problem is you do want everyone using the well-reviewed long-tested thing, but then that thing becomes a decaying designed-by-committee monstrosity which nobody can fix because it would break compatibility. See also HTML, HTTP, DNSSEC, javascript, etc.