No, it would be unprofessional to change the language silently, because it could leave the company with an unmaintainable codebase and invalidate their current automatic code quality checking.
By unmaintainable I don't mean that the code could not possibly be maintained, but that the current staff would have a ramp up period to maintain it, and the worst time to have that would be just after I stop working for them. The most I would do under the radar is a prototype, and I'd propose converting to Java or accepting the other language at the point of becoming something likely to live longer than a prototype. On Aug 30, 2012 12:16 PM, "Kevin Wright" <[email protected]> wrote: > I always figured that anyone who wanted lambdas that much would be sailing > the choppy JVM waters on a differently lingual boat by now. It's not as > though you even have to change your ops infrastructure or much of your > tooling to do so. > > (hint: rename scala.jar/clojure.jar/groovy.jar/whatever.jar to > apache-closures.jar, release your project binaries as you always did. > Don't make a song and dance about it, it's easier to ask forgiveness than > to request permission) > > Jigsaw on the other hand... That means distinctions like SE/ME can be done > away with, long-deprecated code can finally be removed, startup time, > download time, and memory foot print can be reduced, etc. It makes Java > far more suitable for running on something like the Raspberry Pi. These > are cross-cutting concerns that benefit all languages on the Java platform. > > Defender methods and method handles are also just plain awesome. Even > without lambdas, I'd fully expect some powerful optimisations to > be realised on top of those two. > > > > On 30 August 2012 15:57, Thomas Matthijs <[email protected]> wrote: > >> On Thu, Aug 30, 2012 at 4:03 PM, Ricky Clarkson >> <[email protected]> wrote: >> > I want my lambdas now and I'm in a job where using non-Java languages >> > will be a difficult sell. The earlier the release the better for me. >> > >> > I've seen classpath hell exactly once, actually in a current project, >> > and plan to deal with it in a different way - attempting to >> > find/create a combination of libraries that don't have version >> > conflicts, and where that is not possible, moving tasks out of the >> > same JVM process. >> > >> > The other benefit would be JVM startup time, which is less and less an >> > issue each year as machines get faster and Java doesn't get bigger. >> > I'd like to see the startup time be improved further, but lambdas will >> > affect me more than cutting down startup from 5 seconds to 1. >> > >> >> >> I agree fully, jigsaw won't fix any problem i currently have, lambdas >> on the other hand would be very beneficial >> >> -- > You received this message because you are subscribed to the Google Groups > "Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
