Comments on: Java and Practicality http://blog.tmorris.net/java-and-practicality/ The weblog of Tony Morris Sat, 19 May 2012 02:52:03 +0000 http://wordpress.org/?v=2.6 By: Tony Morris http://blog.tmorris.net/java-and-practicality/#comment-46893 Tony Morris Wed, 29 Sep 2010 23:17:59 +0000 http://blog.tmorris.net/?p=797#comment-46893 Hi Berlin, Yes I do and yes they are ("problem solving" is very broad). Hi Berlin, Yes I do and yes they are (”problem solving” is very broad).

]]> By: Berlin Brown http://blog.tmorris.net/java-and-practicality/#comment-46870 Berlin Brown Wed, 29 Sep 2010 16:48:47 +0000 http://blog.tmorris.net/?p=797#comment-46870 "Consequently, one cannot have a reasonable discussion about the merits of problem solving, using the Java programming language" Don't you write Java libraries? Are those projects included in the problem solving? http://functionaljava.org/ “Consequently, one cannot have a reasonable discussion about the merits of problem solving, using the Java programming language”

Don’t you write Java libraries? Are those projects included in the problem solving?

http://functionaljava.org/

]]> By: Tony Morris http://blog.tmorris.net/java-and-practicality/#comment-44876 Tony Morris Mon, 30 Aug 2010 07:32:39 +0000 http://blog.tmorris.net/?p=797#comment-44876 jih276, my email address is ʇǝu˙sıɹɹoɯʇ@sıɹɹoɯʇ jih276, my email address is ʇǝu˙sıɹɹoɯʇ@sıɹɹoɯʇ

]]> By: jlh276 http://blog.tmorris.net/java-and-practicality/#comment-44865 jlh276 Mon, 30 Aug 2010 00:53:07 +0000 http://blog.tmorris.net/?p=797#comment-44865 Hi Tony, Email would be great. Let me know if you don't already have it. Hi Tony,

Email would be great. Let me know if you don’t already have it.

]]> By: Tony Morris http://blog.tmorris.net/java-and-practicality/#comment-44863 Tony Morris Sun, 29 Aug 2010 23:33:11 +0000 http://blog.tmorris.net/?p=797#comment-44863 Hi jih276, I disagree (in the strongest possible way) with some of your statements. I'm happy to take this further if you like -- perhaps email is appropriate? Hi jih276,
I disagree (in the strongest possible way) with some of your statements. I’m happy to take this further if you like — perhaps email is appropriate?

]]> By: jlh276 http://blog.tmorris.net/java-and-practicality/#comment-44852 jlh276 Sun, 29 Aug 2010 13:24:45 +0000 http://blog.tmorris.net/?p=797#comment-44852 Hi Tony, My own impression is that Java currently does pretty well in terms of cost effectiveness to build solutions to some problems and support these solutions. Java programmers are relatively easy to find. The eco-system (vendors, tools, open source libraries) means that for some software problems, a large part of the problem could already be solved. For instance if the problem is to insert the data located in some XML file into a database where the schema is already defined, for a company that already has Java programmers, then Java is likely to be a practical solution. I don't think this type of problem I mentioned is atypical, so that's why Java being considered practical is not controversial to me. But I'm open minded and if I've been wrong, I'd like to understand why and be able to use a better practical solution whenever possible... Java being wrong "to the extent that you've seen"... Where did it go wrong? What types of additional problems did it introduce? Why wasn't the solution cost effective to build and support? Hi Tony,

My own impression is that Java currently does pretty well in terms of cost effectiveness to build solutions to some problems and support these solutions. Java programmers are relatively easy to find. The eco-system (vendors, tools, open source libraries) means that for some software problems, a large part of the problem could already be solved. For instance if the problem is to insert the data located in some XML file into a database where the schema is already defined, for a company that already has Java programmers, then Java is likely to be a practical solution. I don’t think this type of problem I mentioned is atypical, so that’s why Java being considered practical is not controversial to me. But I’m open minded and if I’ve been wrong, I’d like to understand why and be able to use a better practical solution whenever possible…

Java being wrong “to the extent that you’ve seen”… Where did it go wrong? What types of additional problems did it introduce? Why wasn’t the solution cost effective to build and support?

]]> By: Tony Morris http://blog.tmorris.net/java-and-practicality/#comment-44843 Tony Morris Sun, 29 Aug 2010 08:17:19 +0000 http://blog.tmorris.net/?p=797#comment-44843 jih276, Yes. I'm not sure what more you're looking for. jih276,
Yes. I’m not sure what more you’re looking for.

]]> By: jlh276 http://blog.tmorris.net/java-and-practicality/#comment-44836 jlh276 Sun, 29 Aug 2010 06:47:45 +0000 http://blog.tmorris.net/?p=797#comment-44836 So we are in general agreement to the definition of software problem? Meaning they can include the things that I've listed? So we are in general agreement to the definition of software problem? Meaning they can include the things that I’ve listed?

]]> By: Tony Morris http://blog.tmorris.net/java-and-practicality/#comment-44832 Tony Morris Sun, 29 Aug 2010 05:15:07 +0000 http://blog.tmorris.net/?p=797#comment-44832 jih276, Yes definitely. If you ask those questions and you answer "Java", then you are wrong -- at least to the extent that I have seen. In most cases not only are you wrong, but you have just introduced yet more problems, not a viable or practical solution. This is especially true of your last two questions. jih276,
Yes definitely. If you ask those questions and you answer “Java”, then you are wrong — at least to the extent that I have seen. In most cases not only are you wrong, but you have just introduced yet more problems, not a viable or practical solution. This is especially true of your last two questions.

]]> By: jlh276 http://blog.tmorris.net/java-and-practicality/#comment-44830 jlh276 Sun, 29 Aug 2010 04:32:21 +0000 http://blog.tmorris.net/?p=797#comment-44830 Hi Tony, When you say "a problem specific to software"? Does that include or exclude things like problems I could encounter while trying to use system X to retrieve and process data taken from a system A to insert it in system B? There are ranges of "problems" that I can encounter. For instance: - what software is available on A, B and X and what choice I have to modify their runtime environments - what API (or services) are provided by A and B - how much computer power I have on X - what kind of data do I need to process (XML, table-like, ...) - budget or are available to provide a working solution to this problem - budget or what people are available to support the solution Most of the things I listed are probably not "software problems". Yet they contribute to a large extent on why Java is a "practical" tool in this kind of problem solving where software is part of the problem and where there are another bunch of factors. For some definition of software problem that is more narrow, then it's quite likely that Java would not be a contender. Hi Tony,

When you say “a problem specific to software”? Does that include or exclude things like problems I could encounter while trying to use system X to retrieve and process data taken from a system A to insert it in system B? There are ranges of “problems” that I can encounter. For instance:
- what software is available on A, B and X and what choice I have to modify their runtime environments
- what API (or services) are provided by A and B
- how much computer power I have on X
- what kind of data do I need to process (XML, table-like, …)
- budget or are available to provide a working solution to this problem
- budget or what people are available to support the solution

Most of the things I listed are probably not “software problems”. Yet they contribute to a large extent on why Java is a “practical” tool in this kind of problem solving where software is part of the problem and where there are another bunch of factors.

For some definition of software problem that is more narrow, then it’s quite likely that Java would not be a contender.

]]>