It looks a bit unusual at first but I've gotten used to a coworker doing that.
519 karma · joined October 15, 2013
It looks a bit unusual at first but I've gotten used to a coworker doing that.
For some artists there may be an "essentials" playlist or something, which helps, but that already requires a certain level of popularity. If there's nothing like that and no albums, I need to open a single, pick one track to play (because four remixes of the same song one after another isn't my idea of a good time), then the same thing for the next single, etc. Usually I just give up and go find something with less clicking.
An Objective-C class interface might look like
@interface MyClass
- (NSString *)methodWithParam1:(NSString *)str1 param2:(NSString *)str2;
@end
And you'd call it like this: NSString *newString = [myClassInstance methodWithParam1:val1 param2:val2];
The Swift translation layer lets you call that like this: let newString = myClassInstance.method(param1: val1, param2: val)
And the translation works the other way around too, making Objective-C able to call a subset of Swift methods that use types representable in Objective-C. You need the named parameters to make it work, because the names of the parameters are part of the method name.So it's a nice feature, but it was also necessary for Apple to be able to make Swift an incremental addition to their platform (yes I know of the Python/Ruby/etc translation layers for Objective-C but they're nowhere near as nice.)
I'm no expert but I believe there may actually be some limited basis to that claim: ruminants can eat things we can't (grass) and there are areas where it's more ecological to grow grass and let ruminants eat it than try to grow things that we could process. You also get the benefit of better topsoil with the help of the animal dung.
But I think the (huge) majority of the meat we eat is fed grain, where we're obviously wasting energy.
https://www.youtube.com/watch?v=_ahvzDzKdB0
or as PDF:
https://www.cs.virginia.edu/~evans/cs655/readings/steele.pdf
The local energy company is also converting some artificial caves, originally dug for oil storage, to similar use: https://www.helen.fi/en/news/2018/Gigantic-cavern-heat-stora....
Being able to read in direct sunlight is a nice bonus.
Given that the MacRumors article says that the Lexus was parked, it might be a human-driven car for gathering maps data?
https://www.theguardian.com/cities/2015/may/05/amsterdam-bic...
https://thl.fi/web/environmental-health/environmental-pollut...
That's why I think questions about frequency and "most users" (nebulous term, I admit) come into play: yes/no permission dialogs aren't the best and many users do just click through them without thinking, but there's a world of difference between asking several times a day and asking a couple of times a month.
If my usage is far below average, then I agree that it's probably better not try to restrict it. If, as I would guess, I use it more than most, then it feels exceptional enough that letting the user know when it's happening would be fine.
If you could give a permanent permission to a given app, I'd imagine even the daily streamers wouldn't be too badly inconvenienced.
As an iOS developer I run Xscope to check details of designs, I don't know, maybe once every two weeks? And I guess I've probably used Acorn's color picker outside its own window during the last year, but I'm not sure about that.
I'd imagine that most users need apps reading arbitrary pixels off their screen less often than I do. I'd appreciate a warning from the operating system when an app tries to do that.
I care.
I live in three editors: Xcode for iOS/Mac/Swift on server development, VS Code for Rust, Go and Python, and Sublime for a thing that starts up fast, opens new windows fast and can deal with huge amounts of text. I wouldn't mind reducing that number to two, but it doesn't seem likely to happen anytime soon.