You don't have to "page through a giant iPhone screen", you can type and select. I used to use it all the time, without ever reaching for the mouse to do so.
Launchpad also let you change the order of app icons and group them into pages and folders; I don't think the new system lets you do any of these things.
Launchpad was focussed on a single task: launching an app. If I need to launch an app, I know I need to 99.9% of the time (I'm hedging; it's probably 100%), so there's no benefit showing me documents, web pages, and god-knows-what-else at the same time.
I nearly forgot: while I was testing Tahoe, I had a situation in which some apps just did not show up when I typed. They were in the list, they just got filtered out incorrectly. I've no idea if this was a bug or not; I'll see when I upgrade to the final release.
Yes, this is what I've been doing during the beta, and it's far less useful than Launchpad IME so far.
> If you want more precision unmodified F4 followed by CMD+1 will allow you to search only apps.
It looks like I had previously done so, and now the setting is 'stuck'. I.e. it's the default view — I can still go 'up' to search across stuff, but F4 takes me to an app launcher by default, so that's one drawback eliminated (thanks).
As an aside, I've learnt just now while testing this that F4 has an awkward asymmetrical input buffer. You can open+close instantly with two quick presses, but the same does not work to close+open. I'm not really complaining so much about this, just mentioning it!
The spotlight apps view is available for binding a keyboard shortcut directly. Maybe yours became bound to the spotlight shortcut?
I always just disabled these from Spotlight. If I want to search for files I use the search bar in Finder.
But, bringing up Spotlight, clicking backspace, then clicking on the Applications icon brings you basically Launchpad.
They've mushed them together, but there seem to be three states: Spotlight with typing pre-filled, Spotlight bare with some additional icon options, and then Launchpad, which is more Spotlight than I remember it being.
Unless there's some weird setting, that's only in Tahoe. At the very least, it's only enforced in Tahoe; I was using F4 to bring up Launchpad in Sequoia, as I have in every version of MacOS for a long time.
So if someone accidentally triggered Launchpad and realized they could see their apps, they might use that forever (not knowing you can put your Applications folder in your Dock and use it as a start menu lol).
I’m surprised to find out it was itself an Apple product; I had always assumed it was a third-party shell, akin to Norton Desktop for Windows 3.1.
Doesn't work for me (Sequoia 15.4)
I use it rarely, but sometimes I'm happy it's there.
If I had this need, it wouldn’t even occur to me to solve it with Launchpad; I would just go to /Applications in Finder and sort by “Date Added”. (Which is a non-default column, but a very helpful one, so the series of gestures to enable it for a given folder is almost reflexive to me now.)
Compared to: 1 - 4-finger pinch, 2 look for the app.
1. Launchpad filters based on what you type. You don't have to page through things 2. As soon as you type anything, the first hit is selected and the return key launches it 3. Launchpad shows nothing but apps. As an app launcher, it's fantastic.
If Launchpad is gone I'm going to be sad.
I still have an M1 Macbook Pro with touch strip, and my Launchpad touch strip button still works, bringing up Spotlight but with a predicate that makes it search only ./Applications and ~/Applications.
Launching seems easy enough from Finder but you never know about innovation.
I suppose Spotlight is OK as a substitute: COMMAND-SPACE, then type to filter and return to launch. It's a little more clunky (as the search results take a few milliseconds to be assembled) but it'll work.
Cmd+space to open spotlight already worked and typing was the best option for that use case.
I do like the new spotlight experience but this feels like losing a gesture, and it does not spark joy scrolling through the app list.
What if you rely on groupings to remember what you have installed for a given activity?
What if you want a quick visual overview of what is available to you?
What if you like or even prefer launchpad?
What if you install tons of tiny little apps that have a specific, if infrequently used, purpose?
What if you enjoy a little app gardening?
What if you don't like command-prompt style interactions?
What if you see value in having more than one way to do something?
What if you have 20+ years of muscle memory established?
What if the only thing you know prior is how to use your iphone?
And on another note, what is it with tech people lacking the ability to see how other types of people may want to use the hardware they paid for with their hard earned dollars? I am so sick of this awful perspective of, "everybody in the world must be exactly like me"
also spotlight hogs resources indexing stuff all the time, completely pointless when you just want a list of apps
I greatly prefer visual/spatial browsing
For people who never work with things like terminals, sure. For fellow devs, it's an unusual choice unless they routinely cycle through irregularly used apps w/ hard to remember names.
Everyone talks about how CLI is supposedly way more efficient. It is way more efficient to THEM. And now we are stuck in a hell where a good deal of functionality is only accessible if you want and are able to memorize the arcane nonsense that are command names, or the design-by-committee naming choices of moronic PMs who can't stop lapping up whatever bullshit marketing tells them to
Not to invalidate your experience, but you shouldn’t need to memorize too much to use the common command line tools (although it does always help to have more experience using them).
I recommend always keeping a second terminal session open, purely for referencing man pages. You should be able to see most options easily, or be able to grep for the instructions you need.
The tight integration between documentation within the CLI, coupled to the exact software version you have installed, helps immensely when invoking CLI tools.
For the common linux tooling, found in most distros (e.g. coreutils or common busybox ops) the documentation in man pages is quite excellent.
A lot of them also lack sufficient (or any) examples, which are the things I need to see to learn. Making sense of the their sometimes (and seemingly intentionally) obtuse wording when I'm trying to do something I'm not already familiar with makes them a lot harder to parse than they need to be.
And many of the commands are extremely arbitrary. `cd` (change directory) very well could have been `mf` (move folder). `del` in DOS is `rm` in Linux. `move` vs `mv`, `copy` vs `cp`, etc etc. There's no common orthodoxy. If you are not well versed in the history of this stuff its all gobbledygook.
LLMs have been great in this regard, as they can supply those missing examples and then explain to me exactly what it is doing, oftentimes worded more clearly than the original documentation. And they can help me string together whole sequences.
If you only use 'cd', 'mv', 'rm', and 'ln', then really, there is not much to learn. Perhaps the '-rf' option to 'rm', which is how you delete directories (that are not empty). You complained about the naming, but 'mv' requires fewer keystrokes than 'move', and once you know that 'mv' = move, 'rm' = remove, and so on, then what is the issue? It makes sense. DOS had just as "arbitrary" names: 'del' instead of 'rm', for example. The UNIX versions are deliberately short for efficiency, and once you learn them, they are universal.
Man pages are fine. Just press '/' to search by string or regex, and 'n' for next match. They are also consistent: if you want a particular section, you search for it. But it is important to remember that man pages are reference material, not tutorials. If you want quick examples, try https://tldr.sh, https://cheat.sh, or another alternative.
If this is difficult, or you simply do not want to learn it, that is fine: use what works for you. But if you are a programmer, you are going to be learning tools constantly, and the core UNIX utilities are among the simplest. Once learned, they do not change. Personally, I have not had to learn anything new about them since I was 13. I am 31 now. You learn once, and you use forever.
That said, there are real examples of arcane tools. 'ffmpeg' and 'rsync' have some of the most obscure command-line options I have ever seen, which is why I keep bash aliases and functions for the things I do often. That is how you make your life easier as a programmer: learn the fundamentals, then abstract the complexity where it makes sense.
TL;DR: Learning is not optional. Whether it is GNU/POSIX utilities, GUIs, wizards, or even LLMs, you still have to learn them. Man pages are reference material, not tutorials. Learn the basics once, and you are set for life.
These are power tools, meanings they set out to solve one problem quite extensively. They’re not really meant to use as is (just like git), best is to write some alias or functions as a wrapper (or memorize the set of flags you use most).
[0] `brew install tealdeer`, then invoke with e.g. `tldr chown`.
> Man pages are fine. Just press '/' to search by string or regex, and 'n' for next match. They are also consistent: if you want a particular section, you search for it. But it is important to remember that man pages are reference material, not tutorials.
But not everyone gets the chance to do that before they are dropped in a situation where the knowledge is needed. Up until a few years ago (before LLMs) if that was your case and you didnt know how to articulate what you wanted to google (or a teammate), you were fucked.
Like with VI or with emacs. It's sooooooo easy to screw things up in a big way. Better hope you remembered to type shift-colon-Q-exclamation instead of shift-colon-W-Q!
Please, tell me how that makes any sense to anyone without a background in *nix stuff.
I did not grow up in the environment where the above incantations had any context. It was literally a bunch of gobbledygook that made no sense. Why "write" instead of "save"? Why 'quit' instead of 'exit'? In fact I had VI dropped on me quite suddenly for a job, that was a real trial by fire, and I remember this well. (And yes I can operate VI quite fine now, thank you)
I have not worked with many things they require of me either. Before I apply, I either have to learn the very basics, or I will have a hard time, unless they do not mind me not knowing but learning fast.