Because half of the US is geologically dead.
2,638 karma · joined July 12, 2010
I write about cryptography but not from any knowledgable position.
Retired.
You could run your house for weeks off a 100kWh traction battery with V2G.
Airpods Pro are isolating, Airpods are not.
It happens due to failed estimates (we thought we could start production in January but we couldn't figure out the process until March), upstream supply failures (our surface-mount supplier can't get us enough capacitors), or global market conditions (concrete and steel unexpectedly doubled in price and we can't afford to build the whole building this year).
It happens all the time and isn't your fault (but it is your responsibility to handle).
With that said anything M1 or newer is going to be a delightful upgrade for you. An enormous jump in performance, battery life, and thermal performance.
In the same way that PowerPC and m68k hardware still works, sure. Apple silicon is so performant that (much like those previous two hardware jumps) it's not worth maintaining support for the old arch at this point.
macOS supports case-insensitivity[0] and performs unicode normalization[1] on filenames, and decomposes name data to an extent that the question "what does the fs see" is a bit moot.
With that said, the internal storage of filenames in APFS are a nul-terminated UTF-8 string[2], with (i'm pretty sure) colons as colons, which the Finder displays as slashes.
[0] if you make a file named "Makefile" then touch a file named "makefile", it'll touch the first file, instead of making a second file.
[1] if you make a file named "schön" (s-c-h-combining¨-o-n) and then search for (s-c-h-ö-n), you can find it, or vice versa. The particular normalization/canonicalization used is NFD.
[2] j_drec_key_t description in https://developer.apple.com/support/downloads/Apple-File-Sys...
The slide says something like "run the command `seq 2 10000000 | less` and check `ps`, notice that `seq` isn't running". But that isn't how the processes will behave, `seq` will continue running (albeit blocked) until `less` is dead or closes the pipe.
This explanation isn't correct, since a running `less` would not close the pipe and is still a reader. Writes to the pipe would block until `less` fully consumed it, or until `less` was quit such as with the `q` command.
The text _is_ correct if you add a missing step to `q`uit out of the `less` program. I think this step must have been dropped along the way. Unfortunately the screen capture doesn't show this step either.
The author is on holiday (and enjoying their birthday!) and will get to it when they're back home.
[1] https://web.archive.org/web/20140309183752/http://www.2uo.de...
This'll all wait for later, hope you're enjoying a nice mai tai on your holiday.
Before that I hadn't even considered how necessary a product manager or project manager were in software development.
But it was the "No Silver Bullet" essay added as a bonus in my copy that I think about the most. "Never again will we see a 10x productivity increase in a decade", this is self-evident now but must have been crushing to people who had experienced the first compilers, the first high-level languages, the first interactive terminals, and waited for the next incredible leap.
I'm not familiar with the instruction sets of the 6809 but I could also see more compact opcodes, e.g. a JMP with a relative offset can be encoded smaller than JMP with an absolute address.
In modern terms PIC is used for ASLR and is therefore a security requirement. Some arches (I'm most familiar with arm64) are entirely designed around PIC and you need extra hoops to do anything in absolute terms.
We're talking about IP68, where you can take a new phone with you on a long swim.
I wrote a Rabin—Karp implementation in ~2006 as part of the spam and threat scanning stack for the MX Logic mail service. It was incredibly performant, letting us test {n} bytes against an essentially unlimited number of string signatures in O(n) time.