syncsynchalt

They're replying to a user that's giving incorrect or non-sensical replies over and over again. It's not worth time engaging with them with a considered reply, probably best to ignore and move on.

See also "lp0 on fire", an error message for generic printer problems on Linux.

https://musings.danlj.org/2019/05/15/incomplete-information....

Because half of the US is geologically dead.

I don't understand the argument, wouldn't you _want_ an EV if you have frequent power outages?

You could run your house for weeks off a 100kWh traction battery with V2G.

Presumably the organization giving away the million dollars is the arbiter of that question.

They're just covering two ends of the market. I can't stand wearing Pros myself, I can feel the sweat building up in any isolating earbud, and it makes me feel itchy. Would hate for the non-isolating product to disappear.

They mean isolating vs non-isolating.

Airpods Pro are isolating, Airpods are not.

And some, like Anguilla or Tuvalu, hit the lottery and get a nice income from renting theirs out for general use.

Is archive.is still a malicious site that DDOS's finnish security bloggers or has that been sorted?

Had to come back to this post a week later, after having read that Colwell memoir / oral history. Thanks for posting it, really enjoyed it (and not just because I'm a former intel acquisition/employee).

Contracting for more chips than you can make isn't a fun situation to find yourself in, nobody is doing it for profit (it's actually quite expensive in time, money, and reputation to litigate the fallout).

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

Maxwell's Silver Bullet?

You did well to skip the 2015-2020 era (butterfly keyboards, touchbar).

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.

> the hardware works with no problem

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.

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.

PIC is usualy more a _runtime_ benefit rather than a linker benefit, 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.