So you have to add “fs” or “filesystem“ to your search queries, or not even that if the rest of the query gives sufficient context.

Everyone makes name conflicts in independent domains to be a much bigger problem than they are in reality.

There’s Amazon rainforest, Amazon the ecommerce website, and Amazon the cloud company. How often do you have any problem differentiating between them?

Well.. let's google it... "TFS" .. hmm, abbridged lead in to the wikipedia article at the top... And though I'm not a systems programmer likely to implement, or support the code for a filesystem, I am A programmer, and work in IT... And systems operators are also likely to come accross TFS (Team Foundation Server) in terms of supporting a deployment of it.

Though, they've started to refer to the source control protocol implementation as TFVC, since TFS supports git as well now. It does seem to have some conflicts, and even notes another file system called TFS themselves.

In this case, I'm pretty sure another name might be a better idea. Hell, TFS the version control system and the other file system are more well known than Firebird the database when Mozilla renamed their shiny new browser.

If you’re looking for Java and the first result is the Wikipedia article on the island[1] do you just switch programming languages?

I hear C is very search engine friendly. Probably why it’s so popular.

[1] https://en.wikipedia.org/wiki/Java

The point is, there's already a prevalent technology in use by the same name... I wouldn't really expect to choose a programming language based on google-ability... go, is to this day hard to search for on its' own, "golang" being better.

That said, I wouldn't expect a "new" programming language called "Java-Script" (not the current ES/JavaScript) to gain traction. Or for that matter a programming language called "Coffee" to be very successful either.

There are at least two other filesystems called TFS, how hard is it to just add another character to the acronym, tbh(fs)?

You're tilting at windmills. Most threads where someone starts something new has someone making similar complaints to the one you're making here. Yet people's behavior doesn't change. And it won't -- it's just too much overhead to avoid the ever-expanding space of products that have the same name.

Yes, but there's at least two other filesystems called TFS as well, per other threads... so even then, it's still overload. If I were releasing something to the public, I would probably namespace or consider something different in this case.

I did. It’s still not synonymous with “popular.”

It’s not “prevalent technology.” It’s a proprietary product published by a well-known software company.

If you want Microsoft’s TFS just search for “Microsoft TFS.” There is no confusion.

See the definition of prevalent... Even if it's proprietary, it's pretty widespread... not to mention other file systems called TFS already.

For what it's worth, I think you should have taken the advice of the guy you're replying to. The first result for "TFS file system" is https://github.com/redox-os/tfs.

The first result I get is: GitHub - alibaba/tfs: TFS (Taobao File System) is a distributed file ...

It's more than just a bad VCS. It's a bad bug tracker, a bad build system and a bad workflow system as well.

But yeah, if I wanted a set of three letters than suggested quality and reliability, TFS would be near the bottom of my list.

Actually I am yet to find a CI system that allows the TFS workflow of preventing checkins if the unit tests fail.

All the other ones I know require creating scripts that will manage branches and merges into the main branch.

On TFS I select a check box and go off doing something else.

This thread has got quite long but no-one's mentioned the fact you can achieve the same thing with triggered merges: https://blog.jetbrains.com/teamcity/2013/10/automatic-merge/

Thanks for sharing, I wasn't aware of it.

The more you discourage checking in the harder merging becomes.

In some type of enterprise projects I am quite glad that merge never takes place.

I don't want to have a CI build that is green only a few days when all planets are aligned.

> In some type of enterprise projects I am quite glad that merge never takes place.

Surprise! Now you have 2 versions of an app to support, with twice the resource requirements.

No I don't.

I and everyone else on the team enjoys the fact that broken code produced by offshore developers that should have been fired in first place, never touches the official development repository.

Those developers will eventually produce something that passes the unit tests and gets merged, instead of borking the build for weeks.

Should the process done in another form with code reviews and such, yes but that isn't how many enterprise projects are managed.

Note that I am only referring to those that can't learn to code even if we ELI5 them.

There are others on the offshore teams that are highly skilled, but like us onsite, cannot do anything to change the rules of the game.

I read the TFS github landing page and it didn't explain what the 'T' stood for. I then noticed the author's name is "Ticki"[1]. Therefore, I can only guess that TFS stands for "Ticki's File System".

[1]http://ticki.github.io/about/

There is already a tfs file system for flash memory storage. It is prolific in feature phones and other embedded systems. Stands for tiny file system.

The readme also alludes to a file system by terminalcloud which is also apparently named TFS, and doesn't explain what the T is supposed to stand for.

Really poor choice of name. If they wanted a modular replacement for ZFS then call it MFS or ModFS or something...

If it's a successor, they should follow tradition and just pick the letter after Z.

AAFS it is then. To bad it already exists, and even more confusingly also has something to do with a journal :D