yeah. I'm dropping Bitbucket in favor of this for my private projects. BitBucket's UI is so un-intuitive that I (most of the time) dread actually having to log into the web UIs for it.
I'm also just much more comfortable with GitHub since I use it daily in my day job.
precisely. I wholeheartedly agree with this statement as well. The differentiator? Linux, like Chromium, is open-source. I would welcome an OS monoculture with every OS being based upon a linux kernel.
I'll echo tokyodude. Not a valid comparison in the least. The biggest differentiator I can see is that Windows is not, and probably never will be, open sourced. Chromium is.
I would place myself squarely in the camp of those that don't see every browser using Chromium under the hood as a bad thing. It makes every company that has their own browser invested in improving together, for one thing. Also, compatibility across browsers will only get better if that is the case, which is also something that people tell horror stories about from the time when IE was king.
oh look, another fear-mongering firefox ad masquerading as an article that actually warrants reading.
no thanks, I'll pass.
edit: I'll add that I am pretty tired of reading these "Microsoft Edge is dead, long live Firefox" articles like this, where they start with a title that sounds like it is worth reading and in the end it boils down to "Pleeeeeease use Firefox, its betterrrrrr, pleeeeeease!." They are opinion pieces and provide NOTHING of substance or value other than pandering to the current base of firefox users. They won't convince me to switch, and probably never will (in fact, they make me dislike firefox even more than I already do).
Don't care in the slightest about the third-party vendors' complaints. Amazon can control THEIR SITE how they want to control it. They own the site. Don't like their policies? Take your shop elsewhere.
I already stopped trusting third-party vendors on Amazon a LONG time again.
we use a rebase workflow in git at my current employer, and it is amazing.
previous employer used a merge workflow (primarily because we didnt understand git very well at the time), and there were merge conflicts all the time when pulling new changes down or merging new changes in.
It was a headache to say the least. As the integration manager for one project, I usually spent the better part of an hour just going through the pull requests and merge conflicts from the previous day. I managed a team that was on the other side of the world, so there were always new changes when I started working in the morning.