However, I consider that there is still not a great UI for the core service, in special for a complex project.
In the other hand, I bet jujutsu has the best basic take, and is still missing a good forge.
However, I consider that there is still not a great UI for the core service, in special for a complex project.
In the other hand, I bet jujutsu has the best basic take, and is still missing a good forge.
The same goes for Github to a degree. Yes, there are hot paths that "everyone" uses, but also areas where most people never wander and other use daily.
With what I heard about GitHub Actions, the GitLab CI pipelines should be much better.
Not that I haven’t shot myself in the foot with GitLab pipelines on numerous occasions.
pujil's patch alebgra is sick but the whole system implementation is so complex my guy is still toiling away on it, unfinished, after half a decade
At first I thought the KDE apps all playing on the K was kinda weird and awkward, but as time went on I really appreciated how easy it was to search for them due to this. So I really think it's a benefit to play on traditional words rather than use them as-is.
jjplace/jjhub/codetown, whatever. Doesn't matter.
Names don't matter that much for brands. Names just have to be simple enough to remember (ideally two syllables or less). What the heck does Nike mean, for example? Boeing is just someone's name. Microsoft is just two words smashed together. A brand's name literally doesn't matter.
I would guess under 10%, and only that high because Nike sells shoes in Greece and Italy.
("Please don't sue us.")
Mi vidas kion vi tie faris.
For example - We adopted GitHub Actions, then we swapped it out this year. Our own primary use case is code hosting + PRs. We want it to talk to the other (better) tools that intended for their use case. We want it in a secure yet fast and available manner. Nothing else. I don't care about projects, issues, or whatever super app they're trying to become.