You could also improve the current NixOS setup, that would make creating a new instance a lot easier!
In Java you get a bunch of unexpected NullPointerExceptions instead…
They certainly do like to use the word “in” a lot.
What kovarex controversy? Link? Context?
The real joke here is that after causing millions of pointless refactorings and rewrites, now finally the source book is affected as well.
Not even a positron?
At least in Europe the year after the copyright statement has no meaning, and even the copyright statement itself is useless. Since if not stated otherwise, no rights are granted by default.
Let’s assume the reflection is coming from just one flat glass pane.
Trump is too unironically placed next to two important persons from US history here. Ethically questionable.
This is outdated information. Nowadays, you can use let <pattern> = <expression> else <block>
. This is called a let-else statement.
The pattern does not need to be irrefutable, as if it does not match, the else
block is executed. But the block must diverge, i.e. contain a return
, continue
or break
statement to avoid any code in which bindings made in the let
statement would be valid.
The maintainer is a human that needs to eat every day, and not just whenever their services are needed. So at least, the sum of money would need to be a few times higher than whatever labour the fix takes.
But then, the maintainer’s ability to fix these bugs doesn’t come from nowhere. They worked on this project for likely a long time, which would also need to be taken into account when agreeing on a sum.
Further, this would be business to business. And those contracts often include the value that the client gets out of the software. So if Microsoft makes billions from this open source library, then the maintainer’s - as a business - should receive a payment that reflects this for the fix.
All that implies that a few thousand is not nearly enough. Maybe 100k and the maintainer would budge.
The tweet is from today. The ffmpeg team felt like it needed to be said.
Such a great piece of art displaying one of the many issues with stack overflow.
Linux kernel guilty as well. It reports memory in “kb”, but digging through documentation, you will at some point see that they actually mean KiB. The “kb” would be 1000 bits.
They’ll probably cancel that feature well ahead of your death.
That title took me a minute to parse
I think you already used a pretty nice way, which is using shadowing. If one variable is only used for the creation of another, simply shadowing it keeps your namespace clean.
Sometimes it doesn’t make sense to give the shadowed variable the same name, because that name doesn’t describe its content very well. But in this case it seems like that is not a concern.