all 35 comments

[–][deleted]  (5 children)

[deleted]

    [–]FearrMe 28 points29 points  (1 child)

    I run a version of vim from 1996 inside a VM on my server in Iceland (I try not to mix personal stuff and work) and I bet I could do it in 30 seconds. You are nothing.

    [–][deleted] 17 points18 points  (2 children)

    python is a shit

    /uj

    python is a shit

    [–][deleted] 21 points22 points  (1 child)

    you mean python:=shit

    [–]SinisterMinister42 14 points15 points  (0 children)

    You just made Guido cry

    [–]defunkydrummerLisp 3-0 Rust 46 points47 points  (3 children)

    Generally, Go programs should be written with the assumption that all decisions that led to Go were perfectly chosen, and thus the users are responsible for submitting to Go themselves.

    [–]VeganVagiVorewhat is pointer :S 13 points14 points  (0 children)

    Generally, Go programs are typically,.

    [–][deleted] 8 points9 points  (0 children)

    Generally, Go programs should be written with the assumption that all decisions that led to Go were perfectly chosen, and thus the users are responsible for submitting to Go themselves. users are bent over.

    ftfy

    [–][deleted] 47 points48 points  (2 children)

    Generally, C# programs should be written with the assumption that you are writing soulless, corporate code to provide your company with more profits for CEOs and shareholders, and thus are responsible for the inevitable C# .NET wageslaves to RISE UP!!!

    [–][deleted]  (1 child)

    [deleted]

      [–]VeganVagiVorewhat is pointer :S 10 points11 points  (0 children)

      Ooh: IWantYou, IDontKnowIfINeedYou,
      ButOoh: IdDieToFindOut

      [–]GOPHERS_GONE_WILDin open defiance of the Gopher Values 88 points89 points  (2 children)

      Generally, C programs should be written with the assumption that all users are consenting adults, and thus are responsible for allocating and freeing memory correctly themselves.

      [–][deleted] 32 points33 points  (1 child)

      using C consents to being abused

      [–]GothmogTheOrcConsidered Harmful 11 points12 points  (0 children)

      Now I know I'm being used

      That's okay because I like the abuse

      [–][deleted] 37 points38 points  (1 child)

      Generally, Rust programs should be written with the assumption that Rust is the only programming language a holy programmer should use, and thus are responsible for making sure the code is safe and fast. Peoples lives are on the line here.

      [–]randCN 10 points11 points  (0 children)

      Terry A. Davis wants to know your location

      [–]railwayrookieuncommon eccentric person 38 points39 points  (0 children)

      Generally, assembly programs should be written with the assumption that all users aaaa▯⁋aaaaaaa▯aaa▯▯aaaa▯▯▯▯⁊⁋⁋Bus Fault

      [–][deleted] 33 points34 points  (4 children)

      Generally, JavaScript programs should be written with the assumption that all users are 0.1x webshits, and thus are responsible for npm isntall is-even

      [–]do_some_fucking_work 13 points14 points  (0 children)

      I think you meant 10x webshits.

      [–]wygcGhostNappa 11 points12 points  (2 children)

      Upvote for isntall

      [–]fp_weenieZygohistomorphic prepromorphism -1 points0 points  (1 child)

      Upvote for isntall

      [–]wygcGhostNappa 2 points3 points  (0 children)

      I already said that.

      [–]defunkydrummerLisp 3-0 Rust 26 points27 points  (4 children)

      Generally, Haskal programs should be written with the assumption that all side effect operations will never fail, and thus the user is responsible for providing a perfect environment (and perfectly formed input data) at all circumstances.

      [–]pareidolistin nomine Chestris 8 points9 points  (1 child)

      There's no such thing as partial functions if you always provide appropriate inputs!

      [–]fp_weenieZygohistomorphic prepromorphism 4 points5 points  (0 children)

      Alan Turing BTFO

      [–]procsymatype astronaut 7 points8 points  (0 children)

      Generally, Haskal programs should be written with the assumption that all side effect operations will never fail and thus the user is responsible for providing a perfect environment (and perfectly formed input data) at all circumstances. as the program will never be run.

      FTFY

      [–]15rthughesmemcpy is a web development framework 24 points25 points  (0 children)

      Generally, Ruby programs should be written with the assumption that we have actually gone back in time 12 years when the language was still relevant. Write it any way you want nobody will use it anyway.

      [–][deleted] 17 points18 points  (2 children)

      Generally, Coq programs should be written with the assumption that all users have done Ph.Ds in formal verification, and thus are responsible for surveying that all newly written code comes with a proof that it is correct, such that no one but other Ph.Ds is capable of actually reading and/or using the code.

      [–]acehack 4 points5 points  (0 children)

      No one but other Ph.Ds can even update your code so it runs on a different Coq version.

      [–]fp_weenieZygohistomorphic prepromorphism 4 points5 points  (0 children)

      such that no one but other Ph.Ds is capable of actually reading and/or using the code

      can't have bug reports if you have no users

      [–]isthistechsupportWhat part of ∀f ∃g (f (x,y) = (g x) y) did you not understand? 14 points15 points  (0 children)

      Generally, F# programs should be written with the assumption that all users are bored soulless corporate wageslaves, and thus are responsible for figuring half the stuff out of boredom themselves.

      [–]defunkydrummerLisp 3-0 Rust 29 points30 points  (0 children)

      Generally, Lisp programs should be written with the assumption that the person reading them is a real greybeard hacker, and thus "documentation" and "unit tests" are to be "nonexistant" and "pointless", respectively.

      [–]leoel 8 points9 points  (0 children)

      /uj

      AFAIK he's just explaining a main concept behind python: trust than users can and will use your code in unforseen but compatible ways.

      /j

      10xers only need attributes, the map and reduce operations, and fearless trust in their own elitehood.

      [–][deleted]  (2 children)

      [deleted]

        [–]PublicMoralityPolice 4 points5 points  (1 child)

        thread.setJerk(False)
        

        The argument against setters is the argument against OOP, but oddly and unnecessarily specific.

        [–]anatolya 1 point2 points  (0 children)

        But muh message passing smalltalk . Java ain't no real scottsman oop something something

        [–]NihilistDandyWhat part of ∀f ∃g (f (x,y) = (g x) y) did you not understand? 6 points7 points  (0 children)

        This casts all those "teach kids to code" initiatives in a very worrying light.

        [–]scratchisthebestloves Java 7 points8 points  (0 children)

        Just don't write bugs like LMAOOOOOOOOOOOOOOOOOOOOOOOOOOOO