Bro is associated with obnoxious, stupid, despicable, disrespectful.

Just look at the effort and energy dispersed in discussing the name here that could have been used to improve their database if they had chosen a good name for their tool.

Bro is a user provided database of one liner command which you have no idea if they will do what they claim when they do work.

To most people english is a foreign language which makes it improbable they would get a play on english slang words.

'bro' is not even loosely related to man: man is a pager interface for system documentation, it is standard, has existed for decades and comes with pretty much every *nixes and is related to the info command. The content man displays is written by knowledgeable people (developers, maintainers, etc.) and is split in several sections: 1 Executable programs or shell commands 2 System calls (functions provided by the kernel) 3 Library calls (functions within program libraries) 4 Special files (usually found in /dev) 5 File formats and conventions eg /etc/passwd 6 Games 7 Miscellaneous (including macro packages and conventions), e.g. man(7), groff(7) 8 System administration commands (usually only for root) 9 Kernel routines [Non standard]

On the other hand, bro is a brand new non standard ruby utility as an interface to a database of user provided one liner command examples ranked through a voting system that could probably be easily gamed. Its content right now is uncategorized and of dubious quality with some command not being working examples, some missing explanation to even being outright malicious.

Those two very different tools are hardly related in any way.

Lastly, fsck stands for file system check, its name is suited to its use and follows a tradition of clever naming which answer the need to be concise, indicative of its use and somewhat intuitive.

see cp for copy, mv for move, mkdir for make directory, cat for concatenate, chown for change ownership, du for disk usage, df for disk free, ls to list files, rm to remove files, rmdir to remove directories, sed for stream editor and so on.

Asking for a rename of fsck to love is just the perfect example against the point you're trying to make, that what you say is relevant to this discussion.

Here are a few suggestions of names:

- ccex for common case examples - howdoi for how do I - comcasex for common case examples - usex for use examples - usagex for usage examples - howtouse for how to use - ill-namedpoorlythoughtoutcommand for bro - loudandobnoxiousdespicableman for bro

Naming your command based on an inside joke renders it pretty useless to those outside who don't get the joke and hard to find when you don't already know the name.

Less being named from more makes sense, both are common terms and less is more. But bro as a related thing to man when it is actually something totally different is too far fetched to make any sense.

A loud and obnoxious fraternity guy with partying, acting stupid and engaging in despicable behavior as their life style.

1. Obnoxious partying males who are often seen at college parties. When they aren’t making an ass of themselves they usually just stand around holding a red plastic cup waiting for something exciting to happen so they can scream something that demonstrates how much they enjoy partying.

2. An alpha male idiot. This is the derogatory sense of the word (common usage in the western US): white, 16-25 years old, inarticulate, belligerent, talks about nothing but chicks and beer, drives a jacked up truck that’s plastered with stickers, has rich dad that owns a dealership or construction business and constantly tells this to chicks at parties...

man is short for manual following a unix tradition, bro is a word associated with despicable attitude and stupid behavior holding those as life goals which has absolutely no link with its actual use.

There is no way I'm sharing my library of command examples I built for myself over the years with this ill-named initiative.

I have a local set of files full of notes and examples and I will not share them with bro pages for two reasons: 1) the name 2) the ruby requirement which limits its reach and usefulness.

Turns out this is a policy assessment of those companies and whether they publicly stand on the side of users when the government attempts to seek access to private data.

This a 6 point assessment: 1. Require a warrant for content of communications. 2. Tell users about government data requests. 3. Publish transparency reports. 4. Publish law enforcement guidelines. 5. Fight for users’ privacy rights in courts. 6. Fight for users’ privacy in Congress.

A nice attempt at sorting out people through self-selection who are to be put on a special surveillance list.

I wish those guys luck in trying to push against government surveillance towards private for profit transnational corporations' surveillance, but there is no way I would support this kind of initiative.

Either you fight against surveillance or you don't, but fighting some form of surveillance and promoting another is not fight against surveillance.