645 karma · joined May 14, 2015
People are often surprised - "You're reading three books at once?! How do you keep track?". I normally point out that they're probably watching 5 different TV shows right now and they have no problem with that. It's not really different.
A good example is the C++11 standard garbage collection! It was explicitly optional but afiak no one implemented it.
Warnings becoming errors would be scoped to gcc itself only, and they can fix them as part of the upgrade.
It's the type of dog fooding they should be doing! It's one reason why people care so much about self-hosted compilers, it's a demonstration of maturity of the language/compiler.
Higher priority push notifications require a user visible UI element and ca be delivered regardless of certain low power situations.
Definitely not just `ls`.
I've had some luck finding some TikTok creators who curate specific "vibes" and publish Spotify playlists. I think that's just how it's done now.
It's sad that your app won't be as useable but I'd much rather have the universal pasteboard protections. It would be worthwhile if we had to specify a pasteboard access reason in the Info.plist, but that likely would require a new API because it would break all legacy uses of the current API.
1: https://developer.mozilla.org/en-US/docs/Web/CSS/@media/pref...
I usually do this first to make sure the software builds and works, then I try to figure out how to get it working on a newer OS.
A sample:
Pour-over leggings chicharrones same direct trade, sriracha hexagon cardigan succulents pinterest hot chicken tattooed hella. JOMO roof party disrupt taiyaki pickled ugh kickstarter ethical activated charcoal. Gastropub selvage lumbersexual, microdosing mukbang raw denim DIY edison bulb asymmetrical jawn snackwave wayfarers tofu solarpunk organic.
[1]. https://appleinsider.com/articles/10/06/08/cisco_licenses_io...
> The “CPU power” is used to take into account how much calculating capabilities a CPU has compared to the other CPUs and the main factors for calculating it are:
> 1. Whether the CPU is shared, for example by using multithreading.
> 2. How many real-time tasks the CPU is processing.
> 3. In newer kernels, how much time the CPU had spent processing IRQs.
> The current suggested fix for this bug is relying on the theory that while taking into account the real-time tasks (#2 above), scale_rt_power() could return negative value, and thus the sum of all CPU powers may end up being zero.
The author doesn't really describe how this panic is related to uptime. Do long running kernels collect a lot of real-time tasks, is it a leak of some kind?
The suggested fix link doesn't provide any extra context as to why its uptime related either.
[1] https://docs.binary.ninja/dev/bnil-overview.html [2] https://riverloopsecurity.com/blog/2019/05/pcode/ (an example)