112 stories
·
0 followers

Top 10 Docker logging gotchas every Docker user should know

1 Comment

Docker changed the way applications are deployed, as well as the workflow for log management. In this article, Stefan Thies reveals the top 10 Docker logging gotchas every Docker user should know.

The post Top 10 Docker logging gotchas every Docker user should know appeared first on JAXenter.

Read the whole story
walokra
18 days ago
reply
Nice overview of how logging works with Docker.
Share this story
Delete

★ Public Service Announcement: You Should Not Force Quit Apps on iOS

6 Comments and 12 Shares

The single biggest misconception about iOS is that it’s good digital hygiene to force quit apps that you aren’t using. The idea is that apps in the background are locking up unnecessary RAM and consuming unnecessary CPU cycles, thus hurting performance and wasting battery life.

That’s not how iOS works. The iOS system is designed so that none of the above justifications for force quitting are true. Apps in the background are effectively “frozen”, severely limiting what they can do in the background and freeing up the RAM they were using. iOS is really, really good at this. It is so good at this that unfreezing a frozen app takes up way less CPU (and energy) than relaunching an app that had been force quit. Not only does force quitting your apps not help, it actually hurts. Your battery life will be worse and it will take much longer to switch apps if you force quit apps in the background.

Here’s a short and sweet answer from Craig Federighi, in response to an email from a customer asking if he force quits apps and whether doing so preserves battery life: “No and no.”

Here, from the official support document on forcing applications to close, is Apple’s own advice on when to use this feature:

When you double-click the Home button, your recently used apps appear. The apps aren’t open, but they’re in standby mode to help you navigate and multitask. You should force an app to close only when it’s unresponsive.

Update: MacDailyNews quotes a 2010 email from Steve Jobs:

Just use [iOS multitasking] as designed, and you’ll be happy. No need to ever quit apps.

Just in case you don’t believe Apple’s senior vice president for software, Apple’s own official support documentation, or Steve Jobs, here are some other articles pointing out how this habit is actually detrimental to iPhone battery life:

This thing about force quitting apps in the background is such a pernicious myth that I’ve heard numerous stories from DF readers about Apple Store Genius Bar staff recommending it to customers. Those “geniuses” are anything but geniuses.

It occurs to me that some of the best examples proving that this notion is wrong (at least in terms of performance) are YouTube “speed test” benchmarks. There’s an entire genre of YouTube videos devoted to benchmarking new phones by running them through a series of apps and CPU-intensive tasks repeatedly, going through the loop twice. Once from a cold boot and the second time immediately after the first loop. Here’s a perfect example, pitting a Samsung Galaxy S8 against an iPhone 7 Plus. Note that no apps are manually force quit on either device. The iPhone easily wins on the first loop, but where the iPhone really shines is on the second loop. The S8 has to relaunch all (or at least almost all) of the apps, because Android has forced them to quit while in the background to reclaim the RAM they were using. On the iPhone, all (or nearly all) of the apps re-animate almost instantly.

In fact, apps frozen in the background on iOS unfreeze so quickly that I think it actually helps perpetuate the myth that you should force quit them: if you’re worried that background apps are draining your battery and you see how quickly they load from the background, it’s a reasonable assumption to believe that they never stopped running. But they did. They really do get frozen, the RAM they were using really does get reclaimed by the system, and they really do unfreeze and come back to life that quickly.1

An awful lot of very hard work went into making iOS work like this. It’s a huge technical advantage that iOS holds over Android. And every iPhone user in the world who habitually force quits background apps manually is wasting all of the effort that went into this while simultaneously wasting their own device’s battery life and making everything slower for themselves.

This pernicious myth is longstanding and seemingly will not die. I wrote about it at length back in 2012:

Like with any voodoo, there are die-hard believers. I’m quite certain that I am going to receive email from people who will swear up-and-down that emptying this list of used applications every hour or so keeps their iPhone running better than it would otherwise. Nonsense.

As Fraser mentions, yes, there are exceptional situations where an app with background privileges can get stuck, and you need to kill that app. The argument here is not that you should never have to kill any app using the multitasking switcher — the argument is that you don’t need to do it on a regular basis, and you’re not making anything “better” by clearing the list. Shame on the “geniuses” who are peddling this advice.

And don’t even get me started on people who completely power down their iPhones while putting them back into their pockets or purses.


  1. The other contributing factor to believing that force quitting is good for your iPhone are the handful of apps that have been found to be repeated abusers of loopholes in iOS, such that they really do continue running in the background, wasting battery life. Most infamously, Facebook was caught playing silent audio tracks in the background to take advantage of APIs that allow audio-playing apps to play audio from the background. They called it a “bug”. In those cases force-quitting the apps really did help, and I see no reason to trust Facebook. So if you want to keep force quitting Facebook, go right ahead. But don’t let one bad app spoil the whole barrel. The Battery section in the iOS Settings app can show you which apps are actually consuming energy in the background — tap the clock icon under “Battery Usage” and don’t force quit any app that isn’t a genuine culprit. ↩︎

