Digital is already a special case of analog. That is why clock speeds have limits and trace runs must be laid out by someone with a firm understanding of analog. Crosstalk etc. are a thing with digital components.
I have no idea where you got that idea, but in general any such generalization / assumption will be wrong. Nobody is OK with performance slowdowns, especially when the degree of performance degradation is an unknown.
Intel is guilty of attempting to undermine national security and whomever attempted this bullshit should be charged accordingly. Every qualified security expert should look carefully at this code and publish their findings post haste.
If it's code that never executes it won't be there after the compiler gets through with it without explicit pragmas that advertise the fact that said segment of code is a red herring.
I came here to say essentially the same thing. This also clearly assumes proprietary software as this literally can't be done with open source, which is one more advantage of FOSS.
You don't really understand how life works apparently. Did it ever occur to you that they and the bank both agreed they could afford it when the loan was taken, but that circumstances change? People get ill. The economy takes a serious downturn. A great job goes away and one can't find another that pays as well. Seriously, are you a teenager or a troll?
Sorry to burst your bubble but, yes, it is always true. Nice clean well tested code in BASIC has all the problems inherent to BASIC, including but not limited to code reuse and maintanence nightmares. If you really were a competent developer you would know this already.
Actually it is quite literally the only reason, which is why if the glitch didn't happen they would not have been subjected to the foreclosure and that is literally the story.
Found at least one guy that knows nothing about surfing but gets snarky as if he actually knows what he is talking about. (Yes, a child and a very large man can use the same board)
I agree 100%. My point was that at least there is a chance that the C# guy will be a skilled professional, while zero skilled professionals would ever choose BASIC. For bonus points to the readers, what does the first letter of BASIC? (Note: BASIC was the first language I learned and it is useful for that purpose but in 2018 there is no reason to learn it as we have Python now.)
Um... No. He doesn't like it but believes rightly so that it is a thing that isn't going away. He believes one standard devil is better than hundreds of competing ones. So, no, you can't call him a proponent, just a pragmatist.
Well you couldn't even write a single line of psuedocode in your subject line, trying to assign rather than compare ( = != == ) so you are right in your case at least.
Yeah. I should have said "in general". Oh, look, I did and you just "forgot" to boldface that part of my statement.
Very good. You just restated the content of the story. Here's your sign ...
How is "he right" when he said something completely different from what you just wrote?
Keep trying.
Debian would be distributing the patch. It would be redistribution if the Debian user ... wait for it ... redistributed it.
Buying AMD doesn't mitigate the issue for already purchased and deployed hardware. The two aren't mutually exclusive.
Digital is already a special case of analog. That is why clock speeds have limits and trace runs must be laid out by someone with a firm understanding of analog. Crosstalk etc. are a thing with digital components.
I have no idea where you got that idea, but in general any such generalization / assumption will be wrong. Nobody is OK with performance slowdowns, especially when the degree of performance degradation is an unknown.
Yeah ... That's way more funny. DOH!
Intel is guilty of attempting to undermine national security and whomever attempted this bullshit should be charged accordingly. Every qualified security expert should look carefully at this code and publish their findings post haste.
You actually began the sentence that way, not ended it that way ... Idiot.
If it's code that never executes it won't be there after the compiler gets through with it without explicit pragmas that advertise the fact that said segment of code is a red herring.
I came here to say essentially the same thing. This also clearly assumes proprietary software as this literally can't be done with open source, which is one more advantage of FOSS.
We are discussing BASIC. You are trying to change the subject. You are not talking about BASIC. Off you go now ....
You don't really understand how life works apparently. Did it ever occur to you that they and the bank both agreed they could afford it when the loan was taken, but that circumstances change? People get ill. The economy takes a serious downturn. A great job goes away and one can't find another that pays as well. Seriously, are you a teenager or a troll?
Sorry to burst your bubble but, yes, it is always true. Nice clean well tested code in BASIC has all the problems inherent to BASIC, including but not limited to code reuse and maintanence nightmares. If you really were a competent developer you would know this already.
Actually it is quite literally the only reason, which is why if the glitch didn't happen they would not have been subjected to the foreclosure and that is literally the story.
Found at least one guy that knows nothing about surfing but gets snarky as if he actually knows what he is talking about. (Yes, a child and a very large man can use the same board)
I agree 100%. My point was that at least there is a chance that the C# guy will be a skilled professional, while zero skilled professionals would ever choose BASIC. For bonus points to the readers, what does the first letter of BASIC? (Note: BASIC was the first language I learned and it is useful for that purpose but in 2018 there is no reason to learn it as we have Python now.)
Well, to start with, the BASIC code will be written by an amateur, not a highly skilled developer.
Um ... No. He doesn't like it but believes rightly so that it is a thing that isn't going away. He believes one standard devil is better than hundreds of competing ones. So, no, you can't call him a proponent, just a pragmatist.
Well you couldn't even write a single line of psuedocode in your subject line, trying to assign rather than compare ( = != == ) so you are right in your case at least.
What did they say when you brought the error to their attention?
It's like you *want* to appear stupid in front of as many people as possible. Possibility you are Donald Trump confirmed.
That is true, which is why Python doesn't have idiotic rules about whitespace.