DrM @ DrM @feddit.de

Posts

2

Comments

119

Joined

2 yr. ago

At least all countries I've been to have blinds on the outside. Germany and Netherlands have rolling shutters like these: https://www.rollorieper.de/images/rollladen/overview_rollladen_mobile.webp

Southern and Eastern european countries tend to have little doors on the outside like these: https://www.schneider-schoenwalde.de/fileadmin/\_processed\_/3/8/csm_moosgruene-fensterlaeden_d2513c37b0.webp which are made of wood or plastic

I have never been to poland, scandinavia or the baltics, but all countries I've been to have one way or another to completely block light and don't let cats scratch the curtains

European blinds solve this as well, they are made of plastic and are on the outside of the window, not inside

PgUp and PgDn are also extremely useful when scrolling through logs

I try to tell myself that I can't do anything about it to calm down, then I find a solution and I can do something about it

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.

Sadly not available for Ff on Android, hopefully that changes soon

GTA V was 2 years later and it even came out after the next-gen release. But I waited patiently, I skipped any spoilers for 2 years and it was well worth it. Also, GTA has such a long lifespan that the wait really doesn't matter

Did you by any change get inspired by Marius Hornberger? :)

https://www.youtube.com/watch?v=7V0NvNZmvXU

He did something very similar, your's looks a bit better with the lighting

It lost a lot of the super-good touchscreen PDF functionality when it switched to chromium though, which I am still mad about. I hope at one point MS will return the PDF Viewer from the original edge

I don't think that this would work, there are no types anymore during runtime because everything is translated into plain js on build. TypeScript only exists during development

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:

 TypeScript

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

I hate Typescript for promising me that nobody can put cyanide on the list, but in reality it disallows ME from putting cyanide on the list, but everyone else from the outside is still allowed to do so by using the API which is plain JavaScript again

Why would they keep it on? Sure, they will continue to collect data for their AI, but I'm pretty sure they are happy that they don't want to keep it on if it might drive you to use other search engines. And turn it back on after a few versions of optimization

Was the same for me this vacation. Gladly we were on a smaller mountain which was completely surrounded by villages, so we knew that just going down the mountain would lead to a bus that could bring us to the hotel, so we didnt care that much.

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)

No sarcasm, I never got an E-Mail before from a Headhunter, only LinkedIn Messages. Not gonna lie, I hated it.

That's why today I got an email from a headhunter that used Data from my LinkedIn profile. Fuck this.

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

FOSS user:

Wants to improve the software and sees easy fixes, but isn't allowed to create a Merge Request because company policy disallows you from writing code for other projects on company time