The JVM and.Net Framework acheive the same thing, the convert a common language to native language and run it in a (somewhat) enclosed environment. Call it an emulator, a virtual machine, a sandbox, what ever.
That definition even includes compilers. "Emulation" specifically means to program one system to *imitate* the behavior of another, with the strong implication of a loss of efficiency. Not all interpretive execution environments are emulators, or even "emulator-like". And large chunks of modern JVMs are much closer to compilers than interpreters, and need not suffer by comparison with "native" solutions performance-wise (although what exactly is "native" about C on, say, x86, escapes me at the moment).
What makes Java superior in the realms of reliability and security is that it works at a higher level of abstraction than C. This makes it possible to exclude large chunks of the state space that aren't useful, and serve only as a source of defects and vulnerabilities.
We're all duly impressed with the "tons of crap" you've "needed to complete a job". My own experience set overlaps that considerably (with the addition of Fortran, BASIC, COBOL, PL/I and APL. I've managed to avoid Notes and Delphi, so far.)
None of that qualifies you to comment on Java, of course. Today, assuming that because something wasn't coded in Java means it performs better than a Java-based solution is silly. "Higher level of control" sounds nice but doesn't mean much, unless by "higher level" you mean directly accessing memory or attached devices...which most folks would call "lower".
And I very much doubt a situation ever *demands* no cross-platform execution. Unless you work for Microsoft...:-)
Erm...the C++ programmer is only "free to fix it" if it's in his code, or code he controls. "Home-built" apps actually do call libraries and the OS too. Calling a virtual machine an "emulator-like environment" is kind of silly; modern JVMs perform dynamic optimizations that bear little resemblence to what an emulator typically does.
"A C++ app can be just as secure if coded correctly" says nothing; all cars are safe "if you drive correctly". What's "more secure" is probably more secure because it was *easier* to secure...unless extraordinary effort was applied to make it so.
And even that may not be enough, a point that is hopefully not lost on a Windows developer like yourself. Now that we know you're a.Net person the motivation for all this noise becomes a bit clearer, and my original point about "potentially malicious languages" still stands.:-)
Ignorance-based relativism doesn't really further the discussion. It's really hard for you to say anything of merit about something you don't understand.
In point of fact Java architecture contributes significantly to making it easier to write secure applications (as it also improves reliability); hand-waving that "bad stuff can happen in either language" is semantically null.
You *can* crash *any* car, but, by design, some are clearly safer than others.
It's been years, and I can't remember what specific limitations there are.
Then maybe you should consider posting only about things you actually do remeber. The set of languages that can be used for malicious resaons includes English.
By design C allows you to access memory at your own descretion. I beleive Java does also (It's been a while)
Sounds like it's not so much a matter of how *long* it's been since you had the one course in Java you were required to take to graduate, but rather how much attention you paid while you were there.
That's the theory. Of course, the FCC doesn't seem to be terribly concerned about the the impact on HF radio communications of baseband-over-powerline (BPL) systems, another "great technology for people underserved by the internet" move. BPL pilot projects are clearly not meeting even the lax technical standards set for them by the FCC, and yet there is no apparent enforcement action forthcoming, even though HF bands are shared by amateurs with military and homeland security users, and BLP systems aren't even Part 15 users, they're "unintentional radiators", an even less-privileged spectrum user. See http://www.arrl.org/bpl
So I'm not sanguine about FCC's dilgigence enforcing technical standards against a municipal WiFi system operating at less-widely used gigahertz frequencies, primarily used for amateur satellite downlinks.
The primary allocation is to amateur radio; other users are there on a Part 15 basis, which explains your experience with your neighbor's phone. You're required to accept any interference from other devices on the band. Since I hold a licence for that band, I'm a primary user, and if interfered with by a Part 15 device can require that they fix the problem or shut down.
Kel-Tec P-11's are very nice indeed. They will accept S&W standard capacity magazines (not "high capacity", please, what abolishonist nonsense!) as an reply to the size queens who claim nothing smaller than a.45 ACP is stopworthy...just load 12 rounds and where you would have shot once with a.45, shoot twice.
I used an IBM Model 30 once too. It was an IBM System/360 model 30, and had 64k. In an external chassis sold by a third party. About the size of a refrigerator.
We're hoping the same aliens who fixed Oscar 7 pay a visit to Oscar 40 soon.
Erm...yes. The club was founded in 1949. Google hits that FLA against "Proton Medical Research Center" "Parent's Music Resource Center" and "Powder Metallurgy Research Center". There's also a "Penn-Mar Radio Club" somewhere. I'd venture to guess we were the first to use "PMRC" among that crew.
Get used to it: it's 2003, the TLA namespace was saturated long ago, and the four-letter acronym space is in danger too...including "For Unlawful Carnal Knowlege".
I'm a programmer, was once married to a chemist who became a health care practioner, and we were both pilots. Driving down the road, every licence plate we saw had at least one alternative meaning.
Members of the Phil-Mont Mobile Radio Club will put their emergency communication skills to the test when they participate in "Field Day" June 28 and 29. The annual preparedness exercise brings together Amateur Radio operators from throughout North and South America who are committed to assisting their communities in the event of a natural or man-made disaster. Field Day is sponsored by the American Radio Relay League (ARRL), the national association for Amateur Radio.
"Amateur Radio is a lot of fun, but the serious side can't be stressed enough," says Maggie Leber, editor of the PMRC newsletter "The Blurb" and webmistress of the club website at www.phil-mont.org.
"We can play a vital communications role during emergencies, and events such as Field Day ensure that we're ready to handle any type of disaster. We will provide our own electrical power and operate all kinds of radio communications, everything from Morse code to amateur television and amateur satellite radio. We'll be in direct digital communications with the Montgomerty County Emergency Operations center, and will be able to transmit e-mail and other text message through facilities located there."
Field Day is designed to test operators' abilities to set up and operate stations in the field under emergency conditions, such as the loss of commercial electricity. During the weekend, radio operators try to contact as many other Field Day stations as possible, simulating the fast on-air skills needed to assist town officials and served agencies during an emergency. Approximately 35,000 Amateur Radio operators across the country participated in last year's event. The first Field Day was held in 1933.
Ham radio operators typically help with communication during weather-related emergencies such as the devastating tornadoes in the Midwest earlier this spring. But, the need for their services doesn't stop there. A federal grant awarded for emergency communications training in 2002 emphasizes support for ham radio's role in homeland defense.
PMRC will set up its Field Day stations in Lot #4 at Fort Washington State Park, and will be operating from 2pm Staurday until 2pm Sunday. "We hope that the public will come out and see firsthand what this event--and Amateur Radio--is all about," says Ms. Leber, whose amateur callsign is K3XS.
Today there are nearly 700,000 Amateur Radio operators in the United States and more than 2.5 million worldwide. Information on how to become involved in Amateur Radio is available from ARRL -- the national association for Amateur Radio, 225 Main Street, Newington, CT 06111 or by calling 1-800-32-NEW HAM. Visit ARRL on the Web at www.arrl.org.
In this case, "codewizard" is referring to the new Microsoft Access Code Wizard...
It could happen... right?
Erm...no. MSFT is achingly anxious for all these bandit Access tables to eventually end up in a SQLServer, where they will make money on them by the seat *and* by the server.
Surely any Wizard written by MSFT would be pointing the end-user in that direction. Slashdot would be the very *last* place they'd be sent.
The actual expression is "to be hoist on (or by) one's own petard". A "petard" is simply a bomb used for breaching a fortification. "Hoisting your own petard" is about as illiterate as using "for all intensive purposes" instead of "for all intents and purposes".
Sorry, but you are referring to 100LL (100 octane low-lead). There is no 110 octane. There is 80 and 100LL. 80 is green and 100LL is blue. 100LL is by far the most common, 80 is rather hard to find
Sorry, but 80/87 AvGas is *red*. *100/130* is green. 82 unleaded is purple.
Maggie K3XS, 1/10th owner C-177B N19762, who learned to fly at a tiny little field where taildraggers that drank 80/87 were common.
Slashdot Mirror
To most people "the synonym of" television is their favorite show. But that doesn't make them the same thing.
Because they US can't be trusted not to destroy it...
And the UN or the EU can? Mod parent up as Funny.
Fortunately nobody had to trust the US to *invent* the Internet.
The JVM and .Net Framework acheive the same thing, the convert a common language to native language and run it in a (somewhat) enclosed environment. Call it an emulator, a virtual machine, a sandbox, what ever.
:-)
That definition even includes compilers. "Emulation" specifically means to program one system to *imitate* the behavior of another, with the strong implication of a loss of efficiency. Not all interpretive execution environments are emulators, or even "emulator-like". And large chunks of modern JVMs are much closer to compilers than interpreters, and need not suffer by comparison with "native" solutions performance-wise (although what exactly is "native" about C on, say, x86, escapes me at the moment).
What makes Java superior in the realms of reliability and security is that it works at a higher level of abstraction than C. This makes it possible to exclude large chunks of the state space that aren't useful, and serve only as a source of defects and vulnerabilities.
We're all duly impressed with the "tons of crap" you've "needed to complete a job". My own experience set overlaps that considerably (with the addition of Fortran, BASIC, COBOL, PL/I and APL. I've managed to avoid Notes and Delphi, so far.)
None of that qualifies you to comment on Java, of course. Today, assuming that because something wasn't coded in Java means it performs better than a Java-based solution is silly. "Higher level of control" sounds nice but doesn't mean much, unless by "higher level" you mean directly accessing memory or attached devices...which most folks would call "lower".
And I very much doubt a situation ever *demands* no cross-platform execution. Unless you work for Microsoft...
Erm...the C++ programmer is only "free to fix it" if it's in his code, or code he controls. "Home-built" apps actually do call libraries and the OS too. Calling a virtual machine an "emulator-like environment" is kind of silly; modern JVMs perform dynamic optimizations that bear little resemblence to what an emulator typically does.
.Net person the motivation for all this noise becomes a bit clearer, and my original point about "potentially malicious languages" still stands. :-)
"A C++ app can be just as secure if coded correctly" says nothing; all cars are safe "if you drive correctly". What's "more secure" is probably more secure because it was *easier* to secure...unless extraordinary effort was applied to make it so.
And even that may not be enough, a point that is hopefully not lost on a Windows developer like yourself. Now that we know you're a
Ignorance-based relativism doesn't really further the discussion. It's really hard for you to say anything of merit about something you don't understand.
In point of fact Java architecture contributes significantly to making it easier to write secure applications (as it also improves reliability); hand-waving that "bad stuff can happen in either language" is semantically null.
You *can* crash *any* car, but, by design, some are clearly safer than others.
It's been years, and I can't remember what specific limitations there are.
Then maybe you should consider posting only about things you actually do remeber. The set of languages that can be used for malicious resaons includes English.
By design C allows you to access memory at your own descretion. I beleive Java does also (It's been a while)
Sounds like it's not so much a matter of how *long* it's been since you had the one course in Java you were required to take to graduate, but rather how much attention you paid while you were there.
That's the theory. Of course, the FCC doesn't seem to be terribly concerned about the the impact on HF radio communications of baseband-over-powerline (BPL) systems, another "great technology for people underserved by the internet" move. BPL pilot projects are clearly not meeting even the lax technical standards set for them by the FCC, and yet there is no apparent enforcement action forthcoming, even though HF bands are shared by amateurs with military and homeland security users, and BLP systems aren't even Part 15 users, they're "unintentional radiators", an even less-privileged spectrum user. See http://www.arrl.org/bpl
So I'm not sanguine about FCC's dilgigence enforcing technical standards against a municipal WiFi system operating at less-widely used gigahertz frequencies, primarily used for amateur satellite downlinks.
2.4 GHz isn't "unregulated".
The primary allocation is to amateur radio; other users are there on a Part 15 basis, which explains your experience with your neighbor's phone. You're required to accept any interference from other devices on the band. Since I hold a licence for that band, I'm a primary user, and if interfered with by a Part 15 device can require that they fix the problem or shut down.
If I can find them.
Perhaps Microsoft should include an option, like 'Prepare this computer for resale,' which utterly destroys all data."
Of course, "preparing for resale" would include erasing the OS....the seller wouldn't have rights to transfer the licence.
Kel-Tec P-11's are very nice indeed. They will accept S&W standard capacity magazines (not "high capacity", please, what abolishonist nonsense!) as an reply to the size queens who claim nothing smaller than a .45 ACP is stopworthy...just load 12 rounds and where you would have shot once with a .45, shoot twice.
o rg
http://www.kel-tec.com
http://www.pinkpistols.
I used an IBM Model 30 once too. It was an IBM System/360 model 30, and had 64k. In an external chassis sold by a third party. About the size of a refrigerator.
We're hoping the same aliens who fixed Oscar 7 pay a visit to Oscar 40 soon.
How clueful. Evidently you don't know CB (27 MHz) is interfered with by BPL also.
A "cubical warrior" is a warrior shaped like a cube.
Geez.
TCO is a TLA also.
...imagine the size of the discount that made this move cost-justified.
Erm...yes. The club was founded in 1949. Google hits that FLA against "Proton Medical Research Center" "Parent's Music Resource Center" and "Powder Metallurgy Research Center". There's also a "Penn-Mar Radio Club" somewhere. I'd venture to guess we were the first to use "PMRC" among that crew.
Get used to it: it's 2003, the TLA namespace was saturated long ago, and the four-letter acronym space is in danger too...including "For Unlawful Carnal Knowlege".
I'm a programmer, was once married to a chemist who became a health care practioner, and we were both pilots. Driving down the road, every licence plate we saw had at least one alternative meaning.
Press release
Members of the Phil-Mont Mobile Radio Club will put their emergency communication skills to the test when they participate in "Field Day" June 28 and 29. The annual preparedness exercise brings together Amateur Radio operators from throughout North and South America who are committed to assisting their communities in the event of a natural or man-made disaster. Field Day is sponsored by the American Radio Relay League (ARRL), the national association for Amateur Radio.
"Amateur Radio is a lot of fun, but the serious side can't be stressed enough," says Maggie Leber, editor of the PMRC newsletter "The Blurb" and webmistress of the club website at www.phil-mont.org.
"We can play a vital communications role during emergencies, and events such as Field Day ensure that we're ready to handle any type of disaster. We will provide our own electrical power and operate all kinds of radio communications, everything from Morse code to amateur television and amateur satellite radio. We'll be in direct digital communications with the Montgomerty County Emergency Operations center, and will be able to transmit e-mail and other text message through facilities located there."
Field Day is designed to test operators' abilities to set up and operate stations in the field under emergency conditions, such as the loss of commercial electricity. During the weekend, radio operators try to contact as many other Field Day stations as possible, simulating the fast on-air skills needed to assist town officials and served agencies during an emergency. Approximately 35,000 Amateur Radio operators across the country participated in last year's event. The first Field Day was held in 1933.
Ham radio operators typically help with communication during weather-related emergencies such as the devastating tornadoes in the Midwest earlier this spring. But, the need for their services doesn't stop there. A federal grant awarded for emergency communications training in 2002 emphasizes support for ham radio's role in homeland defense.
PMRC will set up its Field Day stations in Lot #4 at Fort Washington State Park, and will be operating from 2pm Staurday until 2pm Sunday. "We hope that the public will come out and see firsthand what this event--and Amateur Radio--is all about," says Ms. Leber, whose amateur callsign is K3XS.
Today there are nearly 700,000 Amateur Radio operators in the United States and more than 2.5 million worldwide. Information on how to become involved in Amateur Radio is available from ARRL -- the national association for Amateur Radio, 225 Main Street, Newington, CT 06111 or by calling 1-800-32-NEW HAM. Visit ARRL on the Web at www.arrl.org.
(This is probably only going to be funny to the union of database geeks and people actually familiar with Mormons, but what the heck!)
You must mean "intersection"....so I'm inferering you're from the LDS side.
tulip blubs sell well, but not like they used to
Yeah, spelling checkers are popular too.
...on this phenomenon at How To Ask Questions The Smart Way by ESR and Rick Moen
Erm...no. MSFT is achingly anxious for all these bandit Access tables to eventually end up in a SQLServer, where they will make money on them by the seat *and* by the server.
Surely any Wizard written by MSFT would be pointing the end-user in that direction. Slashdot would be the very *last* place they'd be sent.
The actual expression is "to be hoist on (or by) one's own petard". A "petard" is simply a bomb used for breaching a fortification. "Hoisting your own petard" is about as illiterate as using "for all intensive purposes" instead of "for all intents and purposes".
Sorry, but 80/87 AvGas is *red*. *100/130* is green. 82 unleaded is purple.
Maggie K3XS, 1/10th owner C-177B N19762, who learned to fly at a tiny little field where taildraggers that drank 80/87 were common.