4 ms·
Can somebody shed some light on how maintaining one network protocol implementation and possibly improving it every couple of years could consume three million
by danbruc 12y ago
Can somebody shed some light on how maintaining one network protocol implementation and possibly improving it every couple of years could consume three million Dollars every year? We all know how easy it is to underestimate the required effort and how quickly tiny things can blow up into major issues, but it is completely beyond my imagination in the case of NTP.
- brohee 12y agoYou need drivers for time sources for a start, there are enough of these to use full time devs for years...
- danbruc 12y agoThis sounds like a bad and unsustainable idea, with capital B and U. Shouldn't it be the responsibility of the vendor to provide a driver? Why would you put the burden to deal with all kinds of clock hardware onto someone maintaining a network protocol implementation? I could see reasons to have one or three or so generic drivers, but if the vendor comes up with something fancy not covered by one of the few generic drivers it should be their responsibility to provide a suitable driver.
- gpvos 12y agoMost time sources have other uses than serving NTP time. Those are the uses that people want to pay lots of money for. Serving NTP time isn't very lucrative.
- smackfu 12y agoIt sounds like that is his opinion of what a "proper" support operation looks like, abstract from the actual support requirements of NTP.