ATTENTION: This is a discussion thread about CENSORSHIP. Please stop using the DOWN VOTE feature against everyone makes a case against censorship - it's simply too ironic, and only goes to show that there is no limit to the censorial impulse.
What will you do when your plan to censor the alt-right backfires and makes the violence worse? Attempt to start rounding them up? And when that makes it even worse?
You don't have a plan, just a knee jerk impulse to censor.
The truth is that information does not radicalize people - censorship does. That's why the channers are as radicalized as they are - they've been censored everywhere else. Censor their last remaining outlets and you will increase violence by orders of magnitude.
The truth is that information does not radicalize people - censorship does. That's why the channers are as radicalized as they are - they've been censored everywhere else. Censor their last remaining outlets and you will increase violence by orders of magnitude.
If ethno-nationalists are not allowed to make their political case with speech, what alternative would they have but violence? You obviously can't change their minds with censorship, only harden them.
If you want something that someone else has got, ask them for it. More often than not, they will give it to you.
If you find someone who is outpacing you, humble yourself for a damn minute and try asking them what they are doing that makes them so effective, then see if you can make it work for you.
If more engineers had this mindset, we'd all be better off.
You know, Dang, this whole thread is a flame war topic. Why didn't you delete that? Oh, I know why, because it supports your side of the ideological narrative.
All people are asking is that you apply your own rules to your own selves. It should be obvious by now that these double standards do not make for community harmony.
For a class X, all functions, including free functions, that both
(a) "mention" X, and
(b) are "supplied with" X
are logically part of X, because they form part of the interface of X.
So yes, f(x) is part of x's interface in C++, and has been considered to be so for a long time.
Please, please, please reconsider not enabling x.f(y) resolve to f(x, y).
You must explain to the detractors that they must reconsider allowing x.f(y) to resolve to f(x, y). This is not a selling out to OO, but in fact the opposite! Allowing x.f(y) to resolve as such enables us to finally get _away_ from OOP by using an alternative style called 'Data Abstraction Style'. I have written up an example of this style here - https://github.com/bryanedds/das
In PLT terms, data abstraction is the dual of OOP. In fact, I use it significantly in F# as a way to do pure functional programming where others just fall back into OOP - https://vimeo.com/128464151
Data Abstraction Style with resolution of free-standing functions to dot syntax gives us the best of both worlds - the increased modularity and extensibility of free-standing functions as well as the nice tooling and API explore-abily of the dot intellisense.
Finally, this syntax is important just to allow extension methods without a more specialized syntax that won't likely appear anyways.
Please pass along this information to the people holding out on allowing x.f(y) resolve to f(x, y) - it is not selling out to OOP - it's an elegant path to finally move beyond it. People must be made to understand this before making their final decision!
Rather than using something inherently complex, entangling, and unscalable like MVC, use composable declarative languages, such as DSLs and monads... but always keep a trap door back to low-level control :)
BTW, I must admit I misspoke on the last sentence - obviously the property of a software system working and doing what the user needs is more important than simplicity.
Too short a road from the obvious to the assumed...