https://web.archive.org/web/20260505052217/https://www.thatp...

https://archive.ph/sM7O5 (missing images and styling, but the content all seems to be there)

[1] https://www.ifixit.com/News/110039/double-trouble-for-repair...

[2] https://www.eff.org/deeplinks/2025/06/right-repair-law-washi...

But that might be violating the Computer History Museum's license: https://github.com/amix/photoshop/blob/2baca147594d01cf9d17d...

Links at the bottom for those of you who'd prefer to skip my long-winded story.

I use a single large(ish) monitor and multiple virtual desktops, or “spaces” as macOS calls them. I have Chrome windows on all of my desktops. When I quit Chrome with ⌘Q and then relaunch it, it collects all of my Chrome windows onto one desktop instead of restoring them to the desktops that they were on previously.

For something like 14 years(!), this has driven me up a wall.

Notably, it doesn’t happen when Chrome relaunches to update itself or when I reboot my machine. In those cases, the app happily restores all my windows to their respective desktops. It’s almost as if it’s taunting me: “oh sure, I can do what you want, I just choose not to sometimes.”

Every once in a while, I go down a rabbit hole, trying to find a solution. I always come up empty-handed. Usually I just find a small handful of other people complaining the same issue. It was never a particularly easy thing to google, and it didn’t help that that it wasn’t clear who was even at fault. Was it a Chrome thing? A macOS thing? Maybe some combination of both? Or even worse, maybe it was a “wontfix, works as intended” situation?

Over the years, I’ve learned to cope. I rarely quit Chrome anyway, aside from updates and reboots, so the itch wasn’t that strong. Or maybe the itch just became part of me. Who knows.

But today, reading this post about things that suck in macOS, I thought of my own thing that sucks in macOS. Like remembering an old friend. An old friend who drove you crazy but who, nonetheless, you cared about.

And today, for old times’ sake if nothing else, I once again googled some combination of the words “Chrome”, “restore”, “windows”, “multiple”, and “spaces”. And folks, this time, I found it.

There’s a setting called NSWindowRestoresWorkspaceAtLaunch. (How had I never found this before? It’s so simple!) You can change the setting for any app, not just Chrome.

https://superuser.com/a/1490087/77154

In case the Stack Exchange network finally succumbs to whims of private equity or otherwise gets lost to sands of time (it’s a fear I have), here’s a gist with the same instructions:

https://gist.github.com/f-steff/0163e0c1ed174e8ab7b33101ab473b5a

I can also put to rest my internal “feature vs bug” debate. Here’s Apple’s response to a bug report from the Chrome team (presumably from before they added the NSWindowRestoresWorkspaceAtLaunch setting):

This issue behaves as intended based on the following: Application restart does not preserve space assignment. We are now closing this bug report.

https://issues.chromium.org/issues/40531488#comment57

Comments URL: https://news.ycombinator.com/item?id=40167961

Points: 1

# Comments: 0

If you’d prefer, feel free to skip over the story to the links at the bottom.

I use a single large(ish) monitor and multiple virtual desktops, or “spaces” as macOS calls them. I have Chrome windows on all of my desktops. When I quit Chrome with ⌘Q and then relaunch it, it collects all of my Chrome windows onto one desktop instead of restoring them to the desktops that they were on previously.

For something like 14 years(!), this has driven me up a wall.

Notably, it doesn’t happen when Chrome relaunches to update itself or when I reboot my machine. In those cases, the app happily restores all my windows to their respective desktops. It’s almost as if it’s taunting me: “oh sure, I can do what you want, I just choose not to sometimes.”

Every once in a while, I go down a rabbit hole, trying to find a solution. I always come up empty-handed. Usually I just find a small handful of other people complaining the same issue. It was never a particularly easy thing to google, and it didn’t help that that it wasn’t clear who was even at fault. Was it a Chrome thing? A macOS thing? Maybe some combination of both? Or even worse, maybe it was a “wontfix, works as intended” situation?

Over the years, I’ve learned to cope. I rarely quit Chrome anyway, aside from updates and reboots, so the itch wasn’t that strong. Or maybe the itch just became part of me. Who knows.

But today, reading this post about things that suck in macOS, I thought of my own thing that sucks in macOS. Like remembering an old friend. An old friend who drove you crazy but who, nonetheless, you cared about.

And today, for old times’ sake if nothing else, I once again googled some combination of the words “Chrome”, “restore”, “windows”, “multiple”, and “spaces”. And folks, this time, I found it.

There’s a setting called NSWindowRestoresWorkspaceAtLaunch. (How had I never found this before? It’s so simple!) You can change the setting for any app, not just Chrome.

https://superuser.com/a/1490087/77154

In case the Stack Exchange network finally succumbs to whims of private equity or otherwise gets lost to sands of time (it’s a fear I have), here’s a gist with the same instructions:

https://gist.github.com/f-steff/0163e0c1ed174e8ab7b33101ab47...

I can also put to rest my internal “feature vs bug” debate. Here’s Apple’s response to a bug report from the Chrome team (presumably from before they added the NSWindowRestoresWorkspaceAtLaunch setting):

This issue behaves as intended based on the following: Application restart does not preserve space assignment. We are now closing this bug report.

https://issues.chromium.org/issues/40531488#comment57

https://web.archive.org/web/20000517232106/http://webreferen...

Digging around a bit more, the original webreference.com (along with this article) existed until around April 2020. It's since been replaced by a generic landing page with a prompt to "subscribe to be the first to know when we relaunch". Shame that the article's URL doesn't work anymore after being maintained for 22 years. I imagine the domain was sold or something?

https://web.archive.org/web/20200330143723/http://webreferen...

I had no idea that you could end with a drag to expand your selection by word or by line like that. That's really cool. (The author's using Linux, but it works on macOS too.)

> Please note you can't hide your online.

https://faq.whatsapp.com/general/chats/about-last-seen-and-o...

The fact that those two things can't be disabled actually makes me want to use WhatsApp less. I doubt I'm alone in that. Makes me wonder if Facebook's "engagement" stats account for those types of disincentives.

I live in Europe and work for a very remote-friendly, NY-based company, and I work pretty normal European hours. I have 2-3 hours of overlap with the various members of my team, and that's all I need. (In fact, I'm more productive in the morning here because it's easier for me to focus when our group chat is mostly quiet.)

Of course, it's not as simple as saying that you can work from anywhere for anybody at any time, but I don't think it's fair to say that timezone issues are not for the company to solve.

https://medium.freecodecamp.org/7-reasons-to-outlaw-reacts-f...

And I wish I had a reference for this, but I seem to remember reading that any future performance optimizations that could be applied to function components could probably also be applied to class components (at least ones that contain only a render() function and nothing else).

In any case, I'm hoping that React eventually gets to a point where developers don't have to make a choice between class and function components, and the compiler or the runtime makes that decision for us on a per-component basis.

EDIT: As an example, here's a Babel plugin that takes care of the conversion for you at compile time: https://github.com/remcohaszing/babel-plugin-transform-react.... Not sure what its heuristics are for determining what should and shouldn't be converted though, if any.

What are the chances of GitHub introducing stacked diffs (or a similar abstraction) as an option? It'd be great to try out this workflow on a non-trivial project, but it seems like a hard sell organizationally when it involves migrating to and supporting a completely different tool like Phabricator or Gerrit.

https://interaktiv.morgenpost.de/mauerzeichnen-auswertung/