What sort of timescale do you mean by "soon"? When you start doing a new exercise regime, it's really common to experience DOMS[1] for the first few weeks. It really feels like the end of the world (personal experience) but it's not actually an indication of real injury and it's generally safe to push through it if you can (and doing so can actually alleviate the pain, at least temporarily). Distinguishing between DOMS (where it's safe to push through) and real injury (where you definitely should not) comes with a bit of practice, and honestly, compared with the few times I've hurt myself for real... DOMS felt worse. Except when I slipped while holding weight and broke my toe. Strongly recommend against that :)
If you're experiencing exercise-induced injuries immediately during a workout (and if you have a budget for this), it might be good to talk to someone about what you're trying to do. Some gym plans include a bit of consultation time with a staff trainer, and they can probably help you work around whatever the problem is, sometimes simple adjustments can help (particularly anything involving preexisting shoulder damage, most of the commonly-recommended shoulder exercises have substitutes that are less risky for already-damaged shoulders).
> We do not have enough maintainers. We do have a lot of people who write code, we have a fair number of maintainers, but... it's hard to find people who really look at other people's code and funnel that code upstream all the way, eventually, to my tree... It is one of the main issues we have.
If I read this correctly, they have a lot of contributors, but few people willing to follow through with the code so it gets all the way up to Linus' tree. I don't see how rust would really help there.
It could be. Maybe there will not be more reviewers, but the process of reviewing could be faster. For example, in the kernel there are inline functions, which accept a constant (known at compile time) integer argument, and they make a switch or loop over that integer. The trick is to force compiler to inline function and to throw away most of switch's cases, or unroll loop completely, or make some other optimizations based on knowledge of the passed integer value.
Such a functions are exported to a public kernel API sometimes. So any kernel developer could call them. It make unavoidable a mistake of a programmer, when some of those functions was called with an unknown at compile time integer value. It is not a bug as it is, code would compile and work nevertheless, code would be bigger that it could be, maybe slower, that's all. But reviewer should be finding such a misuse of API.
It is just one example, linux kernel uses a lot of tricks and exposes it via APIs, reviewer must be aware of all of them and to check everything by itself.
Compare it with Rust. In rust one can encode a lot more limits on the right use of an API than in C. Encode and enforce. Even when rust sometimes cannot do it, rust have nice macros, instead of C's macro-horror. So a lot of mistakes that could be made with C, could be avoided with Rust. So it would be easy to review code, it would take less time from a reviewer to review code.
I would strongly recommend deploying such a regular expression matcher to avoid problems like this.
There are examples in the above article that you can use to test anything in your production deployment that accepts regular expressions to see how well it copes.
I could be mistaken, but I think this is a somewhat weaker version of Android for Work, which shipped about two years ago, I believe (couldn't find the exact date). Perhaps Apple is doing something that AfW isn't already doing, but it's hard to tell from this article, which doesn't mention AfW at all.
I'm not sure of the differences between AfW and this either but I don't think it matters in the big picture. Instead, I see this as just one step in many that Apple has taken in designing their products around user privacy, when possible.
First, let me say that I'm not panicking about the probability of this actually happening, but: "I'm more likely to get killed by a fall in the tub than by a terrorist" is only true of an _arbitrary_ attack at an _arbitrary_ venue and time (and an _arbitrary_ bathtub :)). Events that use Yondr announce it ahead of time, waving a big flag that says "no one here will be able to call for help." The probability of an attack at such an event would be much higher compared to an arbitrary one (although, definitely still small, which is why I'm not exactly panicking...)
Your entire premise is incorrect. Even with Yondr hundreds of people will be able to call for help. Such as ushers, security, ticket takers, concession workers, event management, etc, etc, etc.
Yondr means less (or at least less rapid) social media publicity for a terrorist act, so one could argue that it deters terrorists.
I don't think they're available in the web client, but if you 1) download google earth 2) View -> Explore -> Moon 3) In the layers panel, Moon Gallery -> Apollo Missions -> [Double-click the logo of your favorite] -> Click a Camera icon -> Click the Panorama itself, you'll fly into the terrain-aligned panoramas taken during the mission. (Sorry it's so confusing to find, we (joint google/nasa project) did this in 2009 for the Apollo 11 40th, when the tools weren't quite as good as they are now). Enjoy!
Admittedly, my initial comment sounds a bit sarcastic, we were joking in the office here, but I was really impressed actually. But now I am speechless.
Do you remember when the only way to make your site discoverable was to 1) get yahoo to add you to their hand-curated list of sites or 2) trade banners with a super scummy link exchange? If we still had that internet, the only sites that would get any traffic at all would be the ones that could justify their existence with traffic, i.e. these[1]. How do you get traffic if you can't get listed? You can't unless you advertise through other media.
Is everything better? No. Privacy's worse, signal to noise is worse (that's a natural consequence of availability, anyway). Are a lot of things better? Yep. Niche sites can get traffic in a way they never could before. That's the natural consequence of taking humans out of the loop- instead of having to interest Jerry or David, now your only requirement for indexing is to interest anyone who is also interesting.
Let's keep working to make things better, but let's also not forget the improvements that have already been made.
I never did either of those but more commonly one could:
3) Join a web-ring
4) Add a link in Usenet signatures
5) Ask to be included in the WWW Links section of your interest group's magazine
Or
6) Not worry about discoverability at all because the Web wasn't about growth and profit
My preference as a publisher and reader was for web-rings, they exemplified the attitude of sharing and mutual assistance on the early Web that has been largely lost nowadays.
Good. When I traveled out of the US, I noticed my phone battery life was terrible. Inspecting via catlog, I noticed that the amazon appstore (which I didn't actually have installed directly) was hitting an amazon url in an extremely tight loop, and getting a 403 Forbidden every time (you know, one of the errors that means "don't try again without fixing yourself").
My only explanation is that the amazon appstore has some sort of geographic restriction on the server-side, and the app wasn't written to handle that. I couldn't tell which app was actually responsible, so I just disabled or uninstalled every Amazon app, even though I find some of them useful (rapid package delivery notifications are pretty helpful in a city, when your package is probably sitting on the stoop unprotected). Doing so restored my battery life.
Hopefully this means Google is watching for Amazon's overreach now, and I'll be able to safely get my notifications again.
And if you're using some common Linux fonts (I'm pretty sure it's dejavu, in this case) that character renders as the Klingon Empire logo.
0xF8FF is in the Unicode Private Use range, so any font is allowed to put whatever they want there :) (If you're curious what your current font has: http://www.unicodemap.org/range/78/Private_Use/)
If you're experiencing exercise-induced injuries immediately during a workout (and if you have a budget for this), it might be good to talk to someone about what you're trying to do. Some gym plans include a bit of consultation time with a staff trainer, and they can probably help you work around whatever the problem is, sometimes simple adjustments can help (particularly anything involving preexisting shoulder damage, most of the commonly-recommended shoulder exercises have substitutes that are less risky for already-damaged shoulders).
1. https://en.wikipedia.org/wiki/Delayed_onset_muscle_soreness