Firefox users tend to be savier users I believe. I can't prove it just as they can't prove cause between firefox users not being convinced to click on ads. Anyway, if they are savier, they won't click on false ads that look like windows widgets and crap.
I was not aware single operand devices, that have larger memories, but the simplest ALUs are that hard to design.
If it's so fucking problematic for diebold to do it right, why not have intel, ti, amd, well.. maybe not intel, or other chip makers design the damned thing. It's not hard son.
I'm a java developer too. You'd be surprised about applet use. Lots of games for instance, are written in Java. There are always two options. Applets and flash. Also, whensomeone doesn't know flash, they usually default to java. It may be a small enough group of people to you, but they are still a significant number.
Documentation documentation documentation, especially in a large group. If something is described as working one way, and then it is changed, the written documentation must be cahnged and made clear what is going on. This includes unit tests and examples if necessary.
I'm playing this game right now. It sucks. Arbitrary grading, traffic trying to get to class, books costing $100+.. wait.. you mean playing behind a computer? Oh.. my bad.;P
J2EE is not about the OS, server or database. It's a specification. JBoss (JBass.. heh), Geronimo, Welogic and many others are implementations of it. Some are certified, some are not, like Resin.
You can run it on many os's, including linux. Apache is making one of the J2EE servers. I'm not sure where databases came into all of this, since it's fairly independent. I.e. w/ jboss, there are data mappings for all of these servers, if you decide to use EJB, which is part of the spec, but not a requirement to use. The last thing is the big ol' P.
J2EE is a set of technology specs. Things like XML manipulations (JAXB, JAXM), communication "stuff", like SOAP, JMS and JMX, database abstractions, like EJB using JDO, CMP, BMP.. "web stuff", though you can do your own protocols, with the servlet spec. Last I checked, the closes to a spec I've seen is p5ee, which had an interesting run. You had options of what to use, maybe too many, in p5ee, but that was about it. It would have been nice to see a tight binding between everything.
Anyway.. the LAM in LAMP is irrelivant in this article. I can use Linux, Apache and MySQL with J2EE if I so desired.
This is a somewhat easy problem, no? It's the shortest path problem if you make each square of space a connected vertex. Or did I miss something here...
You don't have the developers talking to each others directly. You have lead developers or architects talking to each other. THey agree on deliverables and communicate changes that way. Instead of having a * structure, you have a small star with offshoots.
Or like me, someone who has a cut on their thumb that left a scar on their thumb. If this was during usage of a biometric system, I've just lost my password!
People dont' use software because it's easier not to, thus it's more insecure. That doesn't jibe. If a user wants to encrypt their email, which is NOT REQUIRED, they easily can.
Take ssh as a counter example. You can't sniff the line (easily) because you are forced to use the security. User feels no impact.
Of course you can. Security only means you are who you are and you can do what you can do. Simplest secure app I can think of actually, is ssh. Back it up with something that checks the difficulty of passwords, and you have something that allows access to a foreign system easily. The ease of use of the rest of the system on the other side is totally seperated from the security.
I can make a horrible to use app that is insecure, and with a bit of effort, make a system that is secure, but easy to use.
Take pgp and email. There are TONS of plugins for various emali clients to support signing and encrypting email. Yes, encryption can be broken someday, it's true, but if someone made a plugin that bumped it to 16k keys, it's easy and fairly secure. If people are further educated and enforcfed to not share their password and private key, it's quite possible.
If you make a system that requires dozens of passwords to do things, duh, people will reuse their passwords or make they simple, or worse yet, put them on their monitors.
Back in the DOS days, the fact that code on a floppy header or something would get executed on insertion was a problem. Solution, don't bring that into memory for execution.
Word, at a point, by default, would execute macros on load of a document. Don't bring in code from a document and execute it.
In outlook, looking at email can cause JS to execute which may have it's own problems due to the implementation of js. Don't execute the JS.
Don't try and figure out how viruses work. Figure out what they exploit and close them up. Duh.
You are right, they are messy. Thus things like IMAP, webdav and the likes. But mind you, what you gain in portability, you lose in performance. Things like photoshop might not be happy when you deal with multiple multi meg files. Well.. not unahppy..just slower.
Slashdot Mirror
Isn't that like Windows 3.11 for MS-DOS? :)
As my simulation server, it's crap. I run things on my 900mhz mac.
Tell that to the Unix group. It is Unix by their definition. :)
But you can't beat ambidextrious ;) Someone set you shallow? Someone set you wide? Switch up!
Firefox users tend to be savier users I believe. I can't prove it just as they can't prove cause between firefox users not being convinced to click on ads. Anyway, if they are savier, they won't click on false ads that look like windows widgets and crap.
Maybe that's why we get dupe stories..
" and a staff of 800(!) computer scientists"
I doubt they are all scientists. I'm sure most are just sysadmin/operations employees.
I finally can post it and be in context...
"Wick, wick wick wick wick wick, wack!"
If it's so fucking problematic for diebold to do it right, why not have intel, ti, amd, well.. maybe not intel, or other chip makers design the damned thing. It's not hard son.
I'm a java developer too. You'd be surprised about applet use. Lots of games for instance, are written in Java. There are always two options. Applets and flash. Also, whensomeone doesn't know flash, they usually default to java. It may be a small enough group of people to you, but they are still a significant number.
Not that critical? 1.5 was released in the last month. What do you think all the people were using before last month?
And I've worked in small and large groups, where it's failed and succeeded all that random times.
Documentation documentation documentation, especially in a large group. If something is described as working one way, and then it is changed, the written documentation must be cahnged and made clear what is going on. This includes unit tests and examples if necessary.
"Woops those goes gravity."
I'm playing this game right now. It sucks. Arbitrary grading, traffic trying to get to class, books costing $100+.. wait.. you mean playing behind a computer? Oh.. my bad. ;P
J2EE is not about the OS, server or database. It's a specification. JBoss (JBass.. heh), Geronimo, Welogic and many others are implementations of it. Some are certified, some are not, like Resin.
You can run it on many os's, including linux. Apache is making one of the J2EE servers. I'm not sure where databases came into all of this, since it's fairly independent. I.e. w/ jboss, there are data mappings for all of these servers, if you decide to use EJB, which is part of the spec, but not a requirement to use. The last thing is the big ol' P.
J2EE is a set of technology specs. Things like XML manipulations (JAXB, JAXM), communication "stuff", like SOAP, JMS and JMX, database abstractions, like EJB using JDO, CMP, BMP.. "web stuff", though you can do your own protocols, with the servlet spec. Last I checked, the closes to a spec I've seen is p5ee, which had an interesting run. You had options of what to use, maybe too many, in p5ee, but that was about it. It would have been nice to see a tight binding between everything.
Anyway.. the LAM in LAMP is irrelivant in this article. I can use Linux, Apache and MySQL with J2EE if I so desired.
This is a somewhat easy problem, no? It's the shortest path problem if you make each square of space a connected vertex. Or did I miss something here...
You don't have the developers talking to each others directly. You have lead developers or architects talking to each other. THey agree on deliverables and communicate changes that way. Instead of having a * structure, you have a small star with offshoots.
Or like me, someone who has a cut on their thumb that left a scar on their thumb. If this was during usage of a biometric system, I've just lost my password!
Take ssh as a counter example. You can't sniff the line (easily) because you are forced to use the security. User feels no impact.
Of course you can. Security only means you are who you are and you can do what you can do. Simplest secure app I can think of actually, is ssh. Back it up with something that checks the difficulty of passwords, and you have something that allows access to a foreign system easily. The ease of use of the rest of the system on the other side is totally seperated from the security.
I can make a horrible to use app that is insecure, and with a bit of effort, make a system that is secure, but easy to use.
Take pgp and email. There are TONS of plugins for various emali clients to support signing and encrypting email. Yes, encryption can be broken someday, it's true, but if someone made a plugin that bumped it to 16k keys, it's easy and fairly secure. If people are further educated and enforcfed to not share their password and private key, it's quite possible.
If you make a system that requires dozens of passwords to do things, duh, people will reuse their passwords or make they simple, or worse yet, put them on their monitors.
Back in the DOS days, the fact that code on a floppy header or something would get executed on insertion was a problem. Solution, don't bring that into memory for execution.
Word, at a point, by default, would execute macros on load of a document. Don't bring in code from a document and execute it.
In outlook, looking at email can cause JS to execute which may have it's own problems due to the implementation of js. Don't execute the JS.
Don't try and figure out how viruses work. Figure out what they exploit and close them up. Duh.
You work for bestbuy, don't you...
You are right, they are messy. Thus things like IMAP, webdav and the likes. But mind you, what you gain in portability, you lose in performance. Things like photoshop might not be happy when you deal with multiple multi meg files. Well.. not unahppy. .just slower.