Pretty sure they're talking about popping into recent apps. But that isn't the gesture, you just do a short swipe up and hold for a fraction of a second until you feel the haptic buzz.
edit: actually just tried and you can also pull it to the side, but it doesn't feel quite as natural
見える only means “look” in the “to seem” or “to appear” sense.
Often in English, we have multiple words for sensory experiences to indicate how much focus is put into the action. “Seeing” a picture is less focused than “looking at” a picture. “Hearing” a song is less focused than “listening to” a song.
> “Seeing” a picture is less focused than “looking at” a picture.
Isn't that backwards? Like in the phrase "they look but do not see", which was what I had in mind in my first comment. Isn't that something like "見るけど見えない" ?
But as you've implicitly noted, you cannot see something without looking. That would be physically impossible.
You can also use "look" to emphasize that focus does not exist; one of the sentences I've collected for interesting use is "He stared at the page, not seeing it."
In that case, there is no possibility of a page being overlooked or otherwise missed. What the sentence is telling us is that although "he" is directing his eyes at the page, his mind is on something else, so "seeing" never occurs.
The difference between "see" and "look" has nothing to do with focus. It is what I noted in the discussion of Mandarin - success. Seeing is the goal of looking.
Note that this phenomenon where native speakers have no trouble obeying a distinction that their language requires, but come out with total nonsense when asked why they choose one form or another, is completely characteristic of grammatical rules, and not characteristic of vocabulary selection.
> How do you propose AWS “collaborate” with Elastic or Redis Labs under the terms of the SSPL?
This is quite simple, and should have happened before these companies decide to switch licenses because of Amazon. Each time Amazon decides to use an open source product, instead of doing it for free, they should contact the parent company and offer them a fee. There are many advantages of such an arrangement: a single version exists, the parent company has a stable source of income etc.
I might be mistaken, but this path was possibly chosen by Citus and Azure, and nobody seems to complain.
It depends. For example, when Ubuntu first appeared and Canonical hired some prominent Debian maintainers, they were criticized for that. But I believe the final net benefit was positive.
The problem here is what happens when Amazon stops to pay them. If the owner of the project is a foundation or a similar organization, it may have better chances of survival.
> If you set your hard limit to $20, then Amazon should refuse to create more than 50 secrets. That's a safe behavior which limits your spend to at most $20.
I have 100 secrets and no hard limit. Now I set the hard limit to $20. What does AWS do?
Are you under the mistaken impression that this feature is already implemented in mobile Safari on iOS 17.3? It isn’t.
On iOS 17.4, you’ll be able to see that the divider is thicker and obvious. Long-press on the Safari address bar for an illustrative example. See the gap between “Voice Search” and “Move to Tab Group”?
> Are you under the mistaken impression that this feature is already implemented in mobile Safari on iOS 17.3?
The blog post didn't mention iOS at all. I'm glad to hear that the feature is coming in the future, though it's strange that the blog post didn't mention it, and also strange that they didn't implement it in 17.0 at the same time as desktop.
That's a grouping meaningful to Christians themselves, but meaningless to non-Christians, which means it's not a good way for this survey to be grouped.
To group things for statistics, pick the grouping level that is meaningful to all the entries in that same list.
> I haven't yet found any great way besides email-as-todo list to manage this.
Which is fine. Put them in a To-Do folder. The original formulation of Inbox Zero suggested three actions:
1. Take care of the e-mail right now. Then archive it.
2. If you can take an action, but not right now, move it to “Follow Up”.
3. If you need someone else to take an action, move it to “Hold”.
It’s _Inbox_ Zero, not e-mail zero. Get the inbox – the place for unprocessed things – empty. Get it empty by processing the things. Then go do something other than e-mail.
This reads a bit like a microcosm of David Allen's "Getting Things Done" system.
Unprocessed emails = "Collection Bucket"
Follow Up folder = "Projects" list
Hold folder = "Waiting For" list
Except with GTD you do this with not just emails but also text messages, DM's, snail mail, personal lists you've jotted down, etc. It's a life organization system.
What on Earth are you referring to?
reply