• 1 Post
  • 99 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle

  • My Odyssey G7’s panel also fell off 2 weeks before the end of the warranty.

    In addition to that, the Odyssey series also has a weird issue where if certain conditions are met, the entire screen will dip in brightness and display horizontal lines. It’s very distracting. They’re aware of the issue (as many people have reported it) but they aren’t doing anything to fix it. I won’t be buying another.



  • It’s been 4 years since I built my last one, but I still think it holds true.

    I’ve heard Intel chips still run hot, especially the 14th Gen i9. However, I came across this article by Puget Systems (a system integrator who mainly deals with professional workstations rather than gaming rigs) who found that decreasing the PL1, which I assume means Power Level, from 253W to 125W was a good enough tradeoff for performance/heat that it’s the default configuration they ship to their customers.

    On the other hand, they still do mention that tasks such as UE light baking, V-Ray, Cinebench, and Blender saw gains of 10-18% when using the higher power limit, which seems much more like what OP’s workload is. Puget then proceed to recommend a CPU with a higher core count like a Threadripper PRO for those kinds of workloads, so perhaps OP really would be better off going AMD for their workstation.












  • Pyro@lemmy.worldtoProgrammer Humor@lemmy.mlHappened to me multiple times
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    4
    ·
    9 months ago

    I want to like Forgejo but the name is really terrible.

    Is it “forj-joe”? Nah, that double-J sound is way too awkward.
    Do you then merge the J sounds to make “forjo”? If so, why not just call it that?
    Is it maybe “for-geh-joe”? That seems the most likely to me, but then that ignores the “build < forge” marketing on their website.

    I know it’s pretty inconsequential, but it feels weird using a tool that you don’t even know how to pronounce the name of.





  • I would say finding that the bug is in a library is worse than finding it in your own code.

    If it’s your own code, you just fix it.

    If it’s in a library you then have to go and search for issues. If there isn’t one, you then go and spend time making one and potentially preparing a minimum reproducible example. Or if you don’t do that (or it’s just unmaintained) then you have to consider downgrading to a version that doesn’t have the bug and potentially losing functionality, or even switching to another library entirely and consequently rewriting all your code that used the old one to work with the new one.

    Yeah, I’d take my own bugs over library bugs any day.