• 0 Posts
  • 47 Comments
Joined 1 year ago
cake
Cake day: July 21st, 2023

help-circle

  • Nah, Diablo 4 is much more fun when leveling from 1 to 70 or so. 70 - 100 is just doing the same things over and over with barely any rewards. It’s the other way around there, leveling is fun, endgame is dogshit.

    Usually “game starts at max level” is used for MMOs like WoW. Where all the leveling is seen as annoying bullshit fetch quests and at max level you do dungeons and raids.


  • The story or the gameplay? Because all I wanted to do was play a fun MMO, get items and do dungeons with other people. Instead I did quests like hit 3 rocks with your basic ability. Great! Hit 3 more rocks with the same ability. Done? Now run between 4 NPCs and talk with each of them. Great, now kill 8 enemies over there. Run back, talk with 2 more NPCs. Run through the city and interact with 8 lamp posts, the interaction takes several seconds each, because why not? …

    I really tried to power through this absolute bullshit, but after a few hours I simply gave up. It only got worse, not better.

    As you say Heavensward, I still hear that there is a ton of dumb quests then. Like the story is right at a critical point and they send you off on hours of fetch quests before you can continue?


  • The story or the gameplay? Because all I wanted to do was play a fun MMO, get items and do dungeons with other people. Instead I did quests like hit 3 rocks with your basic ability. Great! Hit 3 more rocks with the same ability. Done? Now run between 4 NPCs and talk with each of them. Great, now kill 8 enemies over there. Run back, talk with 2 more NPCs. Run through the city and interact with 8 lamp posts, the interaction takes several seconds each, because why not? …

    I really tried to power through this absolute bullshit, but after a few hours I simply gave up. It only got worse, not better.


  • Not just for series, this is the same with games.

    “The first 50 hours of Final Fantasy 14 suck, but the expansions afterwards are worth it!”

    “The game starts at max level!”

    I can’t stand it. And it’s not like the game magically gets much better, it just feels pretty okay for someone who just wasted months of their time on the bad parts. Of course you’ll enjoy mediocre parts later on after suffering through that crap.

    A game has to start being fun ten minutes after the tutorial tops. Why play it otherwise?



  • I personally like to keep it on. Most of my messaging is with family and friends and it’s good to know if someone read or hasn’t read my message.

    Especially if things are time critical. Picking someone up? Asking if they need anything from the supermarket? If I see that they read the message I know that they are going to reply in a moment. If they didn’t even read the message I won’t have to wait around / can guess that they are currently in the car or wherever.

    Sometimes you also have a spotty connection, so the received + read receipt can tell you if they actually got your message.

    In general if someone sends me a message and I read it… I’m going to fucking reply to it (if I’m not super busy, and even then I might send a quick message back). I seriously don’t get people who just leave things on read and then forget about it.




  • But the NAS is in your house… which basically means if it gets flooded/burns down all your data is gone too.

    I already have my data on my PC, a second backup inside the same house isn’t worth that much. But instead of relying on a cloud service I just rent a virtual server (for various things) and use Seafile to keep my data in sync.

    PC breaks? House burns down? My data is on my own server in a datacenter. My server gets cancelled? My data is on my PCs.

    So even with your NAS you are 100% reliant on a cloud backup still, so why did you get the NAS when you already have a copy of your data on your devices?








  • Vlyn@lemmy.worldtoPC Master Race@lemmy.worldRate my Component Selection
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    1 year ago

    Where do you find that this CPU “only has 6 3D cores”?

    It’s common knowledge. 7800X3D = 8 3D cores, 7900X3D = 6 3D cores and 6 normal cores (= 12), 7950X3D = 8 3D cores and 8 normal cores (= 16).

    So if you mostly game and don’t need the CPU for productivity tasks you should 100% grab the 7800X3D. If you need a lot of cores then grab the 7950X3D. The 7900X3D is garbage in the middle.


  • Vlyn@lemmy.worldtoPC Master Race@lemmy.worldRate my Component Selection
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    1 year ago

    Someone already pointed out that a 4090 is a massive upgrade over a 4080, no clue what benchmarks you looked at.

    So another suggestion: Why pick a 7900X3D? It’s the worst of both worlds. It only has 6 3D cores for gaming, which might not be enough in the near future (Look up performance benchmarks between a 5600X vs a 5800X for example, there are already games that benefit from more than 6 cores).

    If gaming is a focus: Pick a 7800X3D so you get a full 8 3D cores to work with. If productivity is a focus (with gaming on top) splurge for a 7950X3D. You’re already spending an insane amount of money, you might as well get a decent CPU.

    Besides that: You are wasting a ton of money on the SSDs. Grab a fast one like that for your Windows drive and for gaming, but for storage there’s much cheaper options (that still deliver 3-6 GB/s, if you even need that). 128 GB of RAM is excessive too, except you have a very clear use-case for it.


  • Vlyn@lemmy.worldtoProgrammer Humor@lemmy.mlSounds great in theory
    link
    fedilink
    English
    arrow-up
    174
    arrow-down
    4
    ·
    1 year ago

    TDD is great when you have a very narrow use case, for example an algorithm. Where you already know beforehand: If I throw A in B should come out. If I throw B in C should come out. If I throw Z in an error should be thrown. And so on.

    For that it’s awesome, which is mostly algorithms.

    In real CRUD apps though? You have to write the actual implementation before the tests. Because in the tests you have to mock all the dependencies you used. Come up with fake test data. Mock functions from other classes you aren’t currently testing and so on. You could try TDD for this, but then you probably spend ten times longer writing and re-writing tests :-/

    After a while it boils down to: Small unit tests where they make sense. Then system wide integration tests for complex use-cases.


  • Multi-threading is difficult, you can’t just slap it on everything and call it a day.

    There are languages where it’s easier (Go, Rust, …) but parallelism is an advanced feature. Do it wrong and you get race conditions or dead locks. There is a reason you learn about this later in programming, but you do learn about it (and get to use it).

    When we’re being honest most programmers work on CRUD applications, which are highly sequential, usually waiting on IO and not CPU cycles and so on. Saving 2ms on some operations doesn’t matter if you wait 50ms on the database (and sometimes using more threads is actually slower due to orchestration). If you’re working with highly efficient algorithms or with GPUs then parallelism has a much higher priority. But it always depends on what you’re working with.

    Depending on your tech stack you might not even have the option to properly use parallelism, for example with JavaScript (if you don’t jump through hoops).