Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sourcehut welcomes Bitbucket refugees

sourcehut.org

Post reply on HN
Print view View original

171–180 of 219 posts

Re: Sourcehut welcomes Bitbucket refugees

#171

Post by jason_s »

steve_adams_86 wrote: post #164
todd3834 wrote: post #161

I literally forgot about Mercurial. It’s been years since I’ve even heard it mentioned. Are there any strong arguments for using it over Git these days? Is this just about supporting legacy code bases. I’m sure there must be a way to migrate to Git [and maintain history]. I’m not trolling, I would love to hear from someone who prefers Mercurial over Git as to how it benefits them.

In my limited experience with Hg, I thought it had a well designed, human-friendly interface. After a decade with git, I still feel like it's an ugly, awkward tool that just gets the job done and I still occasionally make weird mistakes with it. I'm not sure that's the case with other tools I've been using this long. Git has a pretty gross interface, such that people have struggled to make it nicer to use with GUIs f…

...and because Atlassian let Bitbucket's Hg support wither and die.

Re: Sourcehut welcomes Bitbucket refugees

#174

Post by reddotr »

yebyen wrote: post #108
quietbritishjim wrote: post #99

Earlier quoted context omitted.

There are a few good things about it compared to git (and a few bad ones). One I like is that it has an excellent GUI that is cross platform, called TortoiseHg. I know hackers can be a bit snobbish about GUIs but I really think a GUI is essential for version control: flicking through the revision graph in one pane while looking at the modified files in another and a file's changes in a third is much more efficient th…

I know you said GUI, but this single-line git alias that goes in ~/.gitconfig changed my life and I don't look for a git GUI anymore: [alias] l = log --date-order --date=iso --graph --full-history --all --pretty=format:'%x08%x09%C(red)%h %C(cyan)%ad%x08%x08%x08%x08%x08%x08%x08%x08%x08%x08%x08%x08%x08%x08%x08 %C(bold blue)%aN%C(reset)%C(bold yellow)%d %C(reset)%s' Next, go to one of your git project directories and ty…

Finally ended with such a modification:

  [alias]
  glog = log --date-order --graph --all --date=short --pretty=format:"%x09%C(auto)%h  %C(cyan)%ad  %C(green)%

Re: Sourcehut welcomes Bitbucket refugees

#175

Post by VictorSCushman »

cowwoc wrote: post #172

It's not clear how to send you feedback and/or ask questions, so I created a new sourcehut tag on Stackoverflow and posted my first question: https://stackoverflow.com/q/57628020/14731 Looking forward to hearing more about your service. Thank you.

I believe Drew is responsive to email at his (work?) email address sir@cmpwn.com. You may want to send him a message directly.

Re: Sourcehut welcomes Bitbucket refugees

#177

Post by The_Tick »

EGreg wrote: post #126
viach wrote: post #41

They violently break all the recent frontend best practices. Where is the React or Vie, SPA architecture, tons of JS? There should be a federal law prohibiting making fast and simple UIs so that nobody will have concerns that the UI frameworks war leads us to great future.

You know, libertarians often watch train wrecks and wonder how people can so clearly report problems and commiserate but the obvious solutions never seem to come up. Refugees... from a third party service... because things changed since they began there Some other third party service welcomes them, but has bad front end... SOLUTION: 1. Mercurial and Git are decentralized! They have been designed to be so. Make your b…

For #1, yes it's decentralized but when running a team of people having a central clone is ideal. Yea I get it you can push and pull all day long but in reality people want to have a centralized location.

The big appeal for moving to mercurial for us was better merging than svn. Our team worked a certain way already, the tool handle this workflow and that's one of the reasons we chose mercurial. Decentralized was just nice for full backups in a lot of ways.

Re: Sourcehut welcomes Bitbucket refugees

#178

Post by juped »

EGreg wrote: post #126
viach wrote: post #41

They violently break all the recent frontend best practices. Where is the React or Vie, SPA architecture, tons of JS? There should be a federal law prohibiting making fast and simple UIs so that nobody will have concerns that the UI frameworks war leads us to great future.

You know, libertarians often watch train wrecks and wonder how people can so clearly report problems and commiserate but the obvious solutions never seem to come up. Refugees... from a third party service... because things changed since they began there Some other third party service welcomes them, but has bad front end... SOLUTION: 1. Mercurial and Git are decentralized! They have been designed to be so. Make your b…

You're replying to a sarcastic comment which is actually intended to praise Sourcehut's good frontend, hope that helps.

Further, it's a completely open source product which strongly encourages self-hosting; the main reason to subscribe to the hosted instance is to give money to the dev.

Re: Sourcehut welcomes Bitbucket refugees

#179

Post by ignaloidas »

hmnom wrote: post #97
kdmccormick wrote: post #95

Earlier quoted context omitted.

I imagine that the CPU-intensive parts of Flask and Jinja2 are already written in C. Much of Python's standard library is. 800ms is a reasonable response time, and if they scale up according to their userbase, they will hopefully maintain that time. (Also, we don't know how much of that 800ms is Python vs. IO)

https://github.com/pallets/flask https://github.com/pallets/jinja 0% C Also 800 ms is NOT a reasonable response time to generate what basically is a bunch of text, that is absurd, but I guess this is the baseline in 2019. I trust all IO is cached. The author can confirm it. This is just how slow Python is.

Almost none of the IO of that page is cached actually[0]. The only thing I'm sure that is cached is the templates themselves. I'm pretty sure that neither git lookups, nor DB accesses are cached, where you can save time. And mind you, this is served from a single data center in USA, and the latency can already eat up a lot of that. I in Europe have 300ms ping to it, so it might be that you are simply far away from the physical location.

[0] https://git.sr.ht/~sircmpwn/git.sr.ht/tree/master/gitsrht/bl...

Re: Sourcehut welcomes Bitbucket refugees

#180

Post by juped »

whatshisface wrote: post #86

People seem pretty interested in keeping their pre-git source control system, even if it means switching repository hosts. I know the default attitude is "they're just curmudgeons who don't want to change," but Hg could have some advantages.

If you can avoid inflicting a painful VCS migration on yourself, you probably should.
Post reply on HN