Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

macOS needs its grid back

blog.hopefullyuseful.com

Post reply on HN
Print view View original

271–272 of 272 posts

Re: macOS needs its grid back

#271

Post by drfloyd51 »

oneeyedpigeon wrote: post #138
drfloyd51 wrote: post #59

Earlier quoted context omitted.

I want to use full screen apps. But they are not in the command-tab order. So… no good.

They are, but it's nuanced. If you have one app with a single window, it will always be selectable via Cmd+Tab, even if it's full-screened. If you have an app with multiple windows, one of which is full-screened, and you select a non-full-screened window from that same app, you won't be able to return to the full-screened window using Cmd+Tab. Which kinda makes sense, since Cmd+Tab cycles apps, not windows.

I am going to put in a plug for “Which” a command tab replacement that lets you, among other things, cycle between windows like alt-tab.

Re: macOS needs its grid back

#272

Post by joshspankit »

ileonichwiesz wrote: post #99
rmunn wrote: post #41

Earlier quoted context omitted.

See https://en.wikipedia.org/wiki/Bonneville_Salt_Flats — the salt flats are extremely flat (as the name implies), and because of all the salt, no vegetation can survive. Look at the pictures: there are no trees, no grass, no hiding places at all. Anyone standing (or even lying prone) on the salt flats is visible to anyone else for miles around. GP was saying that systems should be "transparent enough that a compromi…

I don’t think the analogy was the issue. What does it mean for a system to be so transparent that it’s obvious when it’s compromised?

What I mean can be shown with an example:

Let’s say first that we know (some) users will inevitably agree to let malware compromise their system, no matter the popup or protections

A compromised system that’s transparent:

- Has only one way an executable can be started and, being designed as a “salt flat”, it’s easy to read

- Exposes all I/O and all network requests (to admins), regardless of driver abstractions

In this case, even a young enthusiast can look at a system and immediately see that it’s compromised, remove it’s ability to start or do work, and likely remove it from the system entirely.

The inspiration for this approach is a backlash against the absolute glut of places to hide in current user-focused systems. From multiple startup options, to services, to drivers, and in to the “hidden from the admin” executables that can be compromised it’s an ever-worsening problem that erodes user’s ability to keep their own system secure

Post reply on HN