all 30 comments

sorted by: hot top controversial new old
[–] 38 points 2 years ago* (last edited 2 years ago) (1 child)
  • [–] 37 points 2 years ago (1 child)

    Fuck Javascript!
    Marry Javascript!
    Kill Javascript!

  • source
  • hideshow 2 child comments
  • [–] 16 points 2 years ago

    CommunityLinkFixer bot is gonna have a field trip on this one 😭🤣

    I'm not familiar with Go or Rust but...

    K Go (made by Google), F TypeScript, M Rust

  • source
  • [–] 8 points 2 years ago

    C C C

    Gosh, I love and hate C.

  • source
  • [–] 8 points 2 years ago

    Fuck Rust

    Marry Rust

    Kill Rust (struggling with borrow checker and lifetimes btw)

  • source
  • [–] 8 points 2 years ago

    Fuck TypeScript, Marry Rust, Kill Go.

  • source
  • [–] 7 points 2 years ago (1 child)

    Hot take:
    Fuck TS, marry Go, kill Rust.

  • source
  • hideshow 2 child comments
  • [–] 1 point 2 years ago (1 child)

    So what's your Go compiler and browser written in?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago (1 child)

    I was under the impression that the Go compiler was written in C/C++, though don't quote me on this one. My browser however is Firefox, so touché on that one.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago* (1 child)

    It's either C/C++ or Rust, right? And the thing about Cu̎윈

    Segmentation fault

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago (1 child)

    There's plenty of applications that aren't critical enough to require precise memory management and where a GC is a worthy tradeoff for the simplicity that Go brings to the table, but sure, if you are interested in going super low level that's what you are left to work with.

    And it's probably fine. If I had to pick between C++ and Rust I would choose the latter any day of the week but thankfully not every developer has to go that low.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago (1 child)

    Oh yeah, don't get me wrong higher-level languages have a place. C and I assume Rust are no good if you just want to hack a simple thing together. Low-level languages are bad is indeed a hot take, though, and I've fully bought into the Rust hype, at least vs. C/C++.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago

    Nah I didn't say that it's bad lol. Didn't mean it that way, at least. The way I understand the "fuck, marry, kill" game is that:

    • Fuck: down to play with it every once in a while
    • Marry: always down to use it
    • Kill: never want to use it

    but if someone else wants to play with Rust who am I to stop them

  • source
  • parent
  • [+] 4 points 2 years ago* (2 children)
  • [–] 4 points 2 years ago

    Kill TypeScript, then stomp on its dead body, burn it to ashes, put it in a lead container and send it to the bottom of the Mariana Trench.

    Fuck or Marry either of the other two.

  • source
  • [–] 3 points 2 years ago

    Ummm, did you like... wait 6 years just to post this?

  • source
  • [–] 3 points 2 years ago

    Fuck go

    Marry typescript

    Kill rust

  • source
  • [–] 2 points 2 years ago

    Kill typescript, fuck rust, marry go

  • source
  • [+] 2 points 2 years ago* (last edited 2 years ago) (1 child)
  • [–] 1 point 2 years ago (2 children)

    @defcon201 @defcon @programmerhumor @TypeScript @rust @golang

    Fuck TS, marry Rust, kill Go (but only because I have to kill one, never used it)

  • source
  • hideshow 4 child comments
  • [–] 1 point 2 years ago (1 child)

    So you’ve used TS and wouldn’t opt to kill it?!

    Tbh I’ve only used JS and don’t know how different JS and TS are outside the typing.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 2 years ago (1 child)

    fuck ts, marry go, kill rust (no language should have magic returns...and its pretty close to unreadable)

  • source
  • hideshow 2 child comments
  • [–] 3 points 2 years ago* (last edited 2 years ago)

    I wish implicit returns could be turned into an error in the configs of a project. It was impopular at the time and probably still is outside of Rust, it permeated through every control structure because of how the language is designed, but the worst part is how unnecessary it was

    It would've cost nothing not to do it

    It would've made no one upset

    Now Rust is the only language to do what it does - and it has this shit in it

  • source
  • parent