All web applications are partly written in C. Your link was deficient because it didn't include web applications, which is where most of the code written today actually is. Furthermore, you haven't actually tried to exploit those. A single buffer overflow can't be exploited on a modern system, it takes more vulnerabilities than that.
If you can't keep track of your memory, how are you going to write secure code?
Security? Invalid memory accesses are too hard to exploit these days with things like ASLR and other kernel protections. They can still be exploited but it's not nearly as easy as it used to be. If you want to use C and still be safe, you can create an API for dealing with memory chunks.
The most common types of vulnerabilities these days are things like SQL (or noSQL) injection, and XSS. Invalid memory access doesn't even make the top 10, but of course you already know that.
They can tell things like when people stop reading in their Kindle, but they don't have really great data to determine why the person stopped reading. They may be able to tell how long popular dialogues are, but an interesting dialogue is determined by much more than length. In fact you might say that length is one of the least important factors.
So great, they have tons of metrics, but they don't have the ability to extract the metrics they need to make a book interesting. And that is entirely the problem.
It essentially solved all the problems. People who think JavaScript automatically solves memory leak issues are ignorant and need to be educated because their code inevitably sucks.
You are not that smart. I'm not insulting you, I'm just telling you the truth, and the truth to every C and C++ programmer sitting here smirking about how they can write solid C code. No, you can't.
It's not about smartness, it's about knowledge. Knowing what you are doing. I worked at a company that was a mix of C and Javascript programmers, and monitored memory leaks in production. The C code had zero memory leaks, and the Javascript code bloated quickly over time until the product was unusable in the browser.
How did the C programmers avoid memory leaks? It wasn't because of their skill: many were recent graduates right out of college. The system was set up correctly because one of the lead programmers knew what to do (basically he built a memory library that set things up to easily avoid memory leaks).
It's possible to write secure C, but people don't do it because they don't know how.
If you support leaking when it hurts the other party but not your own party, you are the problem. Fix your own party so you don't have to worry about leaking (and personally I'd be happy if both parties collapse. They don't represent the majority of the people, anyway).
For example, our planes had difficulty during the early phases of the Vietnam war because it was felt that air-to-air missiles would render dogfights obsolete, and our planes were designed with this assumption in mind
Note this is also the assumption of the F-35 design.
Myth Busters made a copy of a real fingerprint. These guys generated an image of a fingerprint that was close enough to unlock the phone.....without knowing what the original fingerprint looked like.
That's why they call it the "master key" fingerprint....because it can unlock the phone like a ghost key. They used the adversarial neural network to find weaknesses in the fingerprint identification algorithm. Basically, some features of fingerprints are more common than others.
The only reason I even lock my phone is because I don't want to pocket-dial anyone (or press other random buttons in my pocket). I don't lock my wallet, either.
In this case the uncertainty is rather high. We just don't know how AGW will affect hurricanes. If you think scientists know how AGW will affect hurricanes, you should read the paper. In fact, you should read the paper anyway, like a grown up.
The most common vulnerabilities right now are SQL injections and xss-type attacks. Buffer overflows are difficult to exploit these days because of all the kernel protections. Oh and what is the biggest worm right now? Mirai, which spreads by using the default password for devices. It doesn't matter what language you are using that will still be a problem.
Ha. Now you have the information, what are you going to do with it? Looks like you will ignore it because it doesn't fit your biases. The paper goes into great detail about the many uncertainties.
Keep reading down the thread, and you will see that I quoted directly from the paper so that even lazy people like you can understand (too lazy to read the paper).
Slashdot Mirror
All web applications are partly written in C. Your link was deficient because it didn't include web applications, which is where most of the code written today actually is. Furthermore, you haven't actually tried to exploit those. A single buffer overflow can't be exploited on a modern system, it takes more vulnerabilities than that.
Which industry? "Stealing from ATMs" industry? I hear it's profitable.
Telomere regeneration happens naturally in the body, with telomerase.
Top 10
If you can't keep track of your memory, how are you going to write secure code?
Security? Invalid memory accesses are too hard to exploit these days with things like ASLR and other kernel protections. They can still be exploited but it's not nearly as easy as it used to be. If you want to use C and still be safe, you can create an API for dealing with memory chunks.
The most common types of vulnerabilities these days are things like SQL (or noSQL) injection, and XSS. Invalid memory access doesn't even make the top 10, but of course you already know that.
"advertising allows us to provide, support, and improve some of our products"
He seems extremely confused about the definition of the word "improve."
They can tell things like when people stop reading in their Kindle, but they don't have really great data to determine why the person stopped reading. They may be able to tell how long popular dialogues are, but an interesting dialogue is determined by much more than length. In fact you might say that length is one of the least important factors.
So great, they have tons of metrics, but they don't have the ability to extract the metrics they need to make a book interesting. And that is entirely the problem.
It essentially solved all the problems. People who think JavaScript automatically solves memory leak issues are ignorant and need to be educated because their code inevitably sucks.
People don't always vote for the party that represents them.
It makes sense still to have a pilot because larger countries have the capability to jam GPS and other wireless signals.
You are not that smart. I'm not insulting you, I'm just telling you the truth, and the truth to every C and C++ programmer sitting here smirking about how they can write solid C code. No, you can't.
It's not about smartness, it's about knowledge. Knowing what you are doing. I worked at a company that was a mix of C and Javascript programmers, and monitored memory leaks in production. The C code had zero memory leaks, and the Javascript code bloated quickly over time until the product was unusable in the browser.
How did the C programmers avoid memory leaks? It wasn't because of their skill: many were recent graduates right out of college. The system was set up correctly because one of the lead programmers knew what to do (basically he built a memory library that set things up to easily avoid memory leaks).
It's possible to write secure C, but people don't do it because they don't know how.
If you support leaking when it hurts the other party but not your own party, you are the problem. Fix your own party so you don't have to worry about leaking (and personally I'd be happy if both parties collapse. They don't represent the majority of the people, anyway).
They don't have a clear way to do it. If they did, they would have already done it, instead of doing nothing but making noise for the past two years.
For example, our planes had difficulty during the early phases of the Vietnam war because it was felt that air-to-air missiles would render dogfights obsolete, and our planes were designed with this assumption in mind
Note this is also the assumption of the F-35 design.
Myth Busters...
Myth Busters made a copy of a real fingerprint. These guys generated an image of a fingerprint that was close enough to unlock the phone.....without knowing what the original fingerprint looked like.
That's why they call it the "master key" fingerprint....because it can unlock the phone like a ghost key. They used the adversarial neural network to find weaknesses in the fingerprint identification algorithm. Basically, some features of fingerprints are more common than others.
The only reason I even lock my phone is because I don't want to pocket-dial anyone (or press other random buttons in my pocket). I don't lock my wallet, either.
In this case the uncertainty is rather high. We just don't know how AGW will affect hurricanes. If you think scientists know how AGW will affect hurricanes, you should read the paper. In fact, you should read the paper anyway, like a grown up.
Perl 6 is better. In Perl 6 even grammars are great and easy to use.
The most common vulnerabilities right now are SQL injections and xss-type attacks. Buffer overflows are difficult to exploit these days because of all the kernel protections. Oh and what is the biggest worm right now? Mirai, which spreads by using the default password for devices. It doesn't matter what language you are using that will still be a problem.
You must not talk to many poor people. You privileged fuck.
At the moment Patreon is showing it's possible for a large number of sites besides Wikipedia.
Ha. Now you have the information, what are you going to do with it? Looks like you will ignore it because it doesn't fit your biases. The paper goes into great detail about the many uncertainties.
Since he spied on his users, he is worried that Apple will spy on him (and his executives). After all, he would do it in Tim Cook's position.
Keep reading down the thread, and you will see that I quoted directly from the paper so that even lazy people like you can understand (too lazy to read the paper).
Poor people complain about taxes, too.