DrDimension
How can people be this ignorant of recent history?
If a man can't speak his truth, what alternative does he have to violence?
You don't have a plan, just a knee jerk impulse to censor.
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.
Functional Programming and Data-Oriented Design in Games
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.
How Research Was Gutted in the Software Industry
Engineering Integrity vs. Cultural Marxism – Disastrous Ideas in Tech
We're all pretty sick of your badgering everyone with differing opinions, dang.
If you want a safe space insulated from intellectual diversity, try NeoGaf.
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.
Double Cone Design – A Highly Effective Way to Design Functional Programs
‘Professionalism’ Considered Harmful – In Defense of Hacker Culture
According to the classic C++ article, "What's in a class?" by Herb Sutter (http://www.gotw.ca/publications/mill02.htm) -
The Interface Principle suggests -
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
I have also written an entire C++ core library in said style here - https://github.com/bryanedds/ax
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.
Additionally, there are precedence for this functional is less OOP-y language like D and Rust - http://www.drdobbs.com/cpp/uniform-function-call-syntax/2327... https://github.com/rust-lang/rust/issues/16293
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!
#HackerLivesMatter – Systemic abuse in the software industry is taking lives
This is how I built my UI system in my functional game engine - https://github.com/bryanedds/NuGameEngine
More detail - https://github.com/bryanedds/NuGameEngine/blob/master/Nu/Doc...
Sharing Is the Root of All Contention: On Ending Collective Code Ownership
Just say 'No' to benefits-only analysis
Too short a road from the obvious to the assumed...
In the future, I hope that FP will be the default design choice, with objects being used where needed such as for components, plug-ins, and ad-hoc dictionary-passing-style tools.
After all, simplicity is the most important property of any software system - http://www.infoq.com/presentations/Simple-Made-Easy
Iterative Functional Reactive Programming with the Nu Game Engine: An Exp Report
This is an experience report on the design and usage of the Nu Game Engine, a purely-functional 2D game engine written in F# -http://goo.gl/PRHqOpOriginal link here -https://github.com/bryanedds/FPWorks/blob/master/Nu/Documentation/Iterative%20Functional%20Reactive%20Programming%20with%20the%20Nu%20Game%20Engine.pdf?raw=trueSynopsisThe Nu Game Engine certainly qualifies as 'functional reactive'...
Also, let's reverse your argument -
"you make the free-market the source of all evil. blame a lack of regulation, blame the people working in corporations, regulate their pay as well. what happens? free-market service will suck. no one qualified wants to work there. a self fulfilling prophecy."