8. Java vs. MS programming language

2014-05-09 Did I like Java or Microsoft [MS] programming languages?
------
Java [J2EE] has a few things (I haven't used Java since):

1. Portable on all platforms. Write codes once then you can deploy them on other platforms.

2. javadoc is well written and organized. Back to J2EE, I could write java applications quickly using javadoc to search and locate the applicable build-in classes and methods.

3. The java's swing is the disadvantage. Java didn't have the interface or tools to build UI quickly.

4. Java has garbage collector to prevent memory leaks.

5. Java (JVM) is an interpreter for all platforms --> its execution was slow.

6. Oracle bought Java. I found that several current Java tutorials were confusing or complicated. It'd be hard to review codes if they implemented as in the tutorials.

When J2EE was first introduced, the examples were better [SUN was the owner of JAVA].
----------------------------

Microsoft (MS) programming languages:

1. UI development is very easy. Just drag and drop UI components to the display and write codes behind them.

2. MS is so obsessed about OOP, I think. Even the programming language and syntax, they made those object oriented like. All components that access database must be built like an object, i.e. not easy to review or debug! Programming language should be an easy tool for developers to develop their applications. It is up to them to design their applications using OOD and OOP concepts to make applications easy to design, debug, evolve, maintain, etc.

3. MS programing language documents, web-based, were not well written or reviewed. They did not describe the functionality of a class or method. Just one line of text and no example - most of texts were identical.

4. MS tutorial is not very well designed for people who wanted to write simple applications. For example, database access and display result in a specific format OR building a web site should be common applications out there. How about TCP/IP protocol stacks - how to use those classes or methods?

5. VB is really good for small applications on a laptop or PC with ease in UI design. I liked VB 3.0, which was the first version of Visual Basic. With accompanied user guide and user manual, I was able to develop a multimedia application quickly.

6. Methods or variable settings in handling of tables or cells in a data grid were over complicated to me.

7. One thing I found strange about Microsoft was their expertise on their own MS SQL database. Microsoft provides a free tool to compare databases, but their tool was much slower than a tool provided by another company (?)

8. C# is flexible like Java with options to build UI easily.

9. MS has memory leak issues. Why don't they introduce a default method like dispose() to dispose or remove the object(s) from memory? For example, a statement myCalendar.dispose() would dispose myCalendar objects from memory. Btw, I don't know how the compiler or Windows OS would achieve this.
-------------------

Notes: Have you noticed the exception throw by all programming languages above? It is like a chain of function calls leading to the crash. It also includes "internal" function calls by the providing languages, which only confuse developers, because we don't know anything about MS programming languages [compiler] or Java internal functional calls. I even saw some MS SQL internal calls in the exception dumped.

What I learnt from PLEX-C [programming language for Ericsson's AXE] was: the data passing between components mostly caused issues. Why one calling component passed data to a built-in method successful, but others failed? For example, in database they may pass wrong data type [string or integer] in a column. I preferred something a compiler can do is: to print out calling method, receiving method and data passed at that time in the error logs or exception. Well, developers could implement parts of these things in their programs.
-----------------------

Seriously I prefer a programming language than SQL languages. For example, Transact SQL really caused me headache. I couldn't find a book about this SQL language. Developers wrote nested or combined statements with lots of select, insert, group by statements without a parenthesis. How to figure out the first SQL statement?

Btw, Microsoft SQL database does not support parenthesis, I think. Another statement was OPTION, which was at the middle of a SQL script with lots of SQL statements without "begin or end" like statement. I think, OPTION created a loop like FOR, WHILE, or DO but did not have opening or closing parenthesis. Which part of the SQL script did the OPTION statement apply to?

* I hate guessing in software application development, but I have done that too often since I started working in other industries different than cellular telephony industry.
----------------------

I guess, I only like simple or easy to understand programs. An application or system could be complex, but implementation codes must be simple to review or possible extension or modification, i.e. adding more features or debug.

No comments:

Post a Comment