• 0 Posts
  • 97 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle

  • It will be questioned, but you have a good explanation. The tricky part is explaining it elegantly. Hiring managers kinda glance at resumes so you should add a sentence at the end explaining that you were let off due to internal company reasons. You should also try and get a letter from the company explaining that it wasn’t for performance reasons. Even better would be to get letters of recommendation from your coworkers and manager. Hopefully they’ll be extra nice to you due to your situation, but you need to be proactive about it.





  • My opinion is you should use it when it’s useful, but not when it’s unnecessary. Their main use case is when you need to couple the functionality of functions to a shared state, and it’s particularly useful when you have multiple interdependent functions that need to be tied to multiple codependent states.

    I find it relatively rare when I really need to use a class. Between first class functions and closures and modules and other features, I find JavaScript has a lot of tools to avoid needing classes. Classes add complexity so I only use them when the complexity they add is less than the complexity of the task they’re needed for.




  • Another thing to consider is that developers consciously make design choices to adapt to the hardware available at the time, and these are not things you can just turn on and off with settings. For example maybe there’s a zone transition that slows the game down on older hardware and in the past they would have added a subtle loading area like a tunnel but that’s not needed anymore for their current target hardware. Should they completely change the game to be a bit smoother on 5+ year old hardware? You can get a ton of compatibility with changing settings, but to get the same level of optimization as games made at the time the old hardware was the target hardware would oftentimes mean significantly changing the game itself.


  • fidodo@lemm.eetoPC Master Race@lemmy.worldHow low should graphics settings go?
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    1 year ago

    I’m a little confused by your timeline. I agree, 5 year old hardware should definitely support 1080p60, but the 1070 is 7 years old now. Since the 1070 could support that when it came out and those are static targets I think we should expect the 1070 to support 1080p60 forever for games similar to games that were coming out at the time, but it’s a bit unfair to compare starfield to portal 2 and cs:go when those games are in constrained and controlled environments while starfield is vast and open, and environments definitely take a GPU toll, so you will lose some performance to that compared to those games. I haven’t played starfield yet so I don’t know the details, but given the scope I know of it, it doesn’t sound unreasonable for it to miss the 1080p60 mark a bit given the difference in game environment.









  • After experiencing ad hoc inline scripts, frameworkless jQuery spaghetti code, inflexible monoliths like angular, and overly simplistic micro frameworks like backbone, I’m super happy with where we’re at with react and react like frameworks. I really do feel like we’ve hit the sweet spot between power, simplicity, flexibility, and ease of use which is why I’m confident that things aren’t going to be as volatile as the past. React is already 10 years old now and still going strong with no new trends looking to usurp it. I think those old trends were necessary experiments to get to where we are now, and I think the old meme of web dev changing every week is no longer true.


  • I’ve had a good time with react SSR and SSG particularly when using next.js which does a great job optimizing out of the box, but really SSR and SSG are functionally just glorified string interpolators so anything will do. What matters is ease of use and with the strong community and toolset available to react I’ve had no trouble setting up react for SSR/SSG.

    Where things still need improvement is with hybrid apps that take SSR/SSG pages and hydrate them to be ready for the client to take over, but that’s always been a pain point, and while we’re still not where we need to be I do think it’s better than it’s ever been and we’re on the right track to cracking it.

    Maybe it’s because I’ve seen how bad things can get that I’m appreciative of what we have. After experiencing frameworkless jQuery spaghetti code, overly complicated monoliths like angular, and overly simplified micro frameworks like backbone, I’m really happy with the frameworks and toolsets we have now, and react’s ecosystem is very mature.

    I would say that react is overkill for SSR, but pure SSR is pretty simple so react is also able to handle it just fine and elegantly as react is even easier to use when you’re not dealing with dynamic state, and if you find the need to introduce some hybrid client side functionally, which pretty much always happens eventually, it’s a good thing to be on react.