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
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
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
I don’t think it’s because you grew up poor. It’s because why would you buy coffee everyday?
I buy coffee almost everytime I’m at an airport or a train station, but that’s like… once every two months? If I would commute by train, I wouldn’t buy coffee everytime I’m at the train station, I would just wait until I’m in the office to grab a cup.
But I did buy a coffee daily, when I was in university. There was no way to get a coffee besides buying one, so I bought one. So I think thats the main thing about buying daily, necessity. Some companies only have paid machines, so you buy a coffee daily when at work. In school or university you don’t have a coffee machine available, so you buy one daily.
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
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
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
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)