And the world you are living in has very few idiots who would allow this to happen? Lucky you, nice of you to visit, perhaps you should return to your world soon - it's not safe here.
And in the world where I am living, most software is written in C, and will remain so for decades no matter what. It's much easier to get rid of frauds that pretend to be programmers than to get rid of C so aforementioned frauds will write bugs that you deem to be less dangerous. So don't even try this crap -- status quo is not on your side.
So I'm saying with the same level of programmer and one who is not really crap, you won't have SQL injections with Java (you used Java as an example), but you will still have remote exploits with a C program doing the same thing.
No. Programmers you are describing are all crap, and the value of their work is zero or negative. Programmer who won't produce code that allows SQL injection, will also produce code with no buffer overflows in C and vice versa. Programmers who will make such mistakes, will also mess up algorithms and data structures, producing all kinds of problems that you wouldn't notice because you are so concentrated on common exploitable bugs. The problem is, there are too many crappy programmers, and their mistakes -- be it buffer overflow or SQL injections, or anything else -- have the same real-world impact regardless of the language they use.
If you are saying the only programmers who should be be allowed to program will never have remote arbitrary execution exploits when writing stuff like webservers, SSH servers, DNS servers, DHCP servers, mail servers using C then there must be very few people in the world who can write programs in C.
No, I am saying that there are plenty of programmers who don't make idiotic mistakes, just like there are plenty of electrical and mechanical engineers who don't make idiotic mistakes. The problem is, idiots are not allowed to do electrical and mechanical engineering, however there is nothing preventing them from becoming programmers. Naturally, hordes of idiots work as programmers, shitting up the whole industry for everyone else because one such idiot spoils work of everyone else on the same project.
Using C is like driving a manual car without a clutch. It can be done if you are careful and skilled. But only a few people in the world can do it and keep doing it without making mistakes.
No. This is one of the situations that are described as "If this helps you, you are not qualified". Crutches for a marathon runner, bicycle training wheels for a motorcycle rider, a horse pulling a truck, etc. A programmer who studied C properly, and not through a crash course or online "tutorials", would not be able to make a mistake that causes a buffer overflow, except when writing under conditions when no one should be writing software (drunk, extremely tired, etc.). It's in the core understanding of the language. It's not possible to separate from a way a programmer thinks. There is nothing "easy" or "difficult" about it, a programmer can't "forget" or "avoid" thinking about it because there is no separation between buffer handling and the design of data structures that buffers are a part of. A programmer for whom it is not so (you, for example), does not know C, and should not talk about it, leave alone try to write in it.
They will make different mistakes and probably stupider mistakes, but they are far less likely to destroy their car transmission in 5 minutes.
This is a stupid analogy. Programmers don't use a product, they develop it. Design flaws are only tolerable if they make product worse, not cause it to do something terribly wrong -- any engineer, including automotive one, would tell you this. Just because some people are accustomed to abysmal quality of software, it does not make it acceptable.
Just go look at the number of remote vulnerabilities in services/servers written in C.
And it takes an idiot to allow this to happen.
Yes you can have sql injection if the programmer is really crap, but with C you'd have sql injection as well as exploitable buffer overflows etc.
It takes MORE crappy programmer to allow buffer overflow than SQL injection -- and SQL injection bugs are way too common. You are talking about programmers who should never be allowed to program anything in the first place, therefore all your points are invalid.
UNIX is better than Windows. But it isn't that wonderful. C might be preferable to Pascal, but it isn't that great either.
C and UNIX are the "Worse is Better" approach:
It's called "engineering".
after UNIX there was Plan9:
After developing C and Unix, Dennis Ritchie was responsible for two failed attempts to improve things that he and other Unix developers earlier worked on -- one to improve Unix itself (STREAMS that became a part of System V), another to produce an OS better than Unix (Plan 9). Both are currently recognized as failures -- literally no one uses them other than people who given themselves a specific goal to use those things. I would compare their popularity to Mono, but Mono has a distinction of being a stupid, purposeless design, while Ritchie merely failed to provide any clear benefit over things that already existed, even though core ideas were sound.
Unix (as in, a collection of all Unix-like systems because they share most of things that matters) is still the best general-purpose OS. It will likely remain so for at least half a century starting from the moment when all software developed by Microsoft will be out of widespread use (as presence of Microsoft holds up progress in OS development).
C is the best "non-flavored" language (as in, not specifically designed to follow some ideology or narrowly defined purpose such as OO, functional, for simple scripting, database access or designed for mentally deficient people), and is likely to remain so for at least as long.
Maybe stuff would only start happening 10 years later but we might have a lot fewer stupid "buffer overflows" and "exploits".
This is bullshit, and you are an idiot for repeating it. The amount of mistakes a programmer makes per amount of logic/functionality implemented, is constant for every programmer. Shitty programmers writing in C make one type of bugs, shitty programmers writing in Java make different kinds of bugs, impact of those bugs is exactly the same, however shitty programmers writing in Java, write faster and therefore more functionality and more bugs per amount of time.
Near-fleet GPS jamming has nothing to do with ship navigation. Navies have been navigating ships without GPS for several hundred years. GPS jamming is to decoy incoming missiles which use GPS as ONE OF the methods of target location.
Why would American missiles be attacking American ships?
No one is stupid enough to rely on GPS operated by the enemy while attacking that enemy.
No, I mean that a corporate whore asshat has no oversight over his whoring and asshatery. My political views are quite irrelevant in face of this blatant betrayal of public trust into UN-affiliated institutions.
Hacks and tweaks, as in little special cases everywhere "to make interactive tasks look faster", "to make services run faster", "to find identical DLLs loaded from different files", etc. -- all fixes for overall deficient design, none of them of any use for the user.
A surgeon who will recommend to operate when it's not necessary, will lose his license, can be sued for malpractice and may even face criminal charges if he knew that he endangers a patient without a good reason for it.
This asshat, on the other hand, has no oversight over his whoring to corporations, and should never be placed into any such position.
No, he was talking about potato queues. They looked exactly like WWII-time bread lines, but were a fundamentally different thing. Potatoes are easy to store (city apartment buildings even had underground storage space specifically allocated for that), and farmers often sold them at a massive discount when they had surplus after the harvest. Regular grocery stores or farmers' markets didn't have the capacity for this, so usually there will be a potato truck outside a grocery store, with a long line of people buying.
I live in US, and I would rather prefer "queuing for potatoes" (once a year, after the harvest, potatoes are available at a huge discount) and "strict censorship" (so if a journalist actually manages to get something government-related published, government WILL HAVE TO answer in a public manner or fix the perceived problem).
3.4. Network Subscriber is prohibited to: 3.4.1. Use Network Subscriber Equipment for purposes other than personal, family, home, orfor other purposes related to running a business. 3.4.2. Retransmit, perform (copy), or use radio and TV programs in any other manner (except for personal, noncommercial use by Subscriber). 3.4.3. Perform other actions listed in Part 6 "Subscriber's Rights and Obligations". 3.4.4. Use Services to transmit voice over the data networks, including transmission over the Internet, i.e. Subscriber is prohibited from using software such as Skype and similar, to transmit voice over the Internet.
You know absolutely nothing about Socialism, or its implementation in USSR. Everything you think, you know, originates from propaganda that was made to protect interests of corporations -- same corporations that would be destroyed under any economic system other than dysfunctional Capitalism as practiced in post-WWII US.
Slashdot Mirror
And the world you are living in has very few idiots who would allow this to happen? Lucky you, nice of you to visit, perhaps you should return to your world soon - it's not safe here.
And in the world where I am living, most software is written in C, and will remain so for decades no matter what. It's much easier to get rid of frauds that pretend to be programmers than to get rid of C so aforementioned frauds will write bugs that you deem to be less dangerous. So don't even try this crap -- status quo is not on your side.
So I'm saying with the same level of programmer and one who is not really crap, you won't have SQL injections with Java (you used Java as an example), but you will still have remote exploits with a C program doing the same thing.
No. Programmers you are describing are all crap, and the value of their work is zero or negative. Programmer who won't produce code that allows SQL injection, will also produce code with no buffer overflows in C and vice versa. Programmers who will make such mistakes, will also mess up algorithms and data structures, producing all kinds of problems that you wouldn't notice because you are so concentrated on common exploitable bugs. The problem is, there are too many crappy programmers, and their mistakes -- be it buffer overflow or SQL injections, or anything else -- have the same real-world impact regardless of the language they use.
If you are saying the only programmers who should be be allowed to program will never have remote arbitrary execution exploits when writing stuff like webservers, SSH servers, DNS servers, DHCP servers, mail servers using C then there must be very few people in the world who can write programs in C.
No, I am saying that there are plenty of programmers who don't make idiotic mistakes, just like there are plenty of electrical and mechanical engineers who don't make idiotic mistakes. The problem is, idiots are not allowed to do electrical and mechanical engineering, however there is nothing preventing them from becoming programmers. Naturally, hordes of idiots work as programmers, shitting up the whole industry for everyone else because one such idiot spoils work of everyone else on the same project.
Using C is like driving a manual car without a clutch. It can be done if you are careful and skilled. But only a few people in the world can do it and keep doing it without making mistakes.
No. This is one of the situations that are described as "If this helps you, you are not qualified". Crutches for a marathon runner, bicycle training wheels for a motorcycle rider, a horse pulling a truck, etc. A programmer who studied C properly, and not through a crash course or online "tutorials", would not be able to make a mistake that causes a buffer overflow, except when writing under conditions when no one should be writing software (drunk, extremely tired, etc.). It's in the core understanding of the language. It's not possible to separate from a way a programmer thinks. There is nothing "easy" or "difficult" about it, a programmer can't "forget" or "avoid" thinking about it because there is no separation between buffer handling and the design of data structures that buffers are a part of. A programmer for whom it is not so (you, for example), does not know C, and should not talk about it, leave alone try to write in it.
They will make different mistakes and probably stupider mistakes, but they are far less likely to destroy their car transmission in 5 minutes.
This is a stupid analogy. Programmers don't use a product, they develop it. Design flaws are only tolerable if they make product worse, not cause it to do something terribly wrong -- any engineer, including automotive one, would tell you this. Just because some people are accustomed to abysmal quality of software, it does not make it acceptable.
Just go look at the number of remote vulnerabilities in services/servers written in C.
And it takes an idiot to allow this to happen.
Yes you can have sql injection if the programmer is really crap, but with C you'd have sql injection as well as exploitable buffer overflows etc.
It takes MORE crappy programmer to allow buffer overflow than SQL injection -- and SQL injection bugs are way too common. You are talking about programmers who should never be allowed to program anything in the first place, therefore all your points are invalid.
UNIX is better than Windows. But it isn't that wonderful. C might be preferable to Pascal, but it isn't that great either.
C and UNIX are the "Worse is Better" approach:
It's called "engineering".
after UNIX there was Plan9:
After developing C and Unix, Dennis Ritchie was responsible for two failed attempts to improve things that he and other Unix developers earlier worked on -- one to improve Unix itself (STREAMS that became a part of System V), another to produce an OS better than Unix (Plan 9). Both are currently recognized as failures -- literally no one uses them other than people who given themselves a specific goal to use those things. I would compare their popularity to Mono, but Mono has a distinction of being a stupid, purposeless design, while Ritchie merely failed to provide any clear benefit over things that already existed, even though core ideas were sound.
Unix (as in, a collection of all Unix-like systems because they share most of things that matters) is still the best general-purpose OS. It will likely remain so for at least half a century starting from the moment when all software developed by Microsoft will be out of widespread use (as presence of Microsoft holds up progress in OS development).
C is the best "non-flavored" language (as in, not specifically designed to follow some ideology or narrowly defined purpose such as OO, functional, for simple scripting, database access or designed for mentally deficient people), and is likely to remain so for at least as long.
Maybe stuff would only start happening 10 years later but we might have a lot fewer stupid "buffer overflows" and "exploits".
This is bullshit, and you are an idiot for repeating it. The amount of mistakes a programmer makes per amount of logic/functionality implemented, is constant for every programmer. Shitty programmers writing in C make one type of bugs, shitty programmers writing in Java make different kinds of bugs, impact of those bugs is exactly the same, however shitty programmers writing in Java, write faster and therefore more functionality and more bugs per amount of time.
Egyptians? Ones that now have military government, and are protesting against it again?
Thanks for explanation, dumbass!
That would only be the case if those were American missiles. Everyone else uses other means to achieve the same goal.
Near-fleet GPS jamming has nothing to do with ship navigation. Navies have been navigating ships without GPS for several hundred years. GPS jamming is to decoy incoming missiles which use GPS as ONE OF the methods of target location.
Why would American missiles be attacking American ships?
No one is stupid enough to rely on GPS operated by the enemy while attacking that enemy.
It seems familiar to you because you are stupid and ignorant, so you can only think in terms of superficial similarities.
No, I mean that a corporate whore asshat has no oversight over his whoring and asshatery. My political views are quite irrelevant in face of this blatant betrayal of public trust into UN-affiliated institutions.
Why would I not be hostile toward people who are tirelessly shitting up technology for the rest of mankind?
Are you sure, you are in the same universe as the rest of us? Lenovo produces the best non-Mac laptops.
Outside US it's called "corruption".
In US it's the only thing politicians ever did. Except Jefferson, he also did something else.
Developers, developers, developers, developers!
Developers, developers, developers, developers!
Fuck you, Windows software developers!
Hacks and tweaks, as in little special cases everywhere "to make interactive tasks look faster", "to make services run faster", "to find identical DLLs loaded from different files", etc. -- all fixes for overall deficient design, none of them of any use for the user.
At the level of blatant disregard for everything other than money demonstrated by the aforementioned asshat?
A surgeon who will recommend to operate when it's not necessary, will lose his license, can be sued for malpractice and may even face criminal charges if he knew that he endangers a patient without a good reason for it.
This asshat, on the other hand, has no oversight over his whoring to corporations, and should never be placed into any such position.
The "researcher" gives the military an easy way to "explain" the discovered breach that doesn't make military look incompetent.
Lenovo.
2100 EST on a Saturday night? What are all of you people doing reading /. now?
Seriously? Like, what? Everyone that normally reads slashdot is supposed to be out at a bar right now or something?
I am reading Slashdot in a bar, you insensitive clod!
Yes. The same days when /b/ was good, and Reagan had any positive stats other than CHA.
...instead of designing memory management and scheduler that are efficient on their own.
This is why virtual machines are so great for running Windows -- another layer of bad resource management can't make it any worse.
No, he was talking about potato queues. They looked exactly like WWII-time bread lines, but were a fundamentally different thing. Potatoes are easy to store (city apartment buildings even had underground storage space specifically allocated for that), and farmers often sold them at a massive discount when they had surplus after the harvest. Regular grocery stores or farmers' markets didn't have the capacity for this, so usually there will be a potato truck outside a grocery store, with a long line of people buying.
I live in US, and I would rather prefer "queuing for potatoes" (once a year, after the harvest, potatoes are available at a huge discount) and "strict censorship" (so if a journalist actually manages to get something government-related published, government WILL HAVE TO answer in a public manner or fix the perceived problem).
3.4. Network Subscriber is prohibited to:
3.4.1. Use Network Subscriber Equipment for purposes other than personal, family, home, orfor other purposes related to running a business.
3.4.2. Retransmit, perform (copy), or use radio and TV programs in any other manner (except for personal, noncommercial use by Subscriber).
3.4.3. Perform other actions listed in Part 6 "Subscriber's Rights and Obligations".
3.4.4. Use Services to transmit voice over the data networks, including transmission over the Internet, i.e. Subscriber is prohibited from using software such as Skype and similar, to transmit voice over the Internet.
I typically make applications/daemons on a POSIX platform, but I always prototype in .net
No, you don't.
You know absolutely nothing about Socialism, or its implementation in USSR. Everything you think, you know, originates from propaganda that was made to protect interests of corporations -- same corporations that would be destroyed under any economic system other than dysfunctional Capitalism as practiced in post-WWII US.