• 14 Posts
  • 1.65K Comments
Joined 3 years ago
Aquileo | cake
Cake day: July 1st, 2023

Aquileo | help-circle











  • I mean, screw performance. You can get away with a lot of shitty performance and still have a completely functional application. However, the kind of slop that happens around module boundaries that turns your codebase into a giant pile of workarounds and hacks really sucks.

    And AI is particularly bad at this, as AI almost always prefers to work around a problem or do everything it can to meet the plan the user approved, even if that plan meets reality, it has problems. Which tends to lead to cascading misalignment with intentions and cascading infrastructure and architectural technical debt.

    All of which culminate in less stable software, lower likelihood of long-term support of that software, and worse performance.




  • douglasg14b@lemmy.worldtomemes@lemmy.worldHe was very mature about this
    Aquileo | link
    Aquileo | fedilink
    Aquileo | arrow-up
    7
    Aquileo | arrow-down
    18
    ·
    Aquileo | edit-2
    13 days ago

    It’s not a reasonable response at all. It’s unhealthy AF.

    If the partner is prioritizing games over their relationship or responsibilities, and is making the other feel like they have to compete for attention and time with their partners habits or addiction. The affected partner hss every right to desire to leave that relationship because their needs are not being met in that relationship.

    This is what the ultimatum is targeting. His response being intentionally obtuse and flipping it back around to the partner whose needs are likely not being met in their relationship being the problem is extremely toxic and manipulative.


  • TIL!

    Awkwardly, I find that the largest memory pressure tends to come from a particular web page that continually gobbles up more memory the longer it is open.

    There’s always one of these somewhere, and I’m bad at closing tabs. I usually notice pretty quickly when I come back to my computer. As soon as we start hitting page filing, since everything is stuttering and slow, but if it goes overnight, it can literally be 15 to 20 minutes before the system is responsive again after I kill the offending process.

    Whereas on my work device, which is Windows, I usually might not even notice until I’ve maxed out my page file, which can be 64 or 128 GB depending on the device. And even then, I only notice because file operations start getting slow because the SSD is being thrashed. Killing the offending process results in responsiveness usually within a few seconds and a full clear out of the page file in a couple minutes.

    The explanations that I’ve gotten from another commenter make a lot of sense. That Windows has just always had to deal with high memory pressures, so has been forced to mature in that sense. It is rather odd that Linux is behind on this, though, given its overwhelming representation in headless environments