Read the whole story
walokra
65 days ago
reply
Good point.
Share this story
Delete
4 public comments
tiglathpalasar
87 days ago
reply
IOS really sucks.
johnnysimmons33
87 days ago
reply
Noted! well we are all just clueless idiots I guess bc nobody ever told me that I should just leave my 800+ apps running and my phone will be better for it!
Nob Hill, San Francisco
arnabocean
86 days ago
Well, most of us come from a background of operating systems where *we* the users are expected to think about how the *software* should operate and handle memory. That's backwards, and yet we take a long time to be comfortable with the idea that an operating system should be mature and sophisticated enough to handle the "background" logistics. :-)
jhamill
90 days ago
reply
While it might be correct that you don't need to force quit apps or power down your phone or whatever. The bigger problem here, to me, is the people who feel the need to tell other people that they're using the device wrong. It's my device, I'll use it how I want, no matter what you say.

Quit wasting time writing the you're using your device wrong stories.
California
arnabocean
90 days ago
There's two sides to this, isn't it. There's one group of people who do things thinking "this helps me with whatever". With this, you can demonstrate that their actions don't achieve their goals, and then they change their actions. The other group of people are different. For example, they might choose to open Safari, type "google" into the search bar, click the first link to "google.com", type into the search bar in google, and *then* see their actual search results. You might show them there's a better way, and they might say, "well this is my phone, and I'll use it how I want, no matter what you say". Well, they're right, and in that case, you just walk away knowing they're idiots. But it doesn't mean you stop showing other people that there is indeed a better way. :-)
tewha
89 days ago
I have no problem being told I'm doing something wrong and could be doing it in a way that's better and easier, but I guess you do? That's unfortunate, but don't worry: Nobody will ever force you to be rational. You can use the device however you like. Just don't be surprised when there's people pointing out it's not only unhelpful but actually counter productive. And try not to get angry; they have every right to talk about such things.
jhamill
89 days ago
Congratulations everyone, we've "Well, actually" on the internet. That's just as good as the 'you're doing it wrong' article.
tewha
89 days ago
And congratulations, jhamill, for being an ignorant and aggressive asshole.
jhamill
89 days ago
Sure, okay @tewha I'm not the one calling people assholes on the internet but, you do you.
tdknox
91 days ago
reply
The one app I do force quit regularly is Waze, because if you don't it continuously monitors your location even when you're not driving or using it.

iOS 11 makes that much more clear with a giant blue bar at the top of the screen 'Waze is using your location', which miraculously goes away after I punt Waze.

But otherwise, Gruber is completely correct.
Cupertino, CA
Repton
88 days ago
Go go settings ➡️ privacy ➡️ location services, and set it to only have access when you are using the app?
neilcar
85 days ago
The problem with that is, when I'm actually navigating, I may be using other apps (to play music, for example). If I have Waze only use location services when the app is in the foreground, it isn't going to work well. Like tdnox, I force-quit Waze when I'm done with it.

Simple secrets to a successful Agile process

1 Share

Not all Agile implementations are done well. How can you tell that your team has done it right? Here are Gleb Bryksin's six signs that a company has a successful Agile process.

The post Simple secrets to a successful Agile process appeared first on JAXenter.

Read the whole story
walokra
125 days ago
reply
Share this story
Delete

A Complete Guide To Switching From HTTP To HTTPS

1 Comment

   

HTTPS is a must for every website nowadays: Users are looking for the padlock when providing their details; Chrome and Firefox explicitly mark websites that provide forms on pages without HTTPS as being non-secure; it is an SEO ranking factor; and it has a serious impact on privacy in general.

A Complete Guide To Switching From HTTP To HTTPS

Additionally, there is now more than one option to get an HTTPS certificate for free, so switching to HTTPS is only a matter of will.

The post A Complete Guide To Switching From HTTP To HTTPS appeared first on Smashing Magazine.

Read the whole story
walokra
127 days ago
reply
Good overview to the topic. In practice switching e.g. WordPress to HTTPS is somewhat more cumbersome.
Share this story
Delete

iOS 11 Tidbits

1 Comment

Nice rundown from MacRumors of small changes and additions in iOS 11.

Read the whole story
walokra
129 days ago
reply
Have been running iOS 11 Beta and it has nice improvements and already works relatively well.
Share this story
Delete

Apple releases a magic keyboard with a numeric keypad

1 Comment

If you’re looking for a wired keyboard from Apple, well you’re out of luck. The company introduced the Magic Keyboard with Numeric Keypad shortly after its WWDC keynote today, and quickly removed its wired keyboard with numeric keypad from its online store.

The move increases the price of the cheapest keyboard you can purchase from Apple from $49 to $79 for its standard Magic Keyboard, while the new magic keyboard with numeric keypad will come in at $129. A $50 premium for a few additional keys is definitely ridiculous, but plenty of people can’t work without the numeric keyboard, and the wireless capabilities have been a request for some time.

It just would’ve been nice if Apple kept around the wired keyboard for people who don’t want...

Continue reading…

Read the whole story
walokra
134 days ago
reply
Bigger arrow keys are +
Share this story
Delete
Next Page of Stories