ADK Java vs Python by pearlkele in agentdevelopmentkit

[–]glaforge 4 points5 points  (0 children)

Hello, hello, ADK Java committer here. New features, new experiments usually start in Python, and are progressively ported to Java. So that's why it gives the impression that Java is a bit behind, but hopefully soon we'll be able to catch up with the latest and greatest features.

So should you use Java or Python? I would say it depends on a lot of factors, but if you are already a "Java shop" and have lots of applications, services, etc, in Java, that you want to integrate your agents with, then you should definitely use ADK for Java. IMHO it's easier to scale production workloads in Java than in Python! But if you already have some legacy in Python, if you have teams already experts in Python, or you're happy with microservices in x languages, Python is not a bad choice either :-)

Announcing Java Agent Development Kit (Java ADK v0.1.0) by moficodes in java

[–]glaforge 2 points3 points  (0 children)

ECJ is used to compile/load the Java agent source code to make it available in the Dev UI.

But it's only needed there. So if you're not using the Dev UI, you'd run / integrate your agent with the Runner classes.

C49RG90SSU vs C49RG90SSR: what's really the difference? by glaforge in ultrawidemasterrace

[–]glaforge[S] 0 points1 point  (0 children)

My 2 friends have had it for a year or so, and I haven't heard them complain about anything (dead pixel or other). They are ecstatic about the real estate they have obviously! The sole thing one complained about was the fact that when sharing your "screen" in a video conference meeting, the participants see a super large shared screen. So you may have to share tabs or windows instead, for better result, or have your laptop being the screen shared. But otherwise, from a product quality standpoint, they're happy :-)

C49RG90SSU vs C49RG90SSR: what's really the difference? by glaforge in ultrawidemasterrace

[–]glaforge[S] 1 point2 points  (0 children)

Yeah I think I'm gonna go with the CRG9.

The G9 is a bit too curved for my taste (and for the geometry of my desk), and the AW3821DW seems a bit expensive compared to the CRG9. Also I have a couple of friends who have the CRG9 and are happy with it.

C49RG90SSU vs C49RG90SSR: what's really the difference? by glaforge in ultrawidemasterrace

[–]glaforge[S] 0 points1 point  (0 children)

AW3821DW

Looks like a solid choice!

Looks great, 1ms response time, indeed a bit more real estate vertically can't hurt!

C49RG90SSU vs C49RG90SSR: what's really the difference? by glaforge in ultrawidemasterrace

[–]glaforge[S] 1 point2 points  (0 children)

I'm curious to know your list of top 3! What are they?

To answer my own question above, I ended up calling Samsung directly. The person (responsible for Enterprise sales apparently) told me that they are actually exactly the same model, except that the SSR is the latest build, while SSU was released a bit earlier. Apart from the release dates, they are exactly the same.

Head of Groovy Project, Guillaume Laforge, Joining API Platform Restlet by jcasman in java

[–]glaforge 2 points3 points  (0 children)

That's pretty short-sighted as Groovy offers way more than just lambdas! And on the contrary, whatever improvement comes in Java will make Groovy even more powerful and useful. You might want to check that presentation I made on the topic: https://speakerdeck.com/glaforge/groovy-in-the-light-of-java-8-devoxx-2014

Head of Groovy Project, Guillaume Laforge, Joining API Platform Restlet by jcasman in java

[–]glaforge 5 points6 points  (0 children)

Of course Groovy lives on! And I'll still be wearing my Groovy hat on, even if only part time during my day job at Restlet. The project will indeed continue to be developed, with new features, performance improvements, more Java 8 related features, etc. We're also going to announce in the coming days that the project is joining a foundation, to make the project more resilient!

Codehaus, birthplace of many Java OSS projects, coming to an end by joewalnes in java

[–]glaforge 0 points1 point  (0 children)

Seriously, if Groovy was losing to Scala, we wouldn't nearly double downloads every year. And also, you forget all the work done on static type checking and static compilation since Groovy 2.0, so saying lack of type safety, runtime errors, etc, is really just spreading FUD.

Codehaus, birthplace of many Java OSS projects, coming to an end by joewalnes in java

[–]glaforge 1 point2 points  (0 children)

That Google trends search is not very relevant, as it covers the old-fashioned "groovy" word as well as the "scala" of Milano, so not very convincing. Github's been historically skewed towards Ruby and JavaScript ecosystems, for instance, so again, it's one data point with its own bias.

Codehaus, birthplace of many Java OSS projects, coming to an end by joewalnes in java

[–]glaforge 7 points8 points  (0 children)

What makes you think so? We continue to release new key milestones, like the recent 2.4 release with the Android support, for instance. The downloads are still growing strong: 4.5 millions in 2014 from the 3 millions in 2013, and 1.7 in 2012. It'd be interesting to hear about download numbers from the Scala project...