4 ms·
The first few lines in the repo you mention illustrate the problem: > Note that this repository is no longer being maintained. Use this at your own risk, and w
by wkat4242 4y ago
The first few lines in the repo you mention illustrate the problem:
> Note that this repository is no longer being maintained. Use this at your own risk, and with the understanding that it is not being maintained, work is being done on its replacement, and that no support or assistance will be offered.
And its replacement syncserver-rs is in this forever-unfinished state so they've effectively killed self-hosting. At least from a support standpoint.
- williamvds 4y agoGood point, I'll update the comment to indicate syncserver is now unmaintained. Of course, everything self-hosted is at my own risk etc. And official support is a luxury in this kind of FOSS, I generally don't count on it. But since it works for me, it may be worth sharing the details.
- wkat4242 4y agoI agree that a lack of support isn't a huge issue for this kind of thing. I'm more worried about the maintenance, like a vulnerability remaining unpatched (it being python 2 doesn't help either) or a protocol change that makes the old server suddenly unviable. I really wish they'd just finish the Rust version. That would solve everything.
- MawKKe 4y agoSounds like classic case of ”Second System Effect”
- ninju 4y agoBetter known as "if its not broken, break it" https://en.wikipedia.org/wiki/Second-system_effect https://en.wikipedia.org/wiki/Second-system_effect
- toyg 4y agoI don't understand. The original was barely 500 lines of code in two files, everything else being packaging machinery. Yes it's python 2, but how hard could have it been to port 500 LOCs to 3.x...? Even assuming some crypto libraries broke, surely there are working equivalents? Instead, they went for a Big Rewrite in Rust, resulting in a much bigger codebase that will be much harder to maintain... and broke it anyway.
- acdha 4y agoTheir issue tracker suggests that it’s mostly due to their team being focused on the main Firefox service: https://github.com/mozilla-services/syncserver/issues/264#issuecomment-754784657 https://github.com/mozilla-services/syncserver/issues/264#is... I’m sure it wouldn’t be that hard to port but if they’re committed to a different direction it’s probably best not to give the impression that you should plan to keep using it.
- toyg 4y agoYeah, but even internally it makes little sense. You've replaced a very simple system built on a widely-known language with a massive ecosystem, something you could even call "boring technology" these days (python), with a larger implementation using a niche language with a small ecosystem and a minuscule pool of skilled developers. It's now even more unlikely you'll ever get any patches from outsiders, it will be harder to hire people to maintain it, harder to monitor and expand the system... And this for a critical system. I mean, as a job-security device, I'm sure it works out great. As a strategic business decision, though, it looks debatable as a minimum - and I'm being charitable.
- acdha 4y agoNot sure you could call Rust a niche language any more given how many devices it’s running on, but especially at the organization which created it that seems like an understandable choice. I have a lot of experience with Python but can totally sympathize with people running a highly-visible service prioritizing resource utilization.
- toyg 4y ago> Not sure you could call Rust a niche language any more First comment under "The Adoption of Rust in Business": https://news.ycombinator.com/item?id=34691509 https://news.ycombinator.com/item?id=34691509 A bit further down: https://news.ycombinator.com/item?id=34691893 https://news.ycombinator.com/item?id=34691893