Sender:
COSMOSCHEN
COSMOSCHEN@bbs.openfind.com.tw)
Total:
My opinion of Java
This is only a message View: Original Format Online Forum:
Tw.bbs.comp.lang.java
Date: 2002-11-01 02:20:14 PST
Java and .NET, C quarrels are not a day two days, especially in the Java version, there will be someone to quarrel in three less than five, then everyone will hinder, or what new technology is M $ The evaluation, and then more people join the battle ...
I want to go back to the beginning of the beginning of learning OO to try to talk about the view of Java: OO is what the benefits of traditional languages: component reuse is close to the reality of the real world. This holy cup has caused many people's investment. However, entering OO is actually implicitting the logic's reorganization, from analysis, design to practice have many new topics to solve learning, why do we have oo? I believe this answer is very clear: 1. Reduce the problem of solving the problem, II, simplify future maintenance time, three, use the fine program code.
There are many technologies, Java is not the first, I believe that it will not be the last answer to some of the new C OO problems. The reason why I personal preference Java is: sun pays attention to good architecture, and on the product Provide many different options, will not be tied by specific vendors or technology, and Java is simplified!
As the saying goes, "There is a good two good two good", good architectural specifications can help us simplify the maintenance time, but to learn the architecture specifications but also take time; simplified programming designers often mean that there must be more running platforms to provide more The system service, thereby reducing the performance efficiency; the specification does not lock the product representative, but at the same time, the technique of the technique is in turn, but there is a difficult thing to enter because of the five flowers.
But this is only the previous investment. After we learned the "foundation" Java language API syntax, the huge architecture behind it, the design specifications have just begun, we also have powder multi-way: J2EE is an example, providing business logic The components are independent and achieved high reuse. I think many people only look at the EJB to be divided into home / transte / bean / dd, do not mention EJB and session / entity / message driven's different applications, plus weblogic / WebSphere ... These manufacturers Technology is compatible, but there are some slight differences in practice to overcome, so many people will want to shout: "Give me a shortcut!"
This is also the problem that I have been constantly complaining when I just learned Java: I haven't had many Chinese books in Java. Just Java 2 is launched, the new and old technologies are crossing, and the original instruments don't know which version is good, and MS There is an official version of the finalized, and a free MSDN is enough. You see the old dealer, but also don't mention the MS high-end marketing technique with gorgeous product packaging, one .NET is called "cross-language, platform, service Promise, let me really want to transfer the impulse of MS camp, really preventing my transition from the reason for: .NET's product time course with closedness, causing conflicts with the above one, two, three points.
Personally did not criticize any platform, currently learning .NET related technologies, but I am constantly recalling these problems and asks you: I really wait until someone else solves the problem, can I get my own problem? - Of course, let me support my family The process is relaxed - the actual version of .NET continues to be revised, constantly follow the so-called "slogan" change direction, from ASP.NET/C#/J # to Framewrok, these say that it is good to make progress, saying that the truth is torture, Technology is of course hoping that the product has begun to study in a mature stage, but the market, the boss is not tasted, so I accept these trials. Take a look at Java, from 1999 J2EE to now three years, Java does not specifically declares what problems have been solved, but I have learned from the Java platform from a personal point of view: 1. Architecture assisted development Under the independence of many people; Second, the concise province of language has identified the spread of the wrong rotten stall; III, the component design emphasizes the re-use and maintenance challenge, which is why personal or very happy Java factors, even In the future, add new technologies - like the nearest Web Service - Java good architecture allows her to have a good entry point in design solutions, and will not take a whole body, everyone will watch servlet / jsp These J2EE technologies have been used as an example. It has the specifications of the Java API. It is not difficult to enter these areas. It has a good OO concept, and then look at the design concept of these components is relatively easy. You are willing to take the previous period. Is the return of the return of the investment?
Then look at the performance of Java has been constantly being diseased, and the personal opinion here is: In order to develop, simplify maintenance, re-use components, how is it slower? What's more than Java's performance in * NIX is much faster than the MS platform. If you still feel slow, change your job platform or deployment to parallel-processed server arrays? These jobs have not been discussed on .NET - interested in trying the frame MS Cluster Server - I don't mention optimization to process these programs, because this is the above two can be taken.
Let's talk about OO's other part of OOA / OOD / Design Pattern and Refactoring, whether you are familiar with or not, these technologies are "faster and more easier" solutions for development work, but these areas also have super high entry threshold. With the learning curve, the same old saying: Are you willing to take the previous investment? It is not difficult to use Java to do these technologies, and Java itself has also applied many of these technologies, and has been in many years. Of course, .NET is also, but I can't see MS sincerity: Because the high change in the current stage makes her unwilling to put forward these issues at this time, this also represents the future potential trap of the middle market: a rush How many consequences will be taken behind by the technical specifications of certain slogans, this is given to everyone to think.
Taiwan's market is biased towards small and medium-sized development, because Taiwan companies themselves are small and medium-sized, there are many past discussions in rapid development and simple applications, this is not very good, about this, I am very simple: " Why do you want to use a cow knife? "If you want to use Perl / PHP; you want to operate at high speed, please use C; you want to pursue efficiency, please exchange Assembly, the consequence is: If you have the next version - if you exist - then you Time spent in the revision may be equivalent to the time of rewriting, the last time I mention the old saying: Are you willing to take the previous investment? If you think: please take a time to look at the topic of architecture, system, design, analysis, reuse, and Java may be the easiest introduction of the current application and learn to take a good choice for making money. -
