(no title)
Bo102010 | 14 years ago
Also, if they would quit telling me that I can't run VLC because it's not secure, when they have 3 year old versions of the Java Runtime Environment installed on everyone's PC.
Bo102010 | 14 years ago
Also, if they would quit telling me that I can't run VLC because it's not secure, when they have 3 year old versions of the Java Runtime Environment installed on everyone's PC.
fuzzix|14 years ago
But that's not true. I work as a developer or an admin depending on my mood and the money, I would not consider one able to do the job of the other even though I have done each with the same degree in hand.
The discipline of designing stable, maintainable systems & networks or writing code to requirements precisely and accessibly are distinct and often wildly different. Little of it comes with your degree.
That said, my current gig is quite good in that regard: "We support A, B and C. If you want to use X and Z you're on your own. Here are the guidelines on security and patching."
Bo102010|14 years ago
I do doubt that the people making and enforcing IT policies that, e.g. lead to insecure versions of Java being installed on thousands of machines, are more capable than I am at managing the machine I need to use.
samirageb|14 years ago
As for JRE vs. VLC, how do you JRE's status isn't simply a false negative? How many applications in your organization actually utilize the JRE? Is it a non-issue? Are you aware if there are any measures already taken to mitigate known JRE exploits? There is quite a large difference between exploits that exist in an environment vs. those that exist in an application that you actively execute.
Granted I'm not defending the specifics, I personally think VLC is likely fine. But that doesn't change the points made above. In IT, it's always better to go with the devil you know, than the devil you don't.
petervandijck|14 years ago
oz|14 years ago
ryall|14 years ago