• 9 Posts
  • 47 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle








  • Sony is also encountering similar issues in terms of the cost of games being unsustainable and Moore’s Law kicking in. The difference is that they’re making games that move consoles and Microsoft just aren’t.

    At this point, I don’t know what strategy Microsoft has at this point. If you say “Xbox everywhere”, what does Xbox even mean any more for the enthusiast? I don’t think Xbox is done, but if they were looking to be HBO before, they are now going for the Netflix approach - high quantity content, mediocre product - and possibly alienate the existing audience they have.

    I say this as an Xbox Series S owner, I’m happy with my purchase, but as a consumer I don’t think I’ll be upgrading my console to anything Microsoft ship any time soon.




  • I can imagine them carrying on making consoles this generation but long-term Microsoft is a services company and over successive generations they have failed to recapture the lead from Sony since the 360. Ultimately, they just want to make more money and struggling in the hardware business is not an exciting place for them to be in.

    I say this as a Series S owner: the writing is on the wall. I will likely not be purchasing another Microsoft console after this, though I’m not sure they’d be interested in releasing one. I want to buy and own games I can play locally on a piece of hardware, which probably means I have to return to Sony or go back to the humble PC. For anyone currently on the fence seeing this news, I don’t know why they’d consider buying into the Xbox platform and tying in all their gaming purchases.








  • To be honest, it doesn’t seem that bad. With clean architecture, you are going to end up with extra types and mappers. I would argue that what you have isn’t coupled, because a change in one place doesn’t have unexpected side effects elsewhere.

    I haven’t used Goa or Gorm. Writing SQL by hand gets old quick so I get why you’d use Gorm - just less code to write in the end. I’ve used sqlc as it’s more a library than a framework, and it’s fine, but it can’t fulfill every use case. Goa looks too opinionated for me, on the face of it.

    I’ve used wire. It takes some understanding but it’s definitely a lot to understand just to add a dependency. At work we’ve got our own template for doing dependency injection and although I was skeptical at first it strikes a really good balance between being understandable and abstracting away DI. If this is your pain point, I’d consider going back to basics and get rid of the framework.

    If you decide to go with a framework like Laravel, Rails or Next.js and build everything around the framework, you will deliver quickly at first, but you won’t have type safety and it particular point it will stop scaling because these frameworks have no consideration for clean architecture. You won’t necessarily be better off.