> People say Linear is fast but it's nothing compared to how well Pivotal worked.
My company switched off Pivotal Tracker because it would slow to a crawl and require several seconds (!!) to load the page, with individual actions causing a DOM cascade that frequently hung browsers. Maybe it worked at small scale but it definitely didn’t work at a large scale.
Oh so you mean mandatory pairing (which does away with the deep thinking required for some algos) and requiring "clean code" and other Uncle Bob BS doesn't contribute to actually scalable and efficient code?
My partner built Velocity Tracker [1], not a clone but it aims to implement the core philosophy of Pivotal. Any and all feedback would be most welcome.
Man, PT was so good. Linear is okay, but I find it really slow - more than once I've opened an existing issue and started editing it, only for a few seconds later the actual content to pop in and make a mess.
If you continue to not find what you need and are willing to be a subject matter expert on what Pivotal actually is (because I never saw it), I would be interested in building this. A lot of people share your sentiment so it could be successful, but it's hard to clone something unless you know the thing.
Pivotal was far from a perfect company (if there can even be such a thing to begin with), but sadly, a lot of good things were lost in its latter days. This was one of them.
Are there particular attributes, behaviors, or properties you feel are important that you can't find elsewhere? I see you mentioned latency, for example — what else is key to you?
They spent A LOT of time building PT. It isn't something easy to replicate, especially if you didn't work at Pivotal Labs and get their knowledge of how to use it. But, you're right, I was just lamenting the other day that there is nothing like it. I wish Rob had just open sourced it.