Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*"
Favorites infavorites:mine
Status closed:yes
Types is:question
Exclude -[tag]
For more details on advanced search visit our help page
Results tagged with Search options user 2344

Java is a high-level, platform-independent, object-oriented programming language originally developed by Sun Microsystems. Java is currently owned by Oracle, which purchased Sun in 2010.

Do you test dead code you write? Do anything to confirm that it's probably good? If not, get rid of it. For future code changes, are you going to verify that the dead code still works? If not, get …
answered May 17 '11 by David Thornley
What Oracle does to Java won't matter in the short term. All current JVMs and compilers and libraries will still be available, as well as the community. Oracle's actions are, I think, likely to … harm Java in the long run. So, I'd have no hesitation about using it for my next project, but if I depended on it I'd consider a long-term exit strategy just in case. …
answered Dec 10 '10 by David Thornley
COBOL, Fortran, and C are still relevant. What's the chance that Java will go away in five years? Conceivably there won't be much new Java development in five years, but I'd bet against that, too … , since there's lots of people who use Java and shops are rather slow to switch their preferred languages. …
answered Oct 21 '10 by David Thornley
The standard method of handling a constructor that fails is to throw an exception. Constructors do not typically fail, and it's usually easier to handle such failures in a separate place rather than …
answered Aug 14 '18 by David Thornley
baggage and probably somewhat different design goals, and wound up with something seriously different to work with. They weren't going to use Objective-C, because they thought Java a better choice. The … only ways iOS and Android would have had the same native language would have been if Apple had converted over twenty years of work into Java, for no real gain, or if Google had deliberately remained …
answered May 5 '11 by David Thornley
The most complicated feature of C++ is templates, because of their power and awkward syntax. It isn't hard to use pre-written ones, and it isn't hard to write a simple templated class or function, bu …
answered Dec 2 '10 by David Thornley
It depends on the complexity, not the number of lines. I've written big dumb routines that were easy to understand and which did precisely one thing and did it well, but went on for hundreds of lines …
answered Apr 8 '11 by David Thornley
table and the parser, and both are already too complicated. I don't know the story about Java; all I could do would be speculate. As for C, where it started, all C operators are easily translated …
answered Mar 4 '11 by David Thornley
It isn't so much that OOP is enforced, as that an OOP framework is enforced. It's possible to write procedural programs in Java, although it's easier if they're only one file. The advantage is … uniformity. There are several different types of functions and data in C++, and this does cause some problems and confusion sometimes, and at the very least is more to learn. With Java, you've got …
answered Feb 21 '11 by David Thornley
Implementing to APIs and the like probably isn't a copyright violation in the USA. If you need actual legal advice, find a lawyer of the proper specialty in the jurisdiction you're in. It'll be a lo …
answered Dec 30 '10 by David Thornley
optimize on that basis. C compilers couldn't assume that. Java programs are normally compiled to an artificial machine language, and that is normally compiled on the fly (just-in-time compiling … isn't. Java also requires more run-time support, such as a garbage collector, and the JIT compiler and runtime have to load and get going. That results in increased startup time, which can be …
answered Apr 13 '11 by David Thornley
Inheritance is a very strong relationship between two classes. I don't think Java has any stronger. Therefore, you should only use it when you mean it. Public inheritance is a "is-a" relationship … errors, and many people think those classes are well worth eliminating. If you like dynamic typing and duck typing better than static typing and defined inheritance hierarchies, that's fine. However, the Java way does have its advantages. …
answered Apr 14 '11 by David Thornley
egregious example, consider how far the broken C switch statement propagated. I don't know Javascript and C# well enough to say, but I see no reason for new in Java except that C++ had it. …
answered Feb 14 '11 by David Thornley