News for hackers. Stuff that matters.
Re:“No, we’re telling everyone we are using Java” by jwr on Saturday March 09, 2019 @01:01PM (#19347432)
Back when I worked on building software for clients, I used to tell people "we run all software on the Java Virtual Machine" instead of "it's written in Clojure", because I was afraid they would get scared.

But then I noticed that nobody actually cares much about what tools you use, as long as they get the job done. The end result is what counts.

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.
Re:“No, we’re telling everyone we are using Java” by samsonradu on Saturday March 09, 2019 @01:14PM (#19347522)
Many times it is hard to pinpoint what/when the ‘end result’ is. So while the clients are happy now, they won’t be happy to hear they might have a hard time maintaining the project through the years. Clients will want to know they can hire people to work on the codebase.
Re:“No, we’re telling everyone we are using Java” by dwaite on Saturday March 09, 2019 @11:12PM (#19350175)
Unfortunately most times if an external vendor is delivering custom software the clients have already failed - software has a lifecycle that extends far beyond 1.0 delivery. This is why we still have things like X-UA-Compatible: IE=5.
Re:“No, we’re telling everyone we are using Java” by cmauniada on Saturday March 09, 2019 @01:25PM (#19347589)
I wish I followed this advice when I was setting up lambdas on aws. There was this general distaste for "java" in the dev community. Doing a new project and this time around I am using java, and it works so beautifully. The second choice would have been python, but I like the strict type checking.
Re:“No, we’re telling everyone we are using Java” by vajrabum on Saturday March 09, 2019 @01:53PM (#19347758)
Do you find that using the JVM in Lambda affects your cold start times? If so, do you have a pre-warm strategy and how does it work? Or maybe it doesn't matter for your application?
Re:“No, we’re telling everyone we are using Java” by olavgg on Saturday March 09, 2019 @03:45PM (#19348377)
Try Micronaut, which is a micro framework specifically designed for superfast startup time and low memory footprint. It also works with GraalVM.
Re:“No, we’re telling everyone we are using Java” by boyter on Saturday March 09, 2019 @02:23PM (#19347921)
I did when I used Java Lambdas behind API gateway for a largish public API. I ended just setting the HTTP purification tests to run every minute. Solved the issue and let me know how stable it was. Not a huge issue in the end.
Re:“No, we’re telling everyone we are using Java” by sharpy on Saturday March 09, 2019 @05:47PM (#19349030)
Lambda does re-use the JVM instances where it can to alleviate that.
Re:“No, we’re telling everyone we are using Java” by dlhavema on Saturday March 09, 2019 @08:45PM (#19349702)
That only matters if your concurrency is one. If you get 10 requests each before the previous one completes you will get cold starts every other call or so.. its manageable, just takes effort.
Re:“No, we’re telling everyone we are using Java” by mrep on Saturday March 09, 2019 @08:37PM (#19349677)
That is hilariously ironic considering 90% of AWS is written in Java.
Re:“No, we’re telling everyone we are using Java” by technion on Saturday March 09, 2019 @08:47PM (#19349707)
Have you got a source or more information on this? I'm not disputing the statement - but I've seen several different languages claimed to run "most of AWS" (including Haskell at one point) and it'd be good to have a firmer answer.
Re:“No, we’re telling everyone we are using Java” by mrep on Saturday March 09, 2019 @10:27PM (#19349991)
I used to work for AWS. The API framework that powers most if not all of AWS API's is called "Coral" and is Java based.
Re:“No, we’re telling everyone we are using Java” by jophde on Saturday March 09, 2019 @11:19PM (#19350212)
It's like people think Java only supports concurrency via thread pool and isn't capable of event loop / async io models.
Re:“No, we’re telling everyone we are using Java” by raverbashing on Saturday March 09, 2019 @05:05PM (#19348802)
> But then I noticed that nobody actually cares much about what tools you use, as long as they get the job done.

Unfortunately there are a lot of cases where this matter:

- Customer requires the sw to run on their standard environment (think some version of RHEL, or some Windows Server version). Hence you're limited to what's supported there (usually from the vendor). No bleeding edge versions of Python/Node/.NET etc. You might need to build a Go or Rust binary for that specific system and it might not always be obvious. Java might be a different story, but I wouldn't risk it.

- Embedded software (for similar reasons)

- Sw that needs to run on a customer's system

- Sw that needs to interface with an existing system (loading a DLL/.so? JVM?)

Re:“No, we’re telling everyone we are using Java” by marco_salvatori on Saturday March 09, 2019 @11:48PM (#19350346)
Yes. When a client hires a developer, he cares that he receives a proper delivery and he cares that all of the decisions related to that delivery were made in his best interests. Technology choices are an important part of building a technical vision for a company and planning for software maintenance. People may not seem to care much, but that's only because they are trusting the people they hire to care and to know better than they do. When there are any questions on technology, clients appreciate and value unbiased discussion on those choices, in the context of their business. An important part of having clients, perhaps the most important, is establishing trust and one does that with success, but also a record of transparent, appropriate project decisions.
Re:“No, we’re telling everyone we are using Java” by zmmmmm on Saturday March 09, 2019 @02:45PM (#19348046)
I still tell people we're using Java instead of Groovy, but that's more because I can't be bothered having the repeated 5 minute discussion with them about what it is. (Besides that, I actually consider Groovy almost to be essentially like a template engine or set of macros for writing Java code. It's not like other JVM languages that try to introduce a different style).
Re:“No, we’re telling everyone we are using Java” by linkmotif on Saturday March 09, 2019 @02:53PM (#19348104)
Groovy, the real JavaScript. I love Spock but never could get into using Groovy for non-test code.
Re:“No, we’re telling everyone we are using Java” by vorg on Saturday March 09, 2019 @05:30PM (#19348942)
Good idea. I refer to Apache Groovy as "Bash for the JVM". The static typing features in Groovy were bolted on for version 2, whereas Scala and Kotlin were designed from the ground up for building actual systems on the JVM, so they're a far better choice for that.
Re:“No, we’re telling everyone we are using Java” by zmmmmm on Saturday March 09, 2019 @04:33PM (#19348626)
Yeah, you really need to adopt a completely different style if you're writing a whole applications with Groovy as opposed to scripting or test code. It's like a different language almost (more like nicer Java). It does work quite well for it when you do that though.
Re:“No, we’re telling everyone we are using Java” by linkmotif on Saturday March 09, 2019 @05:59PM (#19349091)
I really like groovy with all its groovy idioms and its extended library. It’s really fun to Google for how to write something in Groovy you usually get something really ice. I just didn’t like the lack of typing for non test code. And spotty IDE support even in IntelliJ. It seems to be perfect for tests because your code still compiles and you can fix the tests when you’re ready. Also Spock is beautiful...
Re:“No, we’re telling everyone we are using Java” by nitrogen on Saturday March 09, 2019 @02:56PM (#19348115)
You might enjoy Kotlin.
Re:“No, we’re telling everyone we are using Java” by linkmotif on Saturday March 09, 2019 @03:13PM (#19348206)
Yeah I really want to move to a language with pattern matching. Hopefully it will finally land in Java
Re:“No, we’re telling everyone we are using Java” by vbezhenar on Saturday March 09, 2019 @04:46PM (#19348699)
Kotlin does not support pattern matching.
Re:“No, we’re telling everyone we are using Java” by sk5t on Saturday March 09, 2019 @05:36PM (#19348973)
Yeah, Kotlin has some "enhanced switch" type stuff, but nothing that compares to Scala's matching with unapply, list extraction, etc.
Re:“No, we’re telling everyone we are using Java” by vbezhenar on Sunday March 10, 2019 @06:19AM (#19351296)
Actually they have some foundations, componentN functions serve similar role to unapply, so theoretically it should be possible to build good enough pattern matching. But, unfortunately, they seem to slow down language development a lot since release.
Re:“No, we’re telling everyone we are using Java” by nostrademons on Saturday March 09, 2019 @06:46PM (#19349294)
It has destructuring in value binding and lambda parameters, as well. Pretty handy when you're dealing with a lot of pairs, triples, and data classes, though not quite as powerful as true pattern-matching.
Re:“No, we’re telling everyone we are using Java” by linkmotif on Saturday March 09, 2019 @05:57PM (#19349076)
Oh! Thought it did. Forget Kotlin, then :)!!
Re:“No, we’re telling everyone we are using Java” by sk5t on Saturday March 09, 2019 @06:04PM (#19349114)
Kotlin is still a pleasant language to use, and some of the ideas have some good carryover to Scala, with quite a lot less culture shock than going right from Java to Scala.
Re:“No, we’re telling everyone we are using Java” by dionian on Saturday March 09, 2019 @06:01PM (#19349100)
scala, eta
Re:“No, we’re telling everyone we are using Java” by Floegipoky on Saturday March 09, 2019 @11:35PM (#19350285)
Re:“No, we’re telling everyone we are using Java” by trimbo on Saturday March 09, 2019 @05:29PM (#19348932)
> Back when I worked on building software for clients, I used to tell people "we run all software on the Java Virtual Machine" instead of "it's written in Clojure", because I was afraid they would get scared.

That seems... dishonest? What happens when the client wants to hire someone else in the future, only to find out it's not Java, it's actually this language which is not mainstream at all?

Re:“No, we’re telling everyone we are using Java” by sethhochberg on Saturday March 09, 2019 @05:43PM (#19349012)
I think it would be dishonest if the agreement was that the software should be built in Java - but to me, this reads more like an operational concern. The client felt comfortable with a software package they can deploy on the JVM... but that doesn't necessarily mean they cared whether it was written in Java. If I were hiring a dev for a Java project, I'd explicitly hire a Java developer, not just someone who promised a product which would run on the JVM.
Re:“No, we’re telling everyone we are using Java” by OkGoDoIt on Saturday March 09, 2019 @06:33PM (#19349248)
I think the point is the client might not be sophisticated enough to realize there’s a distinction there. If my auto mechanic replaced a part in my car with something that worked basically the same but cost me a lot of time and money and hassle to fix when it breaks down the road, I’d be pretty upset, especially if he strongly implied that he replaced it with a normal part.
Re:“No, we’re telling everyone we are using Java” by trimbo on Saturday March 09, 2019 @08:00PM (#19349571)
> I think the point is the client might not be sophisticated enough to realize there’s a distinction there

Yup, that's exactly my point. Your car analogy is a good one. I was going to make a similar one with house construction but you've hit on it well.

Re:“No, we’re telling everyone we are using Java” by baud147258 on Monday March 11, 2019 @07:19AM (#19358086)
Actually, I think there are cases where the clients would care: for example with on-premise software, using either the OpenJDK or Oracle JVM will incur different costs. Idem with Oracle/SQL Server.