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
They've aggressively stated they're a cis woman and has found the implication of her being trans incredibly insulting.
You monster, I prefer denial
I tmux my vim session so I never have to exit it, I just end the session and NOTHING OF NOTE HAPPENS
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
At a quick glance I thought this was some spaceship orbiting around venus!
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
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.
Eh, in my experience that's not how development works. With every new tool to improve efficiency, the result is just more features rather than using your new found time to improve your code base.
It's not just from the publishers and shareholders either. Fixing technicial debt issues is hard, and the solutions often need a lot of time for retrospection. It's far easier to add a crappy new feature ontop and call it a day. It's the lower effort thing to do for everyone, management and the low down programmers alike.
Beyond good and evil.
It's sales were poor but the reviews were great. A fantastic adventure game with a great story and a world that felt so incredibly lived in. It had a bunch of interesting mechanics that focused on stealth rather than confrontation.
Playing it now the scope feels pretty small but it's still a very tight experience.
There is valid performance based reasons to use an app over a browser based experience. Sure perhaps it's just data collection, but being able to cache locally and have that information persistent between uses dramatically drops the initial page load time.
But yeah, it's annoying as hell to be bothered about it, and usually compromising the performance/load time is worth not having to go through the hassle of downloading an app.
Edit: Seems like I was wrong. I remember reading about how in general native apps would make significantly fewer API calls than identical website based experiences, even with the user having navigated to the site before.
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.