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

help-circle

  • DrM@feddit.detolinuxmemes@lemmy.worldsystemdeez nuts
    link
    fedilink
    arrow-up
    37
    arrow-down
    1
    ·
    2 months ago

    I updated my sources.list to something non-existing at some point and run sudo apt update && sudo apt dist-upgrade -y && sudo apt autoremove once and it also basically uninstalled everything. But that didn’t even matter, I popped in a recovery disk and could reinstall everything. Pretty great to be able to do all that with Linux, fuck everything up in an instant but after a few hours everything is back again






  • 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.





  • DrM@feddit.detoProgrammer Humor@lemmy.mlAverage TS developer
    link
    fedilink
    arrow-up
    11
    ·
    edit-2
    8 months ago

    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.



  • JSON would be perfect if it allowed for comments. But it doesn’t and that alone is enough for me to prefer YAML over JSON. Yes, JSON is understandable without any learning curve, but having a learning curve is not always bad. YAML provides a major benefit that is worth the learning curve and doesn’t have the issues that XML has (which is that there is no way to understand an XML without also having the XSD for it)


  • DrM@feddit.detoProgrammer Humor@lemmy.mlNo rest for the virtuous
    link
    fedilink
    arrow-up
    20
    arrow-down
    1
    ·
    edit-2
    8 months ago

    I don’t really code in my free time, every merge request for a FOSS project I wanted to do so far was for company projects where a feature was missing or buggy. My GitHub and Gitlab accounts are full of outdated forks we needed for a minor change in the FOSS project which I was not allowed to merge upstream



  • Shared hosting sounds like you don’t have your data stored privately and doesn’t sound like less work for the company.

    Don’t look at the name from a technicians perspective, but from the perspective of a manager of a small startup who wants to reduce the overhead for hosting it’s service as much as possible. Also serverless is not wrong per sé, it’s exactly what you as the customer get.

    You could spin it the same way for every other instance. Why do you call GoDaddy “shared hosting”, in the end it’s just a pod on a kubernetes cluster. So why don’t you call it “private kubernetes pod”?