<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Comments for Borland is Not Open Sourcing JBuilder</title>
<link rel="alternate" type="text/plain" href="http://dn.codegear.com/article/33055" title="Borland is Not Open Sourcing JBuilder" />
<link rel="self" type="application/atom+xml" href="http://dn.codegear.com/article/33055/feed" title="Comments for Borland is Not Open Sourcing JBuilder" />
<id>http://dn.codegear.com/article/33055</id>
<updated>2008-12-01T19:19:31-08:00</updated>
<entry>
<title>Borland is Not Open Sourcing JBuilder</title>
<author>
<name>nsumates nsumates</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=38457</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=38457</id>
<updated>2005-05-30T14:48:42-07:00</updated>
<published>2005-05-30T14:48:42-07:00</published>
<summary>Borland is Not Open Sourcing JBuilder</summary>
<content>no matter whether the confusion is created by the reporter by the developer, to me it is useful and thats it.</content>
</entry>
<entry>
<title>Borland is Not Open Sourcing JBuilder</title>
<author>
<name>Arek Stryjski</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=38423</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=38423</id>
<updated>2005-05-19T10:16:25-07:00</updated>
<published>2005-05-19T10:16:25-07:00</published>
<summary>Borland is Not Open Sourcing JBuilder</summary>
<content>&amp;#8220;A recent article in TheRegister.com has been causing some confusion about Borland's future plans for Jbuilder.&amp;#8221;Don't blame somebody else. Borland made all this confusion not some reporter.On Borland web page I read letter form David Intersimone, and this is how I interpreted it:&amp;#8220;Visual Studio and Eclipse have become the two leading instantiations of this new platform.&amp;#8220;- Eclipse is better then JBuilder.&amp;#8220;(...) we bring the Eclipse ecosystem to our flagship Java IDE, JBuilder, and further advance JBuilder's leading enterprise development functionality for both new and existing customers.&amp;#8220;- Next version of JBuilder will be build on top of Eclipse framework.&amp;#8221;We will also continue to invest in our support for the Microsoft Windows platform, .NET and Visual Studio. Our Eclipse investment will not diminish, in any way, our investments in Delphi, C++, C#, and Microsoft Windows.&amp;#8221;- We are more interested in Windows then in Java.Best regards</content>
</entry>
<entry>
<title>Borland is Not Open Sourcing JBuilder</title>
<author>
<name>Arek Stryjski</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=38422</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=38422</id>
<updated>2005-05-19T10:16:11-07:00</updated>
<published>2005-05-19T10:16:11-07:00</published>
<summary>Borland is Not Open Sourcing JBuilder</summary>
<content>&amp;#8220;A recent article in TheRegister.com has been causing some confusion about Borland's future plans for Jbuilder.&amp;#8221;Don't blame somebody else. Borland made all this confusion not some reporter.On Borland web page I read letter form David Intersimone, and this is how I interpreted it:&amp;#8220;Visual Studio and Eclipse have become the two leading instantiations of this new platform.&amp;#8220;- Eclipse is better then JBuilder.&amp;#8220;(...) we bring the Eclipse ecosystem to our flagship Java IDE, JBuilder, and further advance JBuilder's leading enterprise development functionality for both new and existing customers.&amp;#8220;- Next version of JBuilder will be build on top of Eclipse framework.&amp;#8221;We will also continue to invest in our support for the Microsoft Windows platform, .NET and Visual Studio. Our Eclipse investment will not diminish, in any way, our investments in Delphi, C++, C#, and Microsoft Windows.&amp;#8221;- We are more interested in Windows then in Java.Best regards</content>
</entry>
<entry>
<title>Borland is Not Open Sourcing JBuilder</title>
<author>
<name>Craven Weasel</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=38421</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=38421</id>
<updated>2005-05-19T00:37:58-07:00</updated>
<published>2005-05-19T00:37:58-07:00</published>
<summary>Borland is Not Open Sourcing JBuilder</summary>
<content>It's a shame - the Open Source community might have actually given us a version of JBuilder based on what developers want, rather than the expensive bloatware that we currently have.  But there's always Eclipse, which BEA are supporting.  I sense a forthcoming exodus, perhaps also from StarTeam to ClearCase while we're at it.</content>
</entry>
<entry>
<title>Borland is Not Open Sourcing JBuilder</title>
<author>
<name>Ryszard Kaczynski</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=38379</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=38379</id>
<updated>2005-05-08T09:24:21-07:00</updated>
<published>2005-05-08T09:24:21-07:00</published>
<summary>Borland is Not Open Sourcing JBuilder</summary>
<content>serial Number Key C++BuilderX</content>
</entry>
<entry>
<title>Borland is Not Open Sourcing JBuilder</title>
<author>
<name>Gerhard Stoltz</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=38367</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=38367</id>
<updated>2005-05-03T11:22:32-07:00</updated>
<published>2005-05-03T11:22:32-07:00</published>
<summary>Borland is Not Open Sourcing JBuilder</summary>
<content>Jeez! The way this guy states it, my JBuilder is a loser (dying that is!). Surely you guys can hit back with some statistics to defy his statements.I always though that JBuilder is one of the most advanced compilers &#8211;it already were improving its past features when Visual Studio offered same for the first time. And, surly the Java world has not converted to IBM, or has it?It is not the first time a new release does not sell so well. JBuilder X is just fine for me at thus time. This is a mature compiler and you guys are releasing to quick anyway&#8211; upgrade costs are not worth it.</content>
</entry>
<entry>
<title>Borland is Not Open Sourcing JBuilder</title>
<author>
<name>Mike Dever</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=38363</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=38363</id>
<updated>2005-05-02T19:51:36-07:00</updated>
<published>2005-05-02T19:51:36-07:00</published>
<summary>Borland is Not Open Sourcing JBuilder</summary>
<content>- I wish Borland could address the Pricing issue.I'm a solo Hobbist developer, because I'm stuck in a Microsoft shop.But, I use JBuilder Pro at home, I'd like to be able to upgrade to Enterprise,but, there's no way in H*LL I'll get your price past my wife!Is there anyway you can offer a Pro+ price model, including UML modeling and EJB development for some kind of reasonable price?  The extent of my commercial development would be building a personal web site, which I'm almost 100% positive would bring in Zero money.I'm running a paid for copy of JBuilder pro 2005 on OS X.Respectfully,Michael J. Dever</content>
</entry>
<entry>
<title>Borland is Not Open Sourcing JBuilder</title>
<author>
<name>Francois COURTAULT</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=38362</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=38362</id>
<updated>2005-05-02T01:21:21-07:00</updated>
<published>2005-05-02T01:21:21-07:00</published>
<summary>Borland is Not Open Sourcing JBuilder</summary>
<content>Hello,Nice that you clarify the situation.Regards.</content>
</entry>
</feed>
