5 ms·

> * Viewing diffs requires you to click each file that changed (unlike every other diff/code browser I've used where it has one long page with all the changes)

> * Viewing diffs requires you to click each file that changed (unlike every other diff/code browser I've used where it has one long page with all the changes) This is not my experience. Picking a random project I see a listing of all changes in all files: https://bitbucket.org/atlassianlabs/asap-cli/pull-requests/3/bump-dev-dependencies/diff https://bitbucket.org/atlassianlabs/asap-cli/pull-requests/3... That's for a pull request, this is for a branch: https://bitbucket.org/atlassianlabs/asap-cli/branch/bump_dev_dependencies#diff https://bitbucket.org/atlassianlabs/asap-cli/branch/bump_dev...

ronnier 10y ago
I'm using the "enterprise" version, not the public version. Maybe there's a difference. And yeah, that view you posted is a lot easier to read.
- Karunamon 10y ago
  Can confirm. The enterprise (aka Bitbucket Server) version gives you a two pane layout, with files on the left and changes to those files on the right.
  - ngoldbaum 10y ago
    Bitbucket Server (formerly Stash) is a completely different codebase from Bitbucket Cloud. They share zero code. One is written in Java, the other in Python. It's a constant source of confusion. The naming is because of a terrible marketing decision. Atlassian marketing does all kinds of weird things, like advertising Bitbucket as only supporting git despite also supporting mercurial.
    - nikanj 10y ago
      Almost as bad as Skype vs Skype for Business
- brazzledazzle 10y ago
  Might want to check and see how far behind you are in upgrades. Even though the on-prem version will never have feature parity (new features hit cloud first) it could be that whoever runs your instance hasn't upgraded in a little while.
  - iamaelephant 10y ago
    Feature parity is not really a goal of these products - they are totally separate teams, technologies and languages. If one team develops something awesome then of course the other will try to reimplement, but it's not really the case that features "hit cloud first".
    - brazzledazzle 10y ago
      You're saying the BitBucket cloud and server teams are using totally separate technologies and languages? That's not the impression I've gotten at all at every atlassian conference I've been to. Seems wasteful but nothing surprises me anymore.

ronnier 10y ago

I'm using the "enterprise" version, not the public version. Maybe there's a difference. And yeah, that view you posted is a lot easier to read.

Karunamon 10y ago
Can confirm. The enterprise (aka Bitbucket Server) version gives you a two pane layout, with files on the left and changes to those files on the right.
- ngoldbaum 10y ago
  Bitbucket Server (formerly Stash) is a completely different codebase from Bitbucket Cloud. They share zero code. One is written in Java, the other in Python. It's a constant source of confusion. The naming is because of a terrible marketing decision. Atlassian marketing does all kinds of weird things, like advertising Bitbucket as only supporting git despite also supporting mercurial.
  - nikanj 10y ago
    Almost as bad as Skype vs Skype for Business
brazzledazzle 10y ago
Might want to check and see how far behind you are in upgrades. Even though the on-prem version will never have feature parity (new features hit cloud first) it could be that whoever runs your instance hasn't upgraded in a little while.
- iamaelephant 10y ago
  Feature parity is not really a goal of these products - they are totally separate teams, technologies and languages. If one team develops something awesome then of course the other will try to reimplement, but it's not really the case that features "hit cloud first".
  - brazzledazzle 10y ago
    You're saying the BitBucket cloud and server teams are using totally separate technologies and languages? That's not the impression I've gotten at all at every atlassian conference I've been to. Seems wasteful but nothing surprises me anymore.