Fuck, Marry, Kill?
@defcon @programmerhumor #devsec #devops #progtamming #coding #typescrup #rust #rustlang #golang @TypeScript @rust @golang
@defcon201 @defcon @programmerhumor @TypeScript @rust @golang
Fuck Go, marry Rust, throw TS to the dogs! 🤣
Hi there! Your text contains links to other Lemmy communities, here are correct links for Lemmy users: !rust@programming.dev, !golang@programming.dev
Fuck Javascript!
Marry Javascript!
Kill Javascript!Bro gets it
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
Fuck TypeScript, Marry Rust, Kill Go.
C C C
Gosh, I love and hate C.
Fuck Rust
Marry Rust
Kill Rust (struggling with borrow checker and lifetimes btw)
Hot take:
Fuck TS, marry Go, kill Rust.So what’s your Go compiler and browser written in?
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.
It’s either C/C++ or Rust, right? And the thing about Cu̎윈
Segmentation fault
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.
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++.
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
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.
@defcon201 @defcon @programmerhumor @TypeScript @rust @golang a 3some with TS and Rust for your beautiful full stack side project, than back home to your cockold GO wife because it’s the only one who can give you a job…
TypeScript is far more widely-used than Go.
Hi there! Your text contains links to other Lemmy communities, here are correct links for Lemmy users: !rust@programming.dev, !golang@programming.dev
Kill typescript, fuck rust, marry go
Ummm, did you like… wait 6 years just to post this?
Fuck go
Marry typescript
Kill rust
@defcon201 @defcon @programmerhumor @TypeScript @rust @golang well, Go just became reproducible …, so …
Fuck rust, marry Go, kill TS 😋Actually, imo Rust and Go have different strengths. Rust is great if the goals are known and you can benefit from a tightly-controlled implementation. Go is nicer for small programs, experiments, programs that don’t benefit from/require tight control.
Hi there! Your text contains links to other Lemmy communities, here are correct links for Lemmy users: !rust@programming.dev, !golang@programming.dev
@defcon201 @defcon @programmerhumor @TypeScript @rust @golang
Fuck TS, marry Rust, kill Go (but only because I have to kill one, never used it)
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.
@NightAuthor 😅 I’d kill JS in a heartbeat, and you wouldn’t even need to ask me. TBH I’d kill any language
But there’s a world of difference with TS, typings and compile-time checks make it a very nice and robust language to work with
Hi there! Your text contains links to other Lemmy communities, here are correct links for Lemmy users: !rust@programming.dev, !golang@programming.dev
fuck ts, marry go, kill rust (no language should have magic returns…and its pretty close to unreadable)
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
