Hacker News Reader

Comment by ronnier | Hacker News Reader

The Bitbucket UI is a mess.

* It takes over your native browsers find feature.

* It's javascript heavy and has multiple panes that scroll, collapse, and expand.

* 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)

View on HN

> * 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...

That's for a pull request, this is for a branch: https://bitbucket.org/atlassianlabs/asap-cli/branch/bump_dev...

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.

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.

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.

Almost as bad as Skype vs Skype for Business

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.

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".

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.

It sounds like you're talking about Bitbucket Server. This article is about Bitbucket Cloud. Some people (myself included) much prefer the Cloud product, some people love the server product - and often they have these opinions for the same reason. File-by-file diff is a good example of this :)

Disclosure, I work for Atlassian, but not on either of these products.

I'm a Bitbucket Product Manager. Thanks for the feedback! This is an area we plan to improve in the Server offering. In particular we're actively looking at ways to make diff nav and find much better.

Are you planning on adding code search feature any time soon (in the cloud, that is)?

Bitbucket PM here, We are currently working on code search for Bitbucket cloud, you can follow our progress here: https://bitbucket.org/site/master/issues/2874/ability-to-sea...

And this is why github won...

I actually prefer bitbucket cloud to github. The pull request workflow in particular is a lot cleaner. Currently ditching both for gitlab tho.

Glad to hear you're switching to GitLab. What made you switch? And how can we maybe improve our pull/merge request workflow?

Reply on news.ycombinator.com