It’s definitely up with Git in my opinion. I much prefer the branching in Mercurial.
It’s certainly very offensive to lump it in the same band as SVN and TFVC.
It’s definitely up with Git in my opinion. I much prefer the branching in Mercurial.
It’s certainly very offensive to lump it in the same band as SVN and TFVC.
The only reason that we stopped using Mercurial is that Microsoft used Git in Azure DevOps. I still wish that they’d supported Mercurial instead of or as well as Git.
I really liked Mercurial too. It was much easier to follow branches to find out if a branch included a commit.
And worse than all of those options is Visual Sourcesafe.
We don’t get that lag but we do frequently get it when the camera doesn’t work for somebody.
I really can’t understand the separation between teams, channels and chats. We almost never use anything other than group chats.
I think that whether it needs plugins or not to do the job isn’t really relevant.
You can develop software in a large number of languages including writing the code (with intelligent code completion), building it, committing it to source control and running and debugging it.
If it didn’t use plugins to do that then it’d huge and take ages to start up.
Microsoft SQL Server is most commonly set up as case insensitive in my (limited) experience (it does support case sensitivity too).
I used to work on an old DOS product and we didn’t have a debugger so we used to have a DEBUG command line argument with
if (DEBUG) printf(“debugging”);
to try to see what was happening and the number of times that code alone fixed the problem was scary.
Maybe it’s not changed then because I was using it in the early 2000s. 😀
We used to use Redmine and it was a fantastic piece of software.
I’m not sure that’s the fault of XML though.
It’s more the fault of the implementation and documentation.
We have a WCF service with an odd configuration and nobody has been able to integrate with it that didn’t use Microsoft tools. It’s definitely not XML’s fault.
(That service has been replaced with a REST API now)
It seems that they intend Microsoft Loop to be the collaborative notes app now.
It’s replaced OneNote as the meeting notes app and it has more flexible access control.
Currently they also only have one version as it’s a progressive web app (that might change with time though).
I guess that that’s all that matters.
Did it take time to get used to or did it work straight away?
Is it saying that the PHP developers are kids and the C++ developer is acting as their parent?
I’m not sure.
If you want to fork the repo then you make a commit to the original repo giving yourself rights then you make the fork and you’re golden.
I like the scope creep there:
Yeah, I agree. I never really minded ads as I just mentally ignore them so I didn’t use an ad blocker for a very long time after it was common practice. I also disagreed with the principle of ad blockers as sites need to pay their expenses.
But then they abused the data that they collected to change people’s political opinions in a way that went way beyond just your standard political ads and that was it for me.
I was aware that they made that change but I didn’t know it made it worse for tracker blocking. I don’t see ads and I don’t get the external discussions such as discus so it seems to work.
I’ll check it out.
Technically, I don’t block ads. I block trackers using privacy badger. If they were to just show me ads without trying to track me I’d be fine and they’d get some ad revenue. But they always put trackers in there, I see no ads and they get no money.
It’s not the mechanism of branching that I prefer.
It’s the fact that Mercurial tags the commit with the name of the branch that it was committed to which makes it much easier to determine whether a commit is included in your current branch or not.
Also, Mercurial has a powerful revision search feature built in which I love (https://www.mercurial-scm.org/doc/hg.1.html#revisions).