DWin

joined 1 year ago
[–] DWin 9 points 10 months ago (1 children)

I think some people are upset that the voices aren't 100% true to Justin, and maybe some anti-cancel culture typed as well.

There are some weak episodes, and they are REALLY weak, but I think it also has some of the strongest of the entire series. I'd say it's worth a watch.

[–] DWin 6 points 11 months ago* (last edited 11 months ago)

Personally that's the dream game for me. I haven't got time for hundreds of mid-tier grinding hours. Give me something with emotional impact and an absorbing world that lasts at most 10 hours.

If I want just gameplay I'll just play one of numerous ranked games to get that fix

[–] DWin 10 points 1 year ago (4 children)

They've aggressively stated they're a cis woman and has found the implication of her being trans incredibly insulting.

[–] DWin 3 points 1 year ago

You monster, I prefer denial

[–] DWin 33 points 1 year ago (11 children)

I tmux my vim session so I never have to exit it, I just end the session and NOTHING OF NOTE HAPPENS

[–] DWin 0 points 1 year ago

Yeah I completely agree with you, but sometimes there are other things that jankier languages allow you to do. Say in python, you can do direct property assignment. This is gonna be annoying for someone later to figure out why their object has suddely changed, and without getters and setters, you'll have a harder time picking apart what's going on. The benefit though is that it's very quick to just tack on a property onto some global object and then have that read elsewhere down the road.

It sucks, and you will curse yourself later, like you don't even know what type it is, or maybe it's just null, however it did allow you to ship a project. Maybe that bodge solution is indicative of needing a complete overhaul on how you structure your project, but until you get to that point where you've scoped out what the final idea looks like, it might not be time for static typing and good code design.

I also think that static typing and such makes you move a lot slower when making changes. I love rust to bits, but maintaining an old project is like wading through treacle. I only jump towards using it now once I've got a really great understanding of all the needs of the system, and have the time to really think about the problem in its entirety. Maybe you suddenly need a mutable self in somewhere that you didn't before, perhaps that means going and refactoring a whole load of traits that were designed without mutability (for good reason).

[–] DWin 1 points 1 year ago (3 children)

Hey its better than nothing? Haha

If performance isn't an issue, I'd take it over nothing for long term support

[–] DWin 3 points 1 year ago (7 children)

Time to delivery is important. Moving quickly withing a language and frameworks that prioritise speed over safety gets a product out the door is important when testing whether a business idea holds merit. Once you're established with a better scope of the project you should be rewriting this in a static language.

Dynamically typed interpreted languages should never be used for long term support imo

[–] DWin 5 points 1 year ago

At a quick glance I thought this was some spaceship orbiting around venus!

[–] DWin 9 points 1 year ago

From what I saw, there was one developer spouting some abhorant things, talking about how all Israeli citizens were targets at this point. I haven't seen anything else about other developers sharing these views though so I'm considering it an isolated nutter until we see more

[–] DWin 1 points 1 year ago (1 children)

You don't have to use the platform. Competition is good, and steam taking 30% is massive. I'm a huge fan of steam but the fears of what happens post-gabe should have us all wanting other companies to put pressure on them. Hopefully it'll drive them to promise continued pro-consumer practices such as proton (let's gloss over DRM)

[–] DWin 2 points 1 year ago* (last edited 1 year ago) (1 children)

It feels like maybe this could be a code structure issue, but within your example what about something like this?

fn main(){
    let mut counter = 0;
    let output_array = array.into_iter()
        .map(|single_item| {
            // breaks the map if the array when trying to access an item past 5
            if single_item > 5 {
                break;
            }
        })
        .collect()
        .map(|single_item| {
            // increment a variable outside of this scope that's mutable that can be changed by the previous run
            counter += 1;
            single_item.function(counter);
        })
        .collect();
}

Does that kinda syntax work for your workflow? Maybe it'll require you to either pollute a single map (or similar) with a bunch of checks that you can use to trigger a break though.

Most of the time I've been able to find ways to re-write them in this syntax, but I also think that rusts borrowing system although fantastic for confidence in your code makes refactoring an absolute nightmare so often it's too much of a hassle to rewrite my code with a better syntax.

view more: next ›