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.
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
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).
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
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
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)
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.
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.
Yup, super quick to throw a cut together or some basic footage. It won't replace the full adobe suite, but if you want to cut basic videos together it's perfect
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.
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
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).
Hey its better than nothing? Haha
If performance isn't an issue, I'd take it over nothing for long term support
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
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)
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.
The game is absolutley worse with analogue controls.
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.
Yup, super quick to throw a cut together or some basic footage. It won't replace the full adobe suite, but if you want to cut basic videos together it's perfect
Oh how I've missed Alonso defending here haha
Oh my god, Ocon and Gasly that's terrible