The ratio of consecutive terms of the Fibonacci sequence is approximately the golden ratio phi = ~1.618. This approximation gets more accurate as the sequence advances. One mile is ~1.609km. So technically for large enough numbers of miles, you will be off by about half a percent.
IMO every datetime should be in utc, and variables for datetimes should either be suffixed “Utc” or have a type indicating their time zone (DateTimeOffset or UtcDateTime etc). Conversion to local time happens at the last possible second (e.g. in the view model or an outbound http request parameter). Of course that doesn’t solve the problem of interoperating with other morons programmers who don’t follow these rules, but it keeps things a lot neater locally.
Scheduling based on regional time conventions (holidays, weekends, etc) is just not great though.
It makes a HUGE difference in compile time. Which only matters if you’re building your own kernel anyway. It’s a solution for its own problem.
I think it’s a good learning experience though. There is genuinely a lot of stuff in there that you can easily, safely remove, and reading up on all the less obvious flags is fun.
Swapping CPU manufacturers entirely? I’d just start my kernel config fresh. Pull up the old one next to a new (default ) one and go down line by line. Odds are there are at most a few flags that would need to be changed, but it’s a good chance to reevaluate your previous decisions too.
That has nothing to do with file transfer (“updating”), just long term storage. It’s also a solved problem. You can solve it at the software level with modern self-healing filesystems.
For a long time Firefox Desktop development has supported both Mercurial and Git users. This dual SCM requirement places a significant burden on teams which are already stretched thin in parts. We have made the decision to move Firefox development to Git....
I’m only a native English speaker, so guess I could be interpreting it wrong.
You should try being a native English reader.
What it means is “they will not be accepting pull requests at this time.” Whether or not they are open to changing this in the future is not specified. They have not specifically stated that this is off the table, nor have they stated this is their intent.
You’re quite the lunatic. I’m obviously not defending GitHub PRs, or saying Mozilla should or should not use them. I said “we are not open to PRs at this time” is not the same as “we will be open to PRs in the future.” The truth of that statement has absolutely nothing to do with whether or not Mozilla is, in fact, open to using PRs in the future. But there’s no point in telling you that, because you’re clearly unhinged. Have a good life.
Fair point. I would say on a personal level that GitHub actions is quite nice to use, especially with the marketplace. But I’d be surprised if switching version controls also entailed a CI/CD change for Mozilla, so I can’t think of a good reason.
What are some useful or just cool stuff to memorize?
I just learned the mind palace technique to memorize stuff and wanna put it to use.
You heard me. (mander.xyz)
Welcome to the wonderful world of code obfuscation (imgur.com)
Yes, someone actually did this and I found it running on our server
What happens when Linus dies/retires?
Will we all be fucked or is there a Linus 2?
Mozilla Finally Launches An APT Repository For Easy Firefox Nightly Updating (www.phoronix.com)
on arch btw. (i.imgflip.com)
Floppy disks were high-tech weapons once (files.mastodon.social)
systemd 255-rc1 Brings "Blue Screen of Death" Support and New Tool To Spawn VMs (www.phoronix.com)
Firefox Development Is Moving From Mercurial To Git (groups.google.com)
For a long time Firefox Desktop development has supported both Mercurial and Git users. This dual SCM requirement places a significant burden on teams which are already stretched thin in parts. We have made the decision to move Firefox development to Git....
An unbiased comparison of linux distributions' setup (sh.itjust.works)