Also, applets run on the JVM just like applications do. The only difference is that the JVM is invoked by the browser (you can think of the JVM running inside the browser, but this isn't really true these days). So, his question is perfectly valid - does Jazilla start a JVM (to run applets you're browsing to)that runs on the JVM the browser itself is running on? Or does is start a seperate JVM? Good question - although I bet I can guess the answer...
> So how does IIS come out so crappy when it
> comes to security?
Simple. It's because IIS is a much larger product. It does so many more things than Apache it's not even funny. When you have more lines of code, you have more bugs. When you have more bugs, you have more security holes. IIS has tons more lines of code -> IIS has tons more security holes.
If you'll look at all of the IIS exploits, you will find that most of them (and I mean > 90%) are in very seldom used extensions/code sections (known as ISAPIs in IIS-speak). Apache does not have these components. If the support for a particular feature is not present in Apache, there cannot be security holes in it. Since there are thousands of lines present in these IIS components, there are bound to be security bugs.
Saying that IIS is more secure that Apache is not a fair comparision.
It's really that simple.
Completely wrong.
A company can most certainly record its employees' conversations! It must inform than that it will do so, but such practices as "by using our phones you are hereby consenting to monitoring" are completely legal.
Ahhh..actually this "something" was setup to allow universities to communicate amongst themselves. This whole "everyone uses the Internet for freedom and happiness" stuff came much later.
...this isn't a problem. Once you have the solution for a problem, writing the code for it is straightforward. If you're working on a large problem (or any even somewhat complex problem), you need to DESIGN your solution first. This means making flow charts, diagrams, and assorted things. Then, you need to create pseudocode for the project (most of the time...if you have done the design stage well enough, this usually isn't necessaey). Once you have a design like that, the code should be straightforward in ANY language.
Coding is not THAT difficult. It's the design that is. Once you've figured out the problem and its solution, you're 9/10 of the way there. Coding it up is the EASY part.
Slashdot Mirror
Oops...that should read Java programs = Java applets + Java applications
Actually Java applets are programs - they are just programs that run inside of a web browser as opposed to on their own.
;)
Java applications != Java applets
Java applications = Java applets + Java applications
I think you're confusing them.
Also, applets run on the JVM just like applications do. The only difference is that the JVM is invoked by the browser (you can think of the JVM running inside the browser, but this isn't really true these days). So, his question is perfectly valid - does Jazilla start a JVM (to run applets you're browsing to)that runs on the JVM the browser itself is running on? Or does is start a seperate JVM? Good question - although I bet I can guess the answer...
> So how does IIS come out so crappy when it > comes to security? Simple. It's because IIS is a much larger product. It does so many more things than Apache it's not even funny. When you have more lines of code, you have more bugs. When you have more bugs, you have more security holes. IIS has tons more lines of code -> IIS has tons more security holes. If you'll look at all of the IIS exploits, you will find that most of them (and I mean > 90%) are in very seldom used extensions/code sections (known as ISAPIs in IIS-speak). Apache does not have these components. If the support for a particular feature is not present in Apache, there cannot be security holes in it. Since there are thousands of lines present in these IIS components, there are bound to be security bugs. Saying that IIS is more secure that Apache is not a fair comparision. It's really that simple.
Completely wrong. A company can most certainly record its employees' conversations! It must inform than that it will do so, but such practices as "by using our phones you are hereby consenting to monitoring" are completely legal.
That's not a problem - just use the Google cache to find it!
Ahhh..actually this "something" was setup to allow universities to communicate amongst themselves. This whole "everyone uses the Internet for freedom and happiness" stuff came much later.
...this isn't a problem. Once you have the solution for a problem, writing the code for it is straightforward. If you're working on a large problem (or any even somewhat complex problem), you need to DESIGN your solution first. This means making flow charts, diagrams, and assorted things. Then, you need to create pseudocode for the project (most of the time...if you have done the design stage well enough, this usually isn't necessaey). Once you have a design like that, the code should be straightforward in ANY language. Coding is not THAT difficult. It's the design that is. Once you've figured out the problem and its solution, you're 9/10 of the way there. Coding it up is the EASY part.
(1) Perl is interpreted. This is slow because, at runtime, the Perl engine/interpreter must parse the text of the program code.
(2) Visual Basic is first compiled into p-code (intermediate langauge). This is much faster because all of the text parsing is done prior to runtime.
As text parsing is the SLOWEST part of interpreted langugae, this is why ASP/VB offers a significant performance boost from CGI/Perl.