News for hackers. Stuff that matters.
Re:“No, we’re telling everyone we are using Java” by peterlk on Saturday March 09, 2019 @01:52PM (#19347751)
This is not always true. A friend once built an application for the government (I don't remember any more specifics) in Python. He delivered it to them and mentioned in a document somewhere that it was written in python. This was unacceptable to them because python was not on the list of approved languages. So, after some negotiating, he caved, switched the project to Jython (with minimal changes) and delivered it as "running on the JVM". This was seen as acceptable, and the delivery was accepted.
Re:“No, we’re telling everyone we are using Java” by lostlogin on Saturday March 09, 2019 @08:03PM (#19349575)
I’ve seen software rejected this at a university as the IT teams (pleural) didn’t like the language it was written in. However the problem was solved by the software vendor withdrawing their quote as we were too hard to deal with.
Re:“No, we’re telling everyone we are using Java” by Calib3r on Monday March 11, 2019 @02:39PM (#19361566)
There is nothing wrong with rejecting software because of the technology it uses.

Think about how important maintenance is. If an organization doesn't have in-house skillset to maintain and enhance software solutions they buy outright, why would they want it?

Re:“No, we’re telling everyone we are using Java” by lostlogin on Tuesday March 12, 2019 @03:18PM (#19371926)
I agree, though this isn’t what occurred. University IT is wonderous to experience though I am speaking from an experience of just 1. Hopefully your mileage varies.
Re:“No, we’re telling everyone we are using Java” by S4M on Saturday March 09, 2019 @08:17PM (#19349623)
Why didn't they specify beforehand theor language choice? The negociation about Jython you describe should have taken place before the work started
Re:“No, we’re telling everyone we are using Java” by godelski on Sunday March 10, 2019 @04:14AM (#19350955)
It likely was, but buried in one of the hundreds of documents they reference.
Re:“No, we’re telling everyone we are using Java” by misiti3780 on Saturday March 09, 2019 @06:07PM (#19349127)
That must have changed in the past 10 years because I was working on a DOD project in 2007 and it had a large python component.
Re:“No, we’re telling everyone we are using Java” by frank_nitti on Saturday March 09, 2019 @06:46PM (#19349292)
In my experience in the aerospace industry working closely with USAF, it depends entirely on the program (as in military/civil program, not computer program) as well as the systems being targeted for deployment. I worked on projects that allowed Python 2, but not 3, some that only allow the Python that ships with Anaconda or Canopy. Many programs and classified environments are barely getting approval for C++11 and some unfortunate teams are stuck with uncompiled VBA macros behind Excel UIs because the security personnel for their target systems is unable to review compiled code in fewer than 6 months... it is a mess.
Re:“No, we’re telling everyone we are using Java” by godelski on Sunday March 10, 2019 @04:17AM (#19350962)
C++11 is becoming pretty common. The super computer centers (LCFs) uses C++11 now.
Re:“No, we’re telling everyone we are using Java” by giancarlostoro on Saturday March 09, 2019 @05:39PM (#19348989)
I wonder why that is. I know theres a list of DoD approved software licenses and guidance on using open source software but didnt know there was a list of languages allowed.
Re:“No, we’re telling everyone we are using Java” by sharpy on Saturday March 09, 2019 @05:45PM (#19349020)
Probably more to do with the runtime environment.
Re:“No, we’re telling everyone we are using Java” by sieabahlpark on Saturday March 09, 2019 @06:46PM (#19349293)
This is exactly why.
Re:“No, we’re telling everyone we are using Java” by dwaite on Saturday March 09, 2019 @11:10PM (#19350164)
Some governments (and individual institutions) will have restrictions on only supporting standards because it allows for competing implementations. Some will require multiple implementations directly. Still others may have restrictions based on whether there was a successful audit of the runtime environment.