syncsynchalt

Games are not as fun at 1 fps, or with 10s input lag.

Congrats! I have two, both for the much easier task of doing bibliographic work for the books.

The filesystems of macOS are particularly opinionated, much more than most Unices which tend toward "anything is allowed [and usually preserved] except \0 and /".

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...

aka "gravity losses". Every second you're not (yet) in orbit you're losing dv / cargo capability.

I think it was due to voids in the hinge area causing localized plasma impingement and heating. The v3 design has a more continuous shape around the hinges.

The difference is having high-bandwidth signal pointed up / away from the wall of plasma.

Nothing, except a story's size relative to other stories estimated by the same team.

What you've said is correct.

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.

If we pipe seq to less and look at the list of running processes using ps aux, we can see that the seq program is not running. ... This explains why the seq program is killed when it is piped to less.

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 CSS has broken some time in the last 12 years, people have posted archive links that make it much clearer [1].

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...

Happy birthday!

This'll all wait for later, hope you're enjoying a nice mai tai on your holiday.

The very definition of "LAATTIG".

The article is about the literal oil of boiled snake meat, or at least the product that purported to be that.

It's funny, I also read the book as a teen, and I came away from it amazed that IBM was dedicating entire team members to inter-/extra-team communication.

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.

On older hardware such as this it could e.g. let you write a multitasking environment that supported shared libraries without use of an MMU (though you'd hit memory constraints pretty quickly on a Z80-era cpu!).

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.

Samsung only rated the S5 Active as water resistant, and only IP67.

We're talking about IP68, where you can take a new phone with you on a long swim.

That's where I knew the name from. Thank you!

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.

We call it a "black turkey event", nobody saw it coming.

It's the difference between buying a postcard of a place you've never been and having a photo you took as a memento.

It's true, too. Lunar albedo is 12%.

https://www.ign.com/articles/2015/08/05/nasa-releases-a-gif-...

... matter of fact it's all dark.

(The moon has an albedo of 12%)

Take a look at https://issinfo.net/artemis.html

Your illustration is about right, but the angle they're catching now is even a bit further than you've shown.

Sunlight is yellowish in atmosphere since some blue's been scattered by the atmosphere[1], but it's white in space.

[1] https://en.wikipedia.org/wiki/Rayleigh_scattering

This is not universally applicable, especially if an algo isn't deterministic. For example if you were to time "bogosort of 100 items" you'd see increasingly better times the more runs you performed.

Or the now-ubiquitous footer:

"Store cookie? [Yes] [Ask me again]"

Pretty standard option for any home with a teenager, to be honest. Long enough to drag the handset into the nearest coat closet when needed.

And of course, you can use the ~v / ~V commands (as listed in the ~? menu) to increase/decrease verbosity after the connection is established.

That lets you `ssh -vvvv` to a host then once you've figured out the issue use ~V to decrease verbosity so that debug messages don't clutter your shell.

I see this take a lot but I'd argue what Docker did was to entice everyone to capture their build into a repeatable process (via a Dockerfile).

"Ship your machine to production" isn't so bad when you have a ten-line script to recreate the machine at the push of a button.

There's usually an easy-ish way to override malloc/calloc/realloc/free on Unix, as it's very useful to do when debugging issues or just to collect allocation metrics.

In ELF objects (i.e. on Linux) this is usually done with the "Weak" symbol binding. This is an optional flag for symbols in ELF format that let you override a symbol by providing a competing non-weak symbol, which the linker will prefer when there is a conflict. https://en.wikipedia.org/wiki/Weak_symbol

You can see the list of Weak symbols by looking for a 'W' in the output of `nm` on linux hosts.

a search engine for search engines…

Everything old is new again: https://en.wikipedia.org/wiki/MetaCrawler