no it’s the joke. In o-notation you always use the highest approximation, so o(n!²) does not exist, it’s only o(n!)

Otherwise there would never be o(1) or o(n), because o(1) would imply that the algorithm only has a single line of instructions, same for o(n)

I just googled “BASF T-Shirt” and immediately found the one he is wearing in this video (and he wear it in a couple of other videos recently)

Just using fluentd to push the files into an ElasticSearch DB and using Kibana as frontend is one day of work for a kubernetes admin and it works good enough (and way better than grepping logfiles from every of the 3000 pods running in a big cluster)

And if something breaks they put the burden on you for not creating backups. Always keep it in writing that you are supposed to work on something else, otherwise you will get the problem down the line

Yeah, I bought it for 10ct

No. For 4K Netflix the browser needs to talk to a specific, locked down, part of your Intel (!) CPU. This only works on Edge in Windows or Safari on MacOS (it also works with the Store apps). It never works on Linux and it does not work on Chrome or Firefox.

That’s only because you use a Mac, on Windows only Edge allows 4k Netflix. It’s the integrated browsers that have the HDCP hardware features so it allows 4K

It also is very unstable when using multiple profiles. The profiles update individually, so very often you start a second profile and it updates firefox, which makes the first profile not work anymore. You don’t really notice that though, it just stops loading any websites.

Also on mobile it stops streams running in the background after some time, so when listening to something via firefox you have to actively use FF while listening, can’t leave the phone turned to standby

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

The adapter is still the inconvenience for me, just because the other option is a (tiny) inconvenience for you doesn’t change the fact that the adapter is an inconvenience for me.

The adapter IS the inconvenience.

Of course the amount of insects drastically reduced, but for the windscreen there is another thing to take into account: Cars today are extremely aerodynamic. Even new Jeeps and the F150s are aerodynamic. Because of this, the insects are pushed away from your windscreen instead of against it, which is one of the main reasons why your windscreen isn’t full of insects anymore.

The only real exception to this is the Mercedes G-Class, but I doubt that a lot of us will ever sit in one

Edit: apparently I’m wrong: https://feddit.de/comment/8318194

PgUp and PgDn are also extremely useful when scrolling through logs

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.

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:

@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

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