4 ms·
I'd worked in Sun Microsystems last 3 years before acquisition by Oracle. We've used version control system based on SCCS. Like CVS is based on RCS format, thi
by blacklion 3y ago
I'd worked in Sun Microsystems last 3 years before acquisition by Oracle.
We've used version control system based on SCCS. Like CVS is based on RCS format, this was based on SCCS.
But it was distributed! Only way to clone repo or push or pill was direct file system access (so, NFS was used, of course), without any protocol over HTTP, SSH or TCP.
It was very cumbersome and difficult to understand & master. I could say, it was more complicated than git, because it felt alien. I don't know why and cannot pinpoint reasons for it.
It had generator for web reviews (like modern pull reviews), but again, generator produced static HTMLs with different diffs, and you need some place to host them and they were non-interactive, nothing like in-line comments and such.
At the very end, right before acquisition, we converted repos to Mercurial, but tools for web reviews was ported to hg with exactly same output. And then I left Sun, errr, now Oracle.
- somnium_sn 3y agoIs that TeamWeaver? I’d love to learn more about it!
- bcantrill 3y agoClose: it was called "TeamWare" (née NSELite). Using TeamWare in the mid-1990s felt like living in the future; I elaborated on its history in [0]. [0] https://www.youtube.com/watch?v=-zRN7XLCRhc#t=2m47s https://www.youtube.com/watch?v=-zRN7XLCRhc#t=2m47s
- somnium_sn 3y agoThank you Bryan! That’s a gem! I’ll incorporate it into one of the next blog posts!
- rsecora 3y agoMaybe you are asking about TeamWare [1]. It was the Sun Microsystems VCS based on SCCS and using NFS. There exists an abundance of resources related to TeamWare. From online documentation [2], to patents [3]... [1] https://en.wikipedia.org/wiki/Sun_WorkShop_TeamWare https://en.wikipedia.org/wiki/Sun_WorkShop_TeamWare [2] https://docs.oracle.com/cd/E19957-01/806-3573/TeamWareTOC.html https://docs.oracle.com/cd/E19957-01/806-3573/TeamWareTOC.ht... [3] https://patents.google.com/patent/US5481722 https://patents.google.com/patent/US5481722