this post was submitted on 17 May 2024
57 points (100.0% liked)

Cybersecurity

5677 readers
133 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Community Rules

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !cybersecurity@lemmy.capebreton.social !securitynews@infosec.pub !netsec@links.hackliberty.org !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] MajorHavoc@programming.dev 9 points 6 months ago (1 children)

Yay! I have a better reason to hate submodules now, until it's patched everywhere, at least.

[–] Altreus@sh.itjust.works 6 points 6 months ago* (last edited 6 months ago) (1 children)

Nice, came here to dunk on submodules, and find there's no need.

[–] MajorHavoc@programming.dev 2 points 6 months ago* (last edited 5 months ago) (1 children)

Yeah. I wanted to like submodules, but submodules, to me, ended up feeling like one feature too many in git.

I mainly run into submodules that have been setup accidentally by cloning inside an existing clone. That situation is, of course, not great.

Even for the many reasonable use cases for submodules, I generally end up letting my actual package manager do the work, instead. I'm generally happier for it, since life tends to be simpler when my package manager of choice knows about any required libraries.

[–] Altreus@sh.itjust.works 3 points 5 months ago

Agreed. Haven't yet found a use case that isn't better handled by either build tools or "don't do that"