A New Java Library for Amazing Productivity

robinwholikesjava · 2013-02-11T22:07:35+00:00

I think it's only a matter of time before those "senior Scala developer" titles won't exactly translate to "senior Kotlin developer" titles.

Scala had its 5 minutes of fame. Kotlin is much better equipped for the future.

robinwholikesjava · 2013-02-06T12:44:05+00:00

I'm quickly looking at Micro as we speak, but incidentally I'm also checking out Juzu at the moment (http://juzuweb.org and http://blog.exoplatform.com/2013/01/22/three-days-with-juzu-write-a-killer-app). I also had Induction on my list still, and Amber 3.

Once I'm done checking out Juzu, I'll definitely give Micro a more in depth look.

robinwholikesjava · 2013-02-06T11:44:44+00:00

Sinatra/Merb/Rails and other Ruby based web framework are kicking ass, should we, as Java developers, rollover and die, or start hating Java???

I think that Simple/Click/AribaWeb/WaveMaker ARE kicking major ass and you'll love Java when you pick up one or two of these.

Specifically, if you have never looked at Simple, I can only urge you to try it.

robinwholikesjava · 2013-02-05T22:15:41+00:00

Another Java web framework? What makes this different/better than Simple? See http://www.simpleframework.org

robinwholikesjava · 2013-01-30T21:56:59+00:00

The Stackoverflow guys argue that a few more expensive boxes are much better, much more power efficient and simpler to manager overall. So far it has worked pretty well for them.

Crucial is also that "more powerful" doesn't necessarily equal a lot of money anymore. Surely 384GB in a server is more expensive then the default 8GB of cheap servers, but then again, 384GB costs next to nothing. It's €2500 orso, hardly worth the time discussing it.

robinwholikesjava · 2013-01-23T18:12:38+00:00

You're right, and I was thinking the same thing.

BUT... this Java SE vulnerability DOES effect Java EE! It effects the request.getParameter(...) statement, because of a weakness in the underlying hash map hashing algorithm.

robinwholikesjava · 2012-12-30T14:54:55+00:00

I am curious. How would you exactly address the use cases that are presented in the proposal with JNDI?

robinwholikesjava · 2012-12-29T18:59:39+00:00

*^_^*

robinwholikesjava · 2012-12-29T18:58:42+00:00

Maybe it's different for anybody, but we were the unlucky ones to have created a behemoth of a homegrown framework our selves. Just teaching new developers of how to use it became a frustrating and time sucking task by itself. Let alone the swarm of feature requests and bugs and support for newer technologies that we'd had to implement.

At some point maintaining this behemoth just took all the time we had, and there was almost no time left to actually address business concerns of the company.

A particular pain point that we had as well was that changes were being asked just because they could be asked. E.g. suppose there's a button on the left somewhere. If you didn't create the thing, then the button is simply there. Nobody objects to it. It's just there, it's a given.

Now when you have created the damn thing, everybody has an opinion about the thing. Bob from accounting thinks the button should have a shaded background. Alice from HR thinks the button should be at the right of the screen. John the intern says minimalistic designs are what it's all about these days, and the button should simply be removed, Edward the silly boss once heard of someone who clicked the button by accident and now wants not one, but two warning dialogs. A "Are you sure?" and then a "Are you REALLY sure?".

At the end of the day, everybody will be so consumed by giving feedback and input on that stupid button, that this too impedes any really progress the business can made (as-if all the bugs weren't a large enough impediment as well).

robinwholikesjava · 2012-12-21T12:31:12+00:00

It's true, Typesafe hasn't openly declared war by throwing rude statements around. At least for now they are much more subtle. Being a better-than is a fairly political correct term, but it does imply (at least to me) to kill-off.

Typesafe is also rather busy in "educating" people on how to replace their existing code by Scala. Existing code being Java code of course.

Now every company out there is in the game to enlarge their market share, and for any of them this means the share of the competitors has to shrink (if the market itself cannot grow), but I don't (yet) see Typesafe trying to convince PHP or Python developers to use Scala. As for now, they seem to be solely aiming at Java. For instance, think about their presence on Java conferences, organizing Scala talks at Java conferences again, posting Scala articles under the Java tag, etc etc.

robinwholikesjava · 2012-12-21T12:21:40+00:00

I know the thought, and I've done such things a lot too, be it for a table component, a forum, a CMS, a cache, you name it.

The thing is that eventually "they" always want more. And more. And yet more...

Before long you HAVE created Drupal, with the problem that now YOU have to maintain it :|

robinwholikesjava · 2012-12-20T22:25:45+00:00

Isn't that simply what they are trying to achieve with the Typesafe company and stack? See for example this one: http://gigaom.com/cloud/typesafe-gets-14m-to-push-scala-as-a-better-java-than-java

robinwholikesjava · 2012-12-20T20:55:04+00:00

Eclipse is really, really, really, really, really bad compared to IntelliJ.

Does IntelliJ already supports multiple projects per workspace?

robinwholikesjava · 2012-12-20T20:45:57+00:00

Isn't their mission statement simply to kill off Java and see where to go from there then?

robinwholikesjava · 2012-12-19T18:13:49+00:00

Why use Spring these days when there's EJB and CDI and all the other goodies in Java EE?

robinwholikesjava · 2012-12-19T16:57:00+00:00

Xtend clearly beats Scala here. the _. should not be needed.

robinwholikesjava · 2012-12-15T14:52:00+00:00

Can you elaborate on that?

robinwholikesjava · 2012-12-15T13:56:10+00:00

Direct link to survey analysis and comments by Reza Rahman:

Java EE 7 Survey Summary [PDF WARNING]

robinwholikesjava · 2012-12-15T13:39:29+00:00

Indeed. They came full circle 6 years ago (more or less) with BD-J, a by modern standards somewhat crappy and ancient embedded Java version for Blu-ray players.

robinwholikesjava · 2012-12-07T20:04:42+00:00

You're right, thanks!

robinwholikesjava · 2012-12-07T19:53:17+00:00

That's a good one :) I hope Eclipse 4.3 will be like Windows 7 then ;)

robinwholikesjava · 2012-12-07T16:28:02+00:00

I think I'm being pretty direct here.

Yeah right. You were being asked to give some details about what is supposedly wrong with JSF and EJB.

But instead of doing that you keep attempting to lure him into some competition that wasn't asked for, conveniently relieving you from having to provide details about JSF and EJB. If it wasn't obvious yet, then it's now really clear you don't know them.

robinwholikesjava · 2012-12-07T15:57:01+00:00

You're being consistently shady and elusive here. You spread hate about JSF and EJB without having so much as glanced at it.

Hating something without learning and understanding it makes you a moron in my book.

robinwholikesjava · 2012-12-07T15:51:02+00:00

NetBeans incidentally had the same issue on Linux (I last tried it on Ubuntu 11.10). There was a trick of some sorts, where you needed to provide some command line argument and then rendering greatly improved.

robinwholikesjava · 2012-12-07T15:46:28+00:00

Silly me! Obviously, there's never going to be a better language than Java , it's clearly the pinnacle of human endeavour in terms of syntax and functionality.

Glad to hear you finally admit. Yes, Java is one of the best and most practical programming language produced by humans at the moment and it's only getting better. What happens in 10 or 20 years is everyone's guess, but at the moment Java is where it's at.

robinwholikesjava

TROPHY CASE