I also wonder how this impacts JetBrains' transiti...
# random
e
I also wonder how this impacts JetBrains' transition from internal tooling like Space. I guess Space/Upsource was cool as it was on-premise and not dependent on GitHub's own (un)reliability.
v
Well, you can also run GitHub on-premise 🙂
➕ 1
e
That would be ES, and at that point it would just be better to keep using Space considering how much it costs per seat!
v
If Space would still exist, yes. If one does neither want to rely on GitHub stability, nor afford paying for GitHub Enterprise, one could still decide to use the ugly cousin GitLab as long as the community edition or free tier is enough. 🤷‍♂️
Or use Gitolite for the Git hosting on-premise if you don't need the fancy stuff around, and use TeamCity and YouTrack for CI and Issue Tracking. 🙂
Not as integrated as GitHub, GitLab, or Space, but awesome tools
e
Or even a self hosted Forgejo/Gitea. But then you need to build all the synchronization that was "free" on Space. I'm still really surprised they discontinued it.
h
Also, the GitHub data residency environments are way more stable
c
AFAIK Space still exists and is still used internally by JB
s
no way they took it away from me but keep using it themselves kodee grumpy
v
Why not?
s
because I really liked it
v
Well, probably too few liked and bought it to keep maintaining it publicly. 🤷‍♂️
s
obviously. but the expectations might also have been too high. not many will move their entire project management and code to a new platform
c
I can't cite a JetBrains platform that lasted more than a few years… Difficult to invest in that
I was one of the early adopters for my open source stuff, but it didn't match open source use-cases. It was promising for small companies though
s
yeah I'm also growing more cautious, there are more sunsetting announcements than releases