• 3 Posts
  • 1.4K Comments
Joined 1 年前
cake
Cake day: 2024年9月21日

help-circle
  • you’re wrong. none of the points in the article say anything at all. the pillars that hold up the lies are

    • ruby is bad because python/js good
    • matz is good but DHH is bad and so ruby is bad
    • Twitter failed 14 years ago because ruby is bad and so ruby is still bad
    • ruby is bad because it’s old
    • ruby bad because it’s not used as much as python/js

    Sheon Han worked at Twitter. doubtful he was there between the 2011-2014 rewrite. I also doubt that he’s done much of anything with ruby since he was fired from Twitter after Musk destroyed it. especially so since he’s taken up freelance writing since 2021.

    Sheon Han is attempting to stay relevant by desperately attacking a language he barely uses and hasn’t touched seriously since at least 2021.

    you’re better off ignoring him and “journalists” like him.








  • I wouldn’t go onto a teen community and spout off how to make explosives even though they’re relatively safe to a trained individual.

    same reason behind not allowing a hobbyist and amateur community to think that iptables and firewalld is the best/only solution.

    it’s dangerous and someone will get hurt eventually.








  • GreenKnight23@lemmy.worldtoSelfhosted@lemmy.worldDocker security
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    2 天前
    • anyone gaining physical or remote access to the device can set rules. by protecting the entire network with a hardware firewall you mitigate attack vectors from other hardware on your network that become compromised.
    • iptables and firewalld are notorious for locking users out of the system by overzealous or green system admins. in the msp world this happens practically by the hour.
    • iptables and firewalld can be used against you in the event of a breach. one of the first things an attacker may attempt is to forward ports and lock system admins out as they take over the system.
    • make sure you save your rules properly or they’ll be gone after a reboot or botched upgrade
    • migrating your rules from one system to another when you’re changing hardware or restoring a system is a huge pain in the ass.
    • got a network change that’s going to modify the subnet your systems are on? get ready to migrate all 15 of your devices one by one for the next 8-15 hours (depending on the complexity of your rules)

    it’s far easier, and safer to have all your network config done in the network. from system migrations to securing/hardening. it’s far more efficient and effective to have a single source of truth that manages network routing and firewall rules. hell, you can even have a redundant or load balanced firewall configuration if you’re afraid of a single point of failure.

    point is, firewalld and iptables is for amateur hour and hobbyists.

    if you want to complain that “docker doesn’t respect system firewalls” then at least have the chutzpah enough to do it the right way from the beginning.



  • it’s hilariously depressing how most people hate on Ruby because of the shit Rails does.

    also, Sheon Han(the author), is a corpo-shilling hack that writes predominantly fluff pieces for his silicon valley friends and neighbors.

    don’t believe what he writes because he only gets paid when his opinions garner traffic.

    want to know why Ruby still has a following? same reason why Java is still holding on. Same reason why COBOL and FORTRAN is still going. because it works and people still use it.