• 0 Posts
  • 72 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle












  • This has nothing directly to do with The Day Before, but: Backing a Kickstarter is something completely different and that has to come into peoples heads. Preorders are for a mostly finished product that will 100% ship. The devs have enough funding from investors and publishers, the game will be released no matter how little preorders they will get. Crowdfunding however is for an idea in its infancy that might never be finished. Crowdfunding is an investment.

    But where is the difference in this case, The Day Before? Well, easy: When you invest in a kickstarter, the company has to use the money you invested to actually develop the game. They can’t buy fancy cars with the money, they need to put it to good use. If the company uses the money for their own personal benefit, they can be sued for that. For preorders thats not the case.


  • I couldn’t disagree more with you.

    1. There was no preorder
    2. This was a Kickstarter Project where a lot of people backed
    3. For years the devs didn’t give a lot of information to the backers
    4. There was a class action lawsuit for scamming against the developers because they just took the money and didn’t do anything with it
    5. Now they published something so they can say “here we did something with all of the money” yet it’s obvious that what they developed did not take years.

    It’s pretty obvious that they only published the game in the current state because of the lawsuit. The game is a total scam and they deserve the hate from the people that invested a lot of money when backing. Backing on Kickstarter has something to do with trust. Of course, the project may never be finished and that’s okay. But it’s obvious here, that they just took the money and did not use it for the game.




  • The main problem with JavaScript and TypeScript is that there is such a little entrybarrier to it, that way too many people use it without understanding it. The amount of times that we had major issues in production because someone doesn’t understand TypeScript is not countable anymore and our project went live only 4 months ago.

    For example, when you use nest.js and want to use a boolean value as a query parameter.

    As an example:

    @Get('valueOfMyBoolean')
    @ApiQuery(
      {
        name: 'myBoolean',
        type: boolean,
      }
    )
    myBooleanFunction(
      @Query('myBoolean') myBoolean: boolean
    ){
      if(myBoolean){
        return 'myBoolean is true';
      }
      return 'myBoolean is false';
    }
    

    You see this code. You don’t see anything wrong with it. The architect looks at it in code review and doesn’t see anything wrong with it. But then you do a GET https://something.com/valueOfMyBoolean?myBoolean=false and you get “myBoolean is true” and if you do typeOf(myBoolean) you will see that, despite you declaring it twice, myBoolean is not a boolean but a string. But when running the unit-tests, myBoolean is a boolean.