<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for Pain and Glory from the Trenches of the IT World</title>
	<atom:link href="http://pinderkent.blogsavy.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://pinderkent.blogsavy.com</link>
	<description>Just another Blogsavy.com weblog</description>
	<pubDate>Fri, 25 Jul 2008 19:33:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>Comment on Swing is not an example of good software reuse. by bla bla</title>
		<link>http://pinderkent.blogsavy.com/archives/104#comment-165</link>
		<dc:creator>bla bla</dc:creator>
		<pubDate>Thu, 27 Mar 2008 14:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/114#comment-165</guid>
		<description>! (What a compelling argument)  Perhaps if they rename the menu methods you'll feel better.</description>
		<content:encoded><![CDATA[<p>! (What a compelling argument)  Perhaps if they rename the menu methods you&#8217;ll feel better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why is NetBeans still so slow? by Rhys</title>
		<link>http://pinderkent.blogsavy.com/archives/122#comment-202</link>
		<dc:creator>Rhys</dc:creator>
		<pubDate>Tue, 25 Mar 2008 20:38:02 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/132#comment-202</guid>
		<description>I find that NetBeans 6.0 runs very well on Windows XP but runs slowly (e.g. sluggish menus) under Ubunto 7.x. Eclipse on the same Ubunto machine runs very well by comparision. It amazes me that doing something a simple as the rendering of a menu should actually be visible at all these days.

BTW, in a past life this same Ubuntu machine was running Red Hat Linux 8.x and NetBeans 3.6 was extremely quick and nice to use in that environment.</description>
		<content:encoded><![CDATA[<p>I find that NetBeans 6.0 runs very well on Windows XP but runs slowly (e.g. sluggish menus) under Ubunto 7.x. Eclipse on the same Ubunto machine runs very well by comparision. It amazes me that doing something a simple as the rendering of a menu should actually be visible at all these days.</p>
<p>BTW, in a past life this same Ubuntu machine was running Red Hat Linux 8.x and NetBeans 3.6 was extremely quick and nice to use in that environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why would I want to use a &#8220;WebOS&#8221;? SSH, X11 and VNC work fine. by Cross</title>
		<link>http://pinderkent.blogsavy.com/archives/16#comment-24</link>
		<dc:creator>Cross</dc:creator>
		<pubDate>Tue, 25 Mar 2008 18:35:28 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/16#comment-24</guid>
		<description>It seems that you never raise up your head to see it has been 21 Century, you really like ppl living in 80's or 90's. The tide of web application can not be ignored.
From the point of views of energy saving, your article is meaningless.</description>
		<content:encoded><![CDATA[<p>It seems that you never raise up your head to see it has been 21 Century, you really like ppl living in 80&#8217;s or 90&#8217;s. The tide of web application can not be ignored.<br />
From the point of views of energy saving, your article is meaningless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Neither JavaScript nor Ruby will the be the &#8220;next big lanuage&#8221;. by Arun N Kumar</title>
		<link>http://pinderkent.blogsavy.com/archives/74#comment-125</link>
		<dc:creator>Arun N Kumar</dc:creator>
		<pubDate>Mon, 10 Mar 2008 10:42:53 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/85#comment-125</guid>
		<description>I dont agree with the statement or its justifications at large. A language doesnt weigh [IMO] based on certain specific aspects like Scalability, Parallelism etc. But on a whole bunch of aspects. People do trade-off these in some cases or address it with different architectural strategies[which really helps overcome these]. It just becomes that much more easier once part of a language, but not limiting.

It is indeed true, there wont be any big language, why? Growth. People are already talking about Java being bloated to death :). Every language evolves and gets complicated and during the process leaves behind quite a few benefits it had when we first chose it. Its a catch-22, if it doesnt evolve, it will die or restrain to certain domains due to its stunted growth [Scheme, CommonLisp, Prolog hmm...], but if it does evolve, it could die of obesity [take C++ for example]. Death in terms of popularity or being a first choice to many [there are nerdos programming in every possible thinkable language, yes even today].

Javascript was a disaster on the server side [SSJS], but still the best bet on a browser even today. Ruby is by far the most simple dynamic language and its growing :).

Its true, Functional Programming is the next big thing and Erlang and Haskell are promising, but they are just like their old functional cousins, limited to their intellect and tooling.

The way I see it, what really will stay is a Platform and we will have multiple languages co-existing and collaborating. On the paradigm as well we wont have a clear winner in Functional programming, OO and Imperative Programming will still rule good.

Platforms like .NET have been implicitly polyglot in nature from day one. Java is strong and mature platform and is now being very friendly to other languages and paradigms.

For instance, JRuby provides both the cool dynamic language support to the Java platform but benefits the robustness, scalability and huge bunch of features that lack in Ruby's own platform which is C based. Scala is the new FP kid out on the block by Martin Odersky, and is on top of the Java Platform. It has a good mix of FP and OO programming.

Instead of having 10 Haskell or 10 Erlang, or even 10 Java developers trying to use their language hammer to build all kinds of apps, the world will have multiple tools JS (yes even JS), Ruby, Java, Haskell etc collaborating on a platform to build apps that are specialized by those languages. Like a JS toolkit for client apps, ruby based integration, haskell based perf oriented modules on say a java platform.

Comments and debate welcome.</description>
		<content:encoded><![CDATA[<p>I dont agree with the statement or its justifications at large. A language doesnt weigh [IMO] based on certain specific aspects like Scalability, Parallelism etc. But on a whole bunch of aspects. People do trade-off these in some cases or address it with different architectural strategies[which really helps overcome these]. It just becomes that much more easier once part of a language, but not limiting.</p>
<p>It is indeed true, there wont be any big language, why? Growth. People are already talking about Java being bloated to death :). Every language evolves and gets complicated and during the process leaves behind quite a few benefits it had when we first chose it. Its a catch-22, if it doesnt evolve, it will die or restrain to certain domains due to its stunted growth [Scheme, CommonLisp, Prolog hmm&#8230;], but if it does evolve, it could die of obesity [take C++ for example]. Death in terms of popularity or being a first choice to many [there are nerdos programming in every possible thinkable language, yes even today].</p>
<p>Javascript was a disaster on the server side [SSJS], but still the best bet on a browser even today. Ruby is by far the most simple dynamic language and its growing :).</p>
<p>Its true, Functional Programming is the next big thing and Erlang and Haskell are promising, but they are just like their old functional cousins, limited to their intellect and tooling.</p>
<p>The way I see it, what really will stay is a Platform and we will have multiple languages co-existing and collaborating. On the paradigm as well we wont have a clear winner in Functional programming, OO and Imperative Programming will still rule good.</p>
<p>Platforms like .NET have been implicitly polyglot in nature from day one. Java is strong and mature platform and is now being very friendly to other languages and paradigms.</p>
<p>For instance, JRuby provides both the cool dynamic language support to the Java platform but benefits the robustness, scalability and huge bunch of features that lack in Ruby&#8217;s own platform which is C based. Scala is the new FP kid out on the block by Martin Odersky, and is on top of the Java Platform. It has a good mix of FP and OO programming.</p>
<p>Instead of having 10 Haskell or 10 Erlang, or even 10 Java developers trying to use their language hammer to build all kinds of apps, the world will have multiple tools JS (yes even JS), Ruby, Java, Haskell etc collaborating on a platform to build apps that are specialized by those languages. Like a JS toolkit for client apps, ruby based integration, haskell based perf oriented modules on say a java platform.</p>
<p>Comments and debate welcome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why should we have to tune the JVM&#8217;s memory parameters to run NetBeans acceptably? by Michael Campbell</title>
		<link>http://pinderkent.blogsavy.com/archives/146#comment-322</link>
		<dc:creator>Michael Campbell</dc:creator>
		<pubDate>Mon, 10 Mar 2008 04:23:19 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/159#comment-322</guid>
		<description>&#62; But Eclipse can require memory tuning parms as well.

Sure, it *can* but it generally doesn't.  Out of the box, Eclipse runs reasonably well.  The author's point here (which you appear to have completely sidestepped) is that Netbeans doesn't.</description>
		<content:encoded><![CDATA[<p>&gt; But Eclipse can require memory tuning parms as well.</p>
<p>Sure, it *can* but it generally doesn&#8217;t.  Out of the box, Eclipse runs reasonably well.  The author&#8217;s point here (which you appear to have completely sidestepped) is that Netbeans doesn&#8217;t.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why should we have to tune the JVM&#8217;s memory parameters to run NetBeans acceptably? by Patrick Mueller</title>
		<link>http://pinderkent.blogsavy.com/archives/146#comment-321</link>
		<dc:creator>Patrick Mueller</dc:creator>
		<pubDate>Sun, 09 Mar 2008 16:50:34 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/159#comment-321</guid>
		<description>But Eclipse can require memory tuning parms as well.  I think what you're pointing out is that it's a shame that many programs using Java require memory tuning.  Memory tuning should be relegated to optimization, instead of a pre-req to run the program in the first place.  It's a Java problem; Eclipse, NetBeans, any web container you might use, etc all inherit the problem from Java.</description>
		<content:encoded><![CDATA[<p>But Eclipse can require memory tuning parms as well.  I think what you&#8217;re pointing out is that it&#8217;s a shame that many programs using Java require memory tuning.  Memory tuning should be relegated to optimization, instead of a pre-req to run the program in the first place.  It&#8217;s a Java problem; Eclipse, NetBeans, any web container you might use, etc all inherit the problem from Java.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why is NetBeans still so slow? by Why should we have to tune the JVM&#8217;s memory parameters to run NetBeans acceptably?</title>
		<link>http://pinderkent.blogsavy.com/archives/122#comment-201</link>
		<dc:creator>Why should we have to tune the JVM&#8217;s memory parameters to run NetBeans acceptably?</dc:creator>
		<pubDate>Sat, 08 Mar 2008 23:29:33 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/132#comment-201</guid>
		<description>[...] date with their developments. The last time I tried it, the results were rather terrible. I found NetBeans 6.0 Beta 1 to be extremely slow, even on a modern system with a multicore CPU and gigabytes of RAM. It wasn&#8217;t just a matter [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] date with their developments. The last time I tried it, the results were rather terrible. I found NetBeans 6.0 Beta 1 to be extremely slow, even on a modern system with a multicore CPU and gigabytes of RAM. It wasn&#8217;t just a matter [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Others are leaving Ruby on Rails, as well. And it&#8217;s not going well. by Josh Charles</title>
		<link>http://pinderkent.blogsavy.com/archives/143#comment-309</link>
		<dc:creator>Josh Charles</dc:creator>
		<pubDate>Tue, 26 Feb 2008 14:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/156#comment-309</guid>
		<description>Copolo,

I don't know what you mean exactly by large, complex systems.  I'm current implementing a RoR application that is much more involved than a 'basic CRUD application.'

The organizational structure of RoR makes it very easy to work with and extend as needed.  Need to validate against an Microsoft Active Directory?  Great, write a plugin.  Need to run through a queue of processes every night at 3 a.m.?  Easy, write a plugin.  Need to generate images?  Don't even need a plugin for that.

RoR makes doing the web parts of your application superbly easy - better than any other framework I've come across. But that's mostly just interface, right?  Well, for all that 'other stuff' you need to do, Rails helps you keep it organized.

It's only called 'magic' because you don't understand what's going on.  Take some time to learn what's underneath, and then you'll be going places.</description>
		<content:encoded><![CDATA[<p>Copolo,</p>
<p>I don&#8217;t know what you mean exactly by large, complex systems.  I&#8217;m current implementing a RoR application that is much more involved than a &#8216;basic CRUD application.&#8217;</p>
<p>The organizational structure of RoR makes it very easy to work with and extend as needed.  Need to validate against an Microsoft Active Directory?  Great, write a plugin.  Need to run through a queue of processes every night at 3 a.m.?  Easy, write a plugin.  Need to generate images?  Don&#8217;t even need a plugin for that.</p>
<p>RoR makes doing the web parts of your application superbly easy - better than any other framework I&#8217;ve come across. But that&#8217;s mostly just interface, right?  Well, for all that &#8216;other stuff&#8217; you need to do, Rails helps you keep it organized.</p>
<p>It&#8217;s only called &#8216;magic&#8217; because you don&#8217;t understand what&#8217;s going on.  Take some time to learn what&#8217;s underneath, and then you&#8217;ll be going places.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Swing is not an example of good software reuse. by boor</title>
		<link>http://pinderkent.blogsavy.com/archives/104#comment-164</link>
		<dc:creator>boor</dc:creator>
		<pubDate>Tue, 26 Feb 2008 09:20:24 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/114#comment-164</guid>
		<description>You're wrong,!! Everything in the java libraries are all magnificent....It is the most used language....</description>
		<content:encoded><![CDATA[<p>You&#8217;re wrong,!! Everything in the java libraries are all magnificent&#8230;.It is the most used language&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Others are leaving Ruby on Rails, as well. And it&#8217;s not going well. by Copolo</title>
		<link>http://pinderkent.blogsavy.com/archives/143#comment-308</link>
		<dc:creator>Copolo</dc:creator>
		<pubDate>Mon, 25 Feb 2008 21:22:22 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/156#comment-308</guid>
		<description>It's been my experience that frameworks or languages that perform "too much magic"  - apparently one of the design goals of RoR - can be very limiting when you are implementing a well-designed system that is something more than a basic CRUD application.

I've seen some impressive things developed in Ruby on Rails, but I don't think it's an appropriate choice for the corporate level - or for software companies with more traditional processes.

RoR should be used for what it was made - quickly and rapidly developing small web applications; and should not be used for developing large, complex systems which have had a lot of underlying planning and thought put into them.</description>
		<content:encoded><![CDATA[<p>It&#8217;s been my experience that frameworks or languages that perform &#8220;too much magic&#8221;  - apparently one of the design goals of RoR - can be very limiting when you are implementing a well-designed system that is something more than a basic CRUD application.</p>
<p>I&#8217;ve seen some impressive things developed in Ruby on Rails, but I don&#8217;t think it&#8217;s an appropriate choice for the corporate level - or for software companies with more traditional processes.</p>
<p>RoR should be used for what it was made - quickly and rapidly developing small web applications; and should not be used for developing large, complex systems which have had a lot of underlying planning and thought put into them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
