Are Java-based Products really trustworthy?

[Owen37]

Vista works for me. I've got it running on 2 laptops and a desktop. No real issues (of course, the hardware is all 2+Ghz Core-2 with 4G memory! :-\ ).

[Nemanja Trifunovic]

Someone voted:

1.00/5 (1 vote)

But it doesn't change the fact that eclipse is slow and consumes all the memoty it can find ;P

Programming Blog utf8-cpp

[Dave Buhl]

dmitri_sps wrote:

I should have added that using construct in C# is something far better than Java's alternative of using finally blocks

The using construct is a bit different than the try/catch/finally construct, and C# actually does have a try/catch/finally construct as well. The difference is that using will ensure clean-up of resources even when an exception is encountered, it will take no action to handle the exception other than clean up the resources (close files, close database connection, etc).

[enhzflep]

Precisely. To compare it to a steaming pile of .... would be perhaps unfair, though to say that eclipse is a nice piece of work worth having is pushing the friendship a bit too far. Linux or Windows, Eclipse is just plain slooooooooow. Shame on you Adobe for adopting it as the IDE for Flex - closing and restarting the whole app because I change active project. :mad::mad::mad::mad:

[Kevin McFarlane]

What about Eclipse? Yes, I know you're a non-IDE person. I've not used it but people say it's good. However, is it all written in Java?

Kevin

[Lost User]

Mine is AMD Dual Core 6000+ (that's 3 GHz per core), and I've got SLI configured. I've got no problems running it, but it just doesn't work the way I want it to. It's a piece of crap! ATM, I like Ubuntu more. :rolleyes: Waiting for Windows 7 to make me say "it works" though...

[raicuandi]

Azureus/Vuze is the best BitTorrent client I ever used, and its made in Java. Other than that, I can't name any other Java program that doesn't stink/is ridiculous. (no wordwrap in NetBeans?! Even notepad has that!)

[dmitri_sps]

Thanks for a lesson, and I should point out that

using(x) { /* code */ }

is equivalent to

try { /* code */ } finally { x.Dispose(); }

with added convenience of having x declared within using declaration, like in

using(Stream x = ...} { ... }

My point simply was that using is more convinient than try-finally construct, so there is a greater chance that people will use it. It is possible to do without any of these, but then resources will be cleaned up only in finalization during garbage collection, so there are good reasons to do this programmatically in your code; and C# facilitates such approach by giving more convinient construct: using.

[super_ttd]

yes ! it's open source if you mind looking at it.

---

[Kevin McFarlane]

I don't have a reason to use it right now but I will bear it in mind if I get some real Java or Python work in the future.

Kevin