• 0 Posts
  • 64 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle












  • if Valve isn’t selling at a loss to poorer regions then they are simply extracting additional profit from higher-income regions on the assumption that those customers can afford it.

    Valve can’t sell for a loss the same way ebay can’t. Valve simply takes a percentage of the price everytime a game is bought, publishers are in complete control of the price they want to sell. Often, publishers will let Steam automatically set regional pricing based e.g. the American price though.

    The way these publishers operate, they will simply set the price at the highest possible value to extract as much as money ad they can from those willing to spend 60+$. Those unwilling or incapable of spending that amount of money, will just buy the game later on a sale. Price skimming has only become more and more prevalent in PC gaming with steam being the “innovator” of frequent sales.


  • Yes I did read it. I was pointing out that all this will do is screw over citizens of poorer EU countries. India vs USA was simply to make it obvious why the concept of geo blocking makes sense. Germans will on average have stronger buying power than someone in Latvia.

    Steam is a storefront, not a competitor to game publisher. It’s effectively no different than Lidl agreeing to run a regional rebate program for Samsung TVs in Latvia for whatever reason.

    The geo blocking enabled cheaper prices for certain countries, not higher. The only people who would have an issue with it is people from richer countries that for some reason are jealous of lower prices in some countries.



  • Valve won’t break the law for other publisher’s profits. Steam is just a store front, they were geo blocking on behalf of other publishers.

    Valve also doesn’t take a cut from steam key sales not bought directly through their storefront, so the geoblocking keys isn’t something that will impact them. More likely, this will result in citizens of poorer EU countries getting screwed over by having to pay higher prices for games, since they can’t stop EU citizens from taking advantage of buying the game from the poorest EU country.





  • I get the point the author is coming from. When I was teaching first year engineering students programming, the one on the left is how everyone would write, it’s simply how human intuitively think about a process.

    However, the one on the right feels more robust to me. For non trivial processes with multiple branches, it can ugly real quick if you haven’t isolated functionalities into smaller functions. The issue is never when you are first writing the function, but when you’re debugging or coming back to make changes.

    What if you’re told the new Italian chef wants to have 15 different toppings, not just 2. He also got 3 new steps that must be done to prepare the dough before you can bake the pizza, and the heat of the oven will now depend on the different dough used. My first instinct if my code was the one on the left, would be to refactor it to make room for the new functionality. With the one on the right, the framework is already set and you can easily add new functions for preparing the dough and make a few changes to addToppings() and bake()

    If I feel too lazy to write “proper” code and just make one big function for a process, I often end up regretting it and refactoring it into smaller, more manageable functions once I get back to the project the next day. It’s simply easier to wrap your head around

    bakePizza() 
    box()```
    than reading the entire function and look for comments to mark each important step. The pizza got burned? Better take a look at `bakePizza()` then.