Comments on: Writing experimental code. The pschological barrier with Java http://almaer.com/blog/writing-experimental-code-the-pschological-barrier-with-java blogging about life, the universe, and everything tech Sat, 08 Sep 2012 07:06:53 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Joshua Hoover http://almaer.com/blog/writing-experimental-code-the-pschological-barrier-with-java/comment-page-1#comment-9094 Joshua Hoover Wed, 06 Oct 2004 01:18:06 +0000 http://almaer.com/blog2/writing-experimental-code-the-pschological-barrier-with-java#comment-9094 Hey Dion, I was at your first session on Groovy and it was very interesting. One of my buddies at work was there too and we were just talking about Groovy this morning. He said he didn't see it "catching on" all that much but I told him that for a guy like me who actually prefers a language/environment like PHP (in many situations) over Java or .Net (shocking, I know!), Groovy is rather interesting. Of course, I'd actually rather see the Parrot project take off for dynamic languages like PHP, Python, Perl, Ruby, etc. I think a common cross platform engine that best suits dynamic languages is better than wedging them into the JVM or .Net's CLR. Although, I do like the concept of utilizing Java's strong suite of libraries so that's +1 for Groovy. :) I'm skeptical about Java these days. (Ditto for Web Services...sorry Justin!) It seems like the big vendors call the shots with the JCP process and many Java developers are consumed with theoretically correct solutions versus real world ones. That may be changing a bit with projects like Spring catching on and EJB being given the boot by many developers, but I'm still a bit skeptical. I tend to agree with Dave Thomas when he expressed his concern that technologies were coming and going too fast. We just learn something, get half way good at it and then throw it away only to start from scratch with another new technology. The Java world seems to really get beat up over this -- look no further than persistence and MVC frameworks. Competition is good, but change simply for the sake of change (or politically charged motives) is not so good. Anyway, the conference was great! I attended both your Groovy and JDO sessions and they were excellent. You're a very good speaker which is rather rare in the technology space. I'm recommending more of our development team go to the conference in Milwaukee next year. Josh P.S. Yes, I was the guy expressing similar view points during the server side BOF and the one who asked the (obvious poke to get the panel going) question about Open Source Java. I couldn't resist. :) P.P.S. What is up with a tech conference not having wireless Internet access available?! Hey Dion,

I was at your first session on Groovy and it was very interesting. One of my buddies at work was there too and we were just talking about Groovy this morning. He said he didn’t see it “catching on” all that much but I told him that for a guy like me who actually prefers a language/environment like PHP (in many situations) over Java or .Net (shocking, I know!), Groovy is rather interesting. Of course, I’d actually rather see the Parrot project take off for dynamic languages like PHP, Python, Perl, Ruby, etc. I think a common cross platform engine that best suits dynamic languages is better than wedging them into the JVM or .Net’s CLR. Although, I do like the concept of utilizing Java’s strong suite of libraries so that’s +1 for Groovy. :)

I’m skeptical about Java these days. (Ditto for Web Services…sorry Justin!) It seems like the big vendors call the shots with the JCP process and many Java developers are consumed with theoretically correct solutions versus real world ones. That may be changing a bit with projects like Spring catching on and EJB being given the boot by many developers, but I’m still a bit skeptical.

I tend to agree with Dave Thomas when he expressed his concern that technologies were coming and going too fast. We just learn something, get half way good at it and then throw it away only to start from scratch with another new technology. The Java world seems to really get beat up over this — look no further than persistence and MVC frameworks. Competition is good, but change simply for the sake of change (or politically charged motives) is not so good.

Anyway, the conference was great! I attended both your Groovy and JDO sessions and they were excellent. You’re a very good speaker which is rather rare in the technology space. I’m recommending more of our development team go to the conference in Milwaukee next year.

Josh

P.S. Yes, I was the guy expressing similar view points during the server side BOF and the one who asked the (obvious poke to get the panel going) question about Open Source Java. I couldn’t resist. :)

P.P.S. What is up with a tech conference not having wireless Internet access available?!

]]> By: Dion Almaer http://almaer.com/blog/writing-experimental-code-the-pschological-barrier-with-java/comment-page-1#comment-9093 Dion Almaer Tue, 05 Oct 2004 01:12:40 +0000 http://almaer.com/blog2/writing-experimental-code-the-pschological-barrier-with-java#comment-9093 A setup script is nice. I have things setup so each project has one... and that is great... but it isn't ideal. I still can't open up javash and start probing the API. However with groovysh I can probe that java API (as with BeanShell/Jython/JRuby/insert more). Jan: I understand what you are saying re large projects. However, one of the largest projects I have been involved with was (way back) in Perl. With good practices it was very managable indeed. D A setup script is nice. I have things setup so each project has one… and that is great… but it isn’t ideal.

I still can’t open up javash and start probing the API. However with groovysh I can probe that java API (as with BeanShell/Jython/JRuby/insert more).

Jan: I understand what you are saying re large projects. However, one of the largest projects I have been involved with was (way back) in Perl. With good practices it was very managable indeed.

D

]]>