4 ms·
The code is available to see, but they don't necessarily build in an external environment yet and even if they did we aren't ready to support them being used ex
by durham_meta 4y ago
The code is available to see, but they don't necessarily build in an external environment yet and even if they did we aren't ready to support them being used externally. Hopefully we can support them one day, but for now we're just starting with the client.
- wocram 4y ago'one day' is not very reassuring! Improved UX is nice and all, but why would anyone migrate without getting killer performance features like the virtual file system?
- durham_meta 4y agoSorry! 'one day' is the best I can do for now. We'd love to do it sooner, just gotta find the time. We think, and many of our internal users agree, that the UX alone is a worth while upgrade. Since the majority of Git repos don't actually need the performance of a virtual filesystem, the UX is the main sell for them anyway. At the very least maybe it will inspire some UX improvements in Git.
- wocram 4y agoI don't doubt the UX is better, but internal users are a captive audience. I imagine most developers will not think twice about what vcs they are using unless their organization makes the change.