I read it as "some forks are successful", and well, you need to fork to be a successful fork.

You may note that when US goes to war nobody boycott the US.

It reads to me that you are afraid of getting your project removed if you ever move. No need to pretend you care about the morality of their decision.

Which was one of the most non-sensical word to say "You don't maintain the server".

Likewise, you could ignore his comment but decided to engage.

This is not what is written here:

> Git is not nearly as confusing as people make it out to be. They just never take the few hours it takes to understand it. Which is a sad state of affairs for such an essential tool in the belt of any software engineer.

> just does not cut it, if you call yourself a professional.

I'll repeat myself, I can show you thousands of messages point out how git is confusing. I can show you plenty of message saying "I used X it was fine, but I used git and it's cumbersome", please show me the same amount of messages telling "I used git it was fine, but I used XXX and it's cumbersome."

I could show you thousands of message backing up the confusion.

But you can keep nitpick irrelevant part of messages and pretend you are very smart.

I didn't ask why git was widely used. I didn't say git was useless.

Again, there were version controls before git came out.

No one said everything should be easy as pie.

There are other software similar to git that have not such reputation. Version control is not new.

If your product has a reputation to confuse users compared to other products, your product confuses users.

Let's not start to bend reality just to back up some narrative because after reading a N hours documentation everything is OK.

The people are confused, it's a fact. So it is confusing. Stop gaslighting people.

I'm paid to provide good quality code and not flood my company with more average code than it should.

In my previous job, I could regularly reduce a PR code down to 10-20%% of its size because someone overlooked something or was just "overengineer" a feature.

AI are such "bullshiters" that they produce more text than necessary.

Code bloat was already real, but from my personal experience it becomes realer with AI. The outcome of this will likely be apparent when no one can dive into any code base because of the amount of fluff in it (and you will obviously need more AI to deal with this).

Serious question, is there any kind of entities that can be owned, but not "dismantled", if you don't want it you need to try to sell or make it independant.

Would there be any chance to make it a thing when a company is bought?

Is there any standard protocol/format for "layers" that could be added to such Map apps?

Let's say I want to write a plugin to add my own kind of data, and then I want to export this new kind of data so that someone can import them.

Or I want to create a website with my own data on top of existing one.

Seeing mold in joints is not unusual depending on the conditions, but it's also easily fixable.

For cockroaches either there is none in your area, either get one in a year "by mistake", but if it's a recurring events the problem is likely food or garbage that sits longer than it should.