• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Jesus's middle name is Hume! Caution: Some NSFW images within!

Page 1843 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
10303750_805259092870463_5324432307976656414_n.jpg
 
Instead of "running" a program, which implies thin privilege and pressure to "work out", programs are "given birth". After birth, a program rolls for a 40% chance of executing literally as the code is written, 40% of being "psychoanalytically incompatible", and 40% of executing by a metaphorical epistemology the order of the functions found in main().
Social Integration

No work done is worthwhile if your friends and followers don't know about it. That's why C+= is heavily socially integrated at its core.

  • In addition to yell(), C+= also provides tweet(), fbShare(), tumblrBlog(), and redditSteal() for a diverse social experience of coding output.
  • Our upcoming Inherpreter 2.0, an LLVM frontend, is going to feature full Social API integration. You must now log in to one of the many social networks before any coding is possible. You can also chat with your friends and like() their social code as you code.
  • Posting or hosting on GitHub, BitBucket, or Google Code is strictly prohibited as these hosting services, self-proclaimed "social coding hub", are actually deeply misogynistic and refuses to host the code of C+=. Any C+= code hosted on GitHub, Bitbucket, and Google Code will automatically trigger all of tweet(), fbShare(), tumblrBlog(), and redditSteal() functions to yell() about GitHub's, BitBuckets', and Google Code's misogyny, and will not stop until any onlooking coders (those who starred or followed the repo) are all named, shamed, exposed, doxxed, fired, lynched, castrated, fired again, and lynched.
There is to be no encapsulation: don't tell me to protect my members, tell other functions not to access them!
This is awesome
 

I'm not sure if I should laugh or cry at this.. I did smile at this though.
<li class="L75">// Remember to check your privilege. Always.<li class="L76"> PrivilegeCheck().<li class="L77">// "std" is sooooo old-fashioned. we use "sti" nowadays.<li class="L78">//cout should be removed immediately as the two letters "co" obviously represent the beginning of a phallus.<li class="L79"> sti::cout of_the_following "Hello, feminists!\n". //Frankly I feel that line escape codes could be problematic<li class="L80">ENDMISOGYNY.
 
Back
Top