no idea

  • 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle
  • kroy@lemmy.worldtoProgrammer Humor@lemmy.mlPHP is dead?
    link
    fedilink
    English
    arrow-up
    3
    ·
    11 months ago

    As someone that used PHP professionally for literal decades, the PHP hate is so meme-y.

    Its biggest problem is that it allows you to do some truly cursed things. The same can be said about other languages, but PHP really doesn’t do much to set you up for success, especially as a new-intermediate coder.

    With opcache, it became fast enough for basically most web backends, and as a language overall it does seem to be evolving and shedding off some of the crap that used to make it truly horrible in the hands of a new person. At least the type-juggling stupiderrors

    Now I mainly use go and python (only because I have to on this one), and I would put Python and PHP on a similar level of “fuck this language” moments






  • Have you been listening???

    In Slovakia, gay adoption AND marriage was on a referendum, and weirdly enough, Francis threw his support because against it. To “preserve the family”

    1. “Let’s think of the nuclear arms, of the possibility to annihilate in a few instants a very high number of human beings. Let’s think also of genetic manipulation, of the manipulation of life, or of the gender theory, that does not recognize the order of creation.”

    So “kill a few million people with nukes” is the same as “gender theory”

    1. “The family is threatened by growing efforts on the part of some to redefine the very institution of marriage, by relativism, by the culture of the ephemeral, by a lack of openness to life.”

    God loves you but you ain’t equal. Homosexuality is a sin, but not a crime. You are welcome in the Church, but you are also immoral and going to hell.

    Sheesh, I was worrying a bit there. At least I’m not violating the laws of man.



  • I notice you didn’t actually respond, just pulled out some classic logical fallacy.

    I’m not absolving the armorer here.

    You don’t like the cars vs guns analogy, fine. I was just making it relatable to righties.

    If you put something in my hands that is capable of killing a person, I’m going to be 100% sure of how not to kill a person with this thing.

    Maybe it’s a firework. The armorer has told me that when I light it, I have exactly 5 seconds to ditch it so I don’t hurt anybody. The armorer is fully culpable here when the firework goes off in 1 second and blows off my hand. I am culpable when I take said firework, and throw it into the unsuspecting crowd. We are both culpable when the firework goes off early AND is tossed into the unsuspecting crowd.


  • … okay, but at what point do you take some personal responsibility??? Blindly saying “it was the armor’s job description” is fantastically silly.

    Dealership sells me the car in working and safe condition, I take said car and drive it into a crowd of people. Dealer is guilty?

    I’m not absolving the armorer at all. She has a PILE of cupability here. But to absolve the actor of all responsibility and fault is ridiciulously misguided.



  • Calling it some right-wing conspiracy is probably where the downvotes are coming from.

    1. Some serious shit was actually occurring
    2. Alec Baldwin was a huge arrogant asshole about it at first, trying to cover his ass as a producer regarding #1
    3. Trump, as Trump does, makes a pretty singular inflammatory comment about it, which points all his brainwashed minions at Baldwin.

    So mostly I think the point is that there is room for both on this.






  • kroy@lemmy.worldtoSelfhosted@lemmy.worldOPNsense virtualization
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    I’m happy to discuss it, as I’ve written articles about it.

    I live high level routing and firewalling in VMs (60 Gbps+), and there are a couple of realities you need to accept, especially when you involved a *BSD in the mix.

    1. *BSD’s networking drivers and, to a lesser degree, the whole stack SUUUCK. This becomes extra poignant when you involve *pf, which is incredible for hand editing, but also horrible for performance because it’s a straight top-to-bottom list.
    2. We could argue about the whole networking stack sucking all day, but in reality, it’s the driver situtation that really brings it down. That’s why “You must buy Intel” is such a mantra on *BSD. Because they are about the only drivers which don’t make for a completely horrible experience. You can meme about how terrible Realtek is, but really it’s only terrible on *BSD. It’s a first-class linux citizen, and often supports better hardware features than the ancient X520, pre-Connect-4, etc people circle-jerk about. And if you often losing out on cool new features/offloads/abilities.
    3. The virtio drivers are usually more efficient and performant than most physical hardware drivers (on *BSD)
    4. You asked “why would anyone ever need to do that?”. It’s simple. High availability. You can run two router/firewall VMs on two different hosts and have zero downtime. Or, if you only want one, you can migrate the VM either manually or automagically, and only suffer the downtime for a reboot as the VM moves to a different host. You can share the same physical NIC between multiple VMs with SR-IOV for maximum low-latency networking, aka storage. It’s a waste throwing 10Gb at just pfSense when it’ll be idle most of the time, and with older hardware pfSense isn’t going to even be able to hit half of that.
    5. Your VM just works if you ever have to move it to another host. Your main routing and firewall VM is now tied to a single specific host. In a disaster recovery situation, this is going to make you hate yourself as you basically end up needing to either physically pull a card and re-setup passthrough, or setup passthrough on a new card, make sure the VM is bound to those MACs. When it’s fully virtualized, it’s hardware agnostic. Your VM may think it’s 10Gb on a single link, but underneath the links are high availability (aka vSphere vDS), on different VLANs, etc. My example here is a few years ago where I swapped in a Z8350 WYSE 3040 when my main router died with 40Gb uplinks. Sure, I was limping for a few days, but as far as my router is concerned, there is no difference.
    6. NUMA becomes an issue. Even single processors have NUMA nodes now, and it wouldn’t be difficult for someone not knowing was a NUMA node is to create a NUMA issue, where you incur huge penalties going from CPU/Chipset to RAM to NIC and back again, depending on where the items are physically arranged in the system. This is doubly poignant in the *BSD world.
    7. If a 1Gb interface is your bottleneck, your network design is broken. There is no reason for most people in a homelab to try and route >1Gbps on your edge. Don’t packet inspect it, and internally you are up to 10Gbps and beyond. Sure, a >1Gbps link might be a reason in 2023, but what’s your 95th percentile, like 25Mbps if you are lucky. It’s only “hawt” for your speedtest numbers, and an occasional download. And you can do 10Gbps pretty easily with virtio on basically any semi-modern system especially with the large files that most people would want 10Gb for, and not dedicate a PCIe slot to it and make it portable.

    I mean, you do you. But I’d much rather to just be able to change the uplink on a vSwitch or bridge to get my router going again instead of having to reboot, passthrough, insert grub cli options, swap cards, etc.