Did you think we wouldn't check your links? The second one points out that Cisco didn't win, they dropped their legal action. Later it emerged that they had been complaining about some generic C header files that were likely part of the compiler suite anyway, not even Cisco code.
This isn't the first time you have made this bogus claim either. So the question is, why do you keep doing it? Do you still have some loyalty to Cisco, or is someone paying you to do it, or is this a hacked account now controlled by some NSA staffer?
I never meant to imply that the UK was better. My point was that it's the pot calling the kettle black, and none of the involved parties have the moral high ground here.
TFA is designed to teach people how to think about the lifecycle emissions of things, and how to decide if they are beneficial or not. If you calm down a bit and read it in the light it was intended, it's a reasonable article.
My advice is always get it checked. Otherwise you find out one day you have been living with some undiagnosed problem for 30 years and didn't have to suffer the whole time.
There is no test for RA, it's a bit like Lupus - the diagnosis is that you have some subset of the known symptoms and have ruled out everything else.
It's unlikely that you have it if you don't also have at least some of the other stuff, like the vision problems, and of course the thing that differentiates it from other auto-immune problems: that it gets worse when you get an infection.
It's primarily aimed at developers, especially web devs who want to run a Linux based stack for local testing. Also great if you want to do cross-development for a Linux target.
Why not use a VM? WSL consumes far fewer resources, and makes it easier to share files between the two sides with native performance.
One use case WSL works well for is cross compilation using a Linux based toolchain. Similarly when building.NET based software you can compile and test Linux binaries using Mono without the hassle of a VM.
Clearly the desire to have all this stuff has been there for many years, hence the existence of CygWin and several others.
The GP is correct, uranium dust particles are dangerous. If they get in your lungs then your clothes or a sheet of paper won't help you. Note that your lungs are not normally exposed to sunlight either.
That's the problem here. They had buckets of the stuff lying around, one without the lid even on it. Properly handled it can be safe, but it wasn't properly handled.
What all the parent posters and XKCD are missing is that it's not just the dosage, it's the manner of exposure. Temporary exposure to an xray machine stops the moment the machine is turned off. A bucket of uranium specimens may contain dust that can get inside the body. Thus it needs to be handled carefully to avoid that, and in this case it appears that the staff had little idea of what they were doing.
It's the old "banana equivalent dose" fallacy. The body processes and removes excess potassium, but caesium accumulates in certain organs and does long term damage, with the effects only becoming apparent years later.
I detect some unhappiness among Trump supporters of late, because they are busy filing their taxes right now. That promised tax cut, the one that the 1% had a year ago and was due to reach them around now, hasn't materialized. In fact they are paying more tax now, and the realization that they have screwed is finally having an effect.
Strangely I don't see interviews with Cisco CEOs asking them about the level of cooperation with the NSA or what steps they took to stop their products being intercepted during shipping for installation of malware implants.
That's why this kind of innuendo is unhelpful at best. What matters is what we can verify. Does Cisco allow customers to inspect code? How much does it invest in security hardening? Why do we keep seeing hard coded backdoors in their products, and why haven't they systematically gone through every line and removed them yet?
Perhaps it's because stuff that perpetuates myths and stereotypes about LGBTQ people actually harms them in their daily lives, where as blasphemy just annoys a few people who secretly love the opportunity to write and angry letter to the local paper.
It used to be a common exercise when learning C to demonstrate an understanding of strings and pointers and the standard libraries. It reveals some interesting things about the programmer, e.g. if they try to treat the string as an array or if they use a char* pointer, if they use const modifiers in their function definition, and if they do things like set a maximum string length and what the code does if the string exceeds it.
The exact same argument can be applied to the US. We should cut ties because the NSA hacks the planet, the US wages stupid trade wars with us and tries to make us pay for its own shit. It abuses its own citizens, especially if they are poor or black, it has secret black site prisons and openly tortures people it calls terrorists. The current leader lost the last election and is still in power!
Yeah, let's boycott the US, I'm sure that will encourage the people to rise up and change the regime.
I'll do basic programming if that's what you want, but you still have to pay me the same rate as if I was doing the advanced stuff. Hardcore C/C++ skills, especially on the embedded side, are getting extremely valuable these days.
That's how it should be. You have to have a little bit of faith that you can detect when the candidate is trying to BS you, and if you screw up badly enough to let a bad one in anyway that's what the probation period is for.
It's arthritis, and not the kind you get from old age. Thanks for trying to diagnose me over the internet though, obviously I never bothered to see an actual doctor about it.
Nooo, you shouldn't be using ints and chars for embedded! Always use intX_t that states the width explicitly.
Embedded is hard because to do anything decent you have to really understand the hardware. Not just the CPU, the whole system. You don't get any memory protection, exceptions crash the whole thing, and you have to handle your own interrupts. Oh, and your code needs to run perfectly for years without stopping or running out of memory, and in some cases needs to survive external problems like supply fluctuations or a temporarily broken clock.
And that's before you do any useful work which often requires you to have a good understanding of things like digital sampling theory.
Don't get me wrong, higher level stuff is great, but it's also a hell of a lot easier than embedded. That's why I get the big bucks.
That's why you discuss the code. You ask them why they wanted to show you that bit, why it is interesting or impressive, and why they designed it that way.
Jesus went against the grain of society, stoop up for the oppressed, advocated equality and social justice for all, disliked the 1%... He even sent himself death threats and his followers have a near-religious fervour. Eventually conservatives got fed up with his BS and constantly claiming to be the victim - "waaah thy nailed me to a cross waaah!" Suck it up, Jesus.
My guess is it's an experiment to see if they can get rid of the on-screen buttons entirely. It will doubtless be an option, just like you can change the order of the current buttons or disable them on phones with hardware ones.
Like say you are watching a full screen video, at the moment you have to tap once to bring up the buttons and then again on the button. With a gesture you could just swipe where the button would be, similar to how iOS handles the home/switch gesture.
Slashdot Mirror
Did you think we wouldn't check your links? The second one points out that Cisco didn't win, they dropped their legal action. Later it emerged that they had been complaining about some generic C header files that were likely part of the compiler suite anyway, not even Cisco code.
This isn't the first time you have made this bogus claim either. So the question is, why do you keep doing it? Do you still have some loyalty to Cisco, or is someone paying you to do it, or is this a hacked account now controlled by some NSA staffer?
I never meant to imply that the UK was better. My point was that it's the pot calling the kettle black, and none of the involved parties have the moral high ground here.
TFA is designed to teach people how to think about the lifecycle emissions of things, and how to decide if they are beneficial or not. If you calm down a bit and read it in the light it was intended, it's a reasonable article.
My advice is always get it checked. Otherwise you find out one day you have been living with some undiagnosed problem for 30 years and didn't have to suffer the whole time.
There is no test for RA, it's a bit like Lupus - the diagnosis is that you have some subset of the known symptoms and have ruled out everything else.
It's unlikely that you have it if you don't also have at least some of the other stuff, like the vision problems, and of course the thing that differentiates it from other auto-immune problems: that it gets worse when you get an infection.
It's primarily aimed at developers, especially web devs who want to run a Linux based stack for local testing. Also great if you want to do cross-development for a Linux target.
Why not use a VM? WSL consumes far fewer resources, and makes it easier to share files between the two sides with native performance.
One use case WSL works well for is cross compilation using a Linux based toolchain. Similarly when building .NET based software you can compile and test Linux binaries using Mono without the hassle of a VM.
Clearly the desire to have all this stuff has been there for many years, hence the existence of CygWin and several others.
The GP is correct, uranium dust particles are dangerous. If they get in your lungs then your clothes or a sheet of paper won't help you. Note that your lungs are not normally exposed to sunlight either.
That's the problem here. They had buckets of the stuff lying around, one without the lid even on it. Properly handled it can be safe, but it wasn't properly handled.
What all the parent posters and XKCD are missing is that it's not just the dosage, it's the manner of exposure. Temporary exposure to an xray machine stops the moment the machine is turned off. A bucket of uranium specimens may contain dust that can get inside the body. Thus it needs to be handled carefully to avoid that, and in this case it appears that the staff had little idea of what they were doing.
It's the old "banana equivalent dose" fallacy. The body processes and removes excess potassium, but caesium accumulates in certain organs and does long term damage, with the effects only becoming apparent years later.
I detect some unhappiness among Trump supporters of late, because they are busy filing their taxes right now. That promised tax cut, the one that the 1% had a year ago and was due to reach them around now, hasn't materialized. In fact they are paying more tax now, and the realization that they have screwed is finally having an effect.
Strangely I don't see interviews with Cisco CEOs asking them about the level of cooperation with the NSA or what steps they took to stop their products being intercepted during shipping for installation of malware implants.
That's why this kind of innuendo is unhelpful at best. What matters is what we can verify. Does Cisco allow customers to inspect code? How much does it invest in security hardening? Why do we keep seeing hard coded backdoors in their products, and why haven't they systematically gone through every line and removed them yet?
Those are the questions that matter.
Try googling "reactive arthritis".
Every screenshot I've seen doesn't look like it re-renders. Do you have one to demonstrate?
Perhaps it's because stuff that perpetuates myths and stereotypes about LGBTQ people actually harms them in their daily lives, where as blasphemy just annoys a few people who secretly love the opportunity to write and angry letter to the local paper.
It used to be a common exercise when learning C to demonstrate an understanding of strings and pointers and the standard libraries. It reveals some interesting things about the programmer, e.g. if they try to treat the string as an array or if they use a char* pointer, if they use const modifiers in their function definition, and if they do things like set a maximum string length and what the code does if the string exceeds it.
The exact same argument can be applied to the US. We should cut ties because the NSA hacks the planet, the US wages stupid trade wars with us and tries to make us pay for its own shit. It abuses its own citizens, especially if they are poor or black, it has secret black site prisons and openly tortures people it calls terrorists. The current leader lost the last election and is still in power!
Yeah, let's boycott the US, I'm sure that will encourage the people to rise up and change the regime.
I'll do basic programming if that's what you want, but you still have to pay me the same rate as if I was doing the advanced stuff. Hardcore C/C++ skills, especially on the embedded side, are getting extremely valuable these days.
That's how it should be. You have to have a little bit of faith that you can detect when the candidate is trying to BS you, and if you screw up badly enough to let a bad one in anyway that's what the probation period is for.
Thanks. Unfortunately I was diagnosed rather late and a lot of damage was already done, so now I'm super careful not to make it any worse.
It's arthritis, and not the kind you get from old age. Thanks for trying to diagnose me over the internet though, obviously I never bothered to see an actual doctor about it.
Nooo, you shouldn't be using ints and chars for embedded! Always use intX_t that states the width explicitly.
Embedded is hard because to do anything decent you have to really understand the hardware. Not just the CPU, the whole system. You don't get any memory protection, exceptions crash the whole thing, and you have to handle your own interrupts. Oh, and your code needs to run perfectly for years without stopping or running out of memory, and in some cases needs to survive external problems like supply fluctuations or a temporarily broken clock.
And that's before you do any useful work which often requires you to have a good understanding of things like digital sampling theory.
Don't get me wrong, higher level stuff is great, but it's also a hell of a lot easier than embedded. That's why I get the big bucks.
That's why you discuss the code. You ask them why they wanted to show you that bit, why it is interesting or impressive, and why they designed it that way.
Jesus went against the grain of society, stoop up for the oppressed, advocated equality and social justice for all, disliked the 1%... He even sent himself death threats and his followers have a near-religious fervour. Eventually conservatives got fed up with his BS and constantly claiming to be the victim - "waaah thy nailed me to a cross waaah!" Suck it up, Jesus.
Sounds like an SJW to me.
The Norse myths are great. I recommend Neil Gaiman's take on them, especially the recent BBC adaptation.
My guess is it's an experiment to see if they can get rid of the on-screen buttons entirely. It will doubtless be an option, just like you can change the order of the current buttons or disable them on phones with hardware ones.
Like say you are watching a full screen video, at the moment you have to tap once to bring up the buttons and then again on the button. With a gesture you could just swipe where the button would be, similar to how iOS handles the home/switch gesture.