The unicyclist on the left is saying the bicyclist is only riding a bike because they don't have enough skill for a unicycle. The unicyclist on the right is saying they can't learn to ride a bike because they've spent too much of their life riding a unicycle. It's a dig at people who don't want to switch to memory-safe languages like rust.

[–] sukhmel@programming.dev 15 points 15 hours ago (2 children)

It's a dig at people who don't want to switch to memory-safe languages like rust.

Now that's a stretch, it could be anything (no, it couldn't, although I think this may have application to some other pairs of languages)

[–] Ajen@sh.itjust.works 2 points 14 hours ago* (last edited 14 hours ago) (1 children)

I mean, that's just my interpretation. I don't think it's a stretch though, switching to memory safe languages like rust has been pretty big recently.

How did you interpret the comic?

[–] sukhmel@programming.dev 1 points 13 hours ago (1 children)

I should have added a '/s', but I thought it is somewhat obvious, it really reminds of all the 'git gud at C instead of doing Rust'

[–] Ajen@sh.itjust.works 3 points 11 hours ago

Yeah, hard to tell without the /s unfortunately.

[–] CanadaPlus@futurology.today 12 points 13 hours ago* (last edited 13 hours ago) (1 children)

Yeah, Rust is simply the big one right now. It could just as easily apply to people in the 1960's who didn't want to adopt structured programming, or a compiler at all.

[–] ZILtoid1991@lemmy.world 3 points 13 hours ago (1 children)

I personally prefer the memory safety tools offered by D over Rust. D also doesn't come with const by default, and you can even opt out of the RAII stuff a certain graphics driver developer boasted about in the Linux developer mailings (RAII can be a bad for optimization).

[–] CanadaPlus@futurology.today 7 points 13 hours ago (1 children)

I feel like this has come up before, and D is not memory safe. It has some helper-type features, but at the end of the day it is still C-like.

[–] ZILtoid1991@lemmy.world 2 points 11 hours ago

Not if you opt in it. You can even put @safe: in the beginning of your D source code, then you'll have a memory safe D (you have to opt out by using @trusted then @system).

[–] stingpie@lemmy.world -3 points 14 hours ago (2 children)

I am both the left guy and right guy. If you can't program without using a memory safe language, it's a skill issue. But I also don't want to switch to rust because I like the challenge of manual memory management. (Also rust's syntax and semantics looks like it was designed by a monkey attacking a typewriter.)

[–] CanadaPlus@futurology.today 6 points 14 hours ago (1 children)

Please tell me you just code golf or similar, and aren't making things for people to actually use and maintain.

[–] stingpie@lemmy.world 4 points 13 hours ago

No, I don't do anything professionally. I just enjoy challenging myself.

[–] Ajen@sh.itjust.works 8 points 13 hours ago (1 children)

I write C++ professionally. Saying it's a skill issue doesn't solve the problem. If a dev with 15+ years of experience still isn't writing memory-safe C++ (ie. some of the people I work with), they're not going to learn now.

And if you're a project manager and you choose to use C++ because your team says they like the challenge then you should be fired.

Of course none of this applies to hobby projects...

[–] stingpie@lemmy.world 3 points 13 hours ago (1 children)

Yeah, I'm not a model for good programing. I don't program professionally, I just like challenging myself in my hobby projects.

[–] sukhmel@programming.dev 2 points 9 hours ago

I tried to learn assembly for that, but never did after all