Anti Hydrogen
- 37
- 4
- TL;DR
- I am completely ignorant of this, could you help me?
thanks
The discussion revolves around the various uses of the programming language Java, exploring its applications in business development, web development, mobile applications, and object-oriented programming. Participants also touch on the challenges and advantages of using Java, particularly in relation to its extensive library ecosystem and cross-platform capabilities.
Participants express a range of views on Java's applications and its learning curve, with some agreeing on its strengths in object-oriented programming and cross-platform capabilities, while others highlight the challenges and complexities involved. The discussion remains unresolved regarding the best practices for using Java and the implications of its extensive library ecosystem.
Participants note limitations in understanding Java's library dependencies and the potential for outdated knowledge as libraries evolve. There are also references to specific programming challenges that illustrate the practical difficulties faced by developers.
This discussion may be of interest to software developers, computer science students, and professionals considering Java for their projects, as well as those exploring the implications of using Java in various programming contexts.
Anti Hydrogen said:I am completely ignorant of this, could you help me?
Assembler yes, since each processor type has its own instruction set, but C and C++ aren't hardware specific. A given C or C++ program will run on pretty much any hardware, as long as there is a compiler for that hardware.jedishrfu said:Before Java, apps would be written in more hardware specific languages like C/C++ or assembler
It's true that Java programmers depend on libraries a lot, but if you want to see the code inside those libraries, you can easily do so by using a good IDE like NetBeans. I have often done so myself; in fact, that is a great way of learning programming.AdirianSoan said:The downside to this is that Java development tends to be a hodgepodge of different libraries, each with their own logical approach to problems, which means you have to get really, really comfortable living in a tiny island of understanding in a vast sea of ignorance to get anything done; don't expect to ever understand everything going on in even a medium sized application. Everything will be a black box; inputs go in, outputs come out.
jedishrfu said:Except node.js is based on JavaScript not java.
Wrichik Basu said:It's true that Java programmers depend on libraries a lot, but if you want to see the code inside those libraries, you can easily do so by using a good IDE like NetBeans. I have often done so myself; in fact, that is a great way of learning programming.
TWAIN sounds about right as the interface to the scanner.Svein said:Even with a clearly defined interface to the scanner (TWAIN, if my memory serves me right) he was totally unable to connect to the scanner. I was called in and had no trouble connecting to the scanner, but the poor guy did not even know what kind of software interface he needed. I proposed a "pipe", but he did not know the concept. I think we ended up by me creating a file in a defined directory and he reading the file. The problem was of course that he would try to read the file before I had finished writing to it and closed it...
Instead what I’d like to claim is that Java is not, generally, a hard enough programming language that it can be used to discriminate between great programmers and mediocre programmers.