After my last post on the之後,我在去年的後對 differences between Java and PHP development practices之間的分歧Java和PHP開發的做法 , I saw some strange notions surface in PHP developers regarding Java. ,我看到了一些奇怪的概念,表面上在PHP開發有關的Java 。 This post is an attempt to dispel some myths about Java by PHP (and other non-Java) developers.這個職位是企圖消除一些神話的Java由PHP (和其他非Java )發展。 Feel free to chime in.隨時附和英寸

Myth 1: Strong Multi-threading support makes Java complicated and lack of it (actually very primitive support using ticks) makes PHP simpler. 神話1 :強大的多線程支持,使Java的複雜性和缺乏資訊科技(其實是很原始的支持使用蜱) ,使PHP的簡單。

In Java nobody forces you to use multi-threading.在Java中沒有人勢力您使用多線程。 In JSP, which is a true cousin of PHP, much of the code is written without multi-threading.在JSP中,這是一個真實的堂弟, PHP中,大部分的代碼是書面沒有多線程。

Multi-threading is a tool, which used judiciously, can make some tasks simpler (in development) and more efficient.多線程是一種工具,使用明智的,可以作一些簡單的任務(在發展)和更有效率。 It also makes any UI seems more responsive to user.它也使任何用戶界面,似乎更敏銳的反應用戶。

With帶有 ThreadLocal threadlocal multi-threading has become much simpler even for novices.多線程已成為簡單得多,即使是生手。

Myth 2: All Java projects follows Big-Upfront-Design 神話2 :所有的Java項目如下大的前期設計
Extreme Programming is a development paradigm which professes simple design and iterative rapid development cycles (1-3 weeks).極限編程是一個發展的範式,其中自稱簡單的設計和迭代的快速發展週期( 1-3週) 。 It professes against big upfront design.它自稱對大的前期設計。 Interestingly XP is widely practiced by Java developers, more so then any other languages by a large margin.有趣的XP是廣泛實行的Java開發者,更那麼任何其他語文的大幅度。 Many projects do follow BDUF and it is the same for any other production languages.許多項目做後續bduf ,這是相同的任何其他生產語文。 Lack of architecture or design in anyway doesn’t confer greater strength to PHP or any other languages.缺乏建築或設計在無論如何並不賦予更大的力量, PHP中,或者任何其他語言。
XP succeeds because of large volumes of unit and acceptance(read regression) tests to back up the rapid changes to codebase. XP的成功,因為大量的單位和接受(閱讀回歸)測試,以備份起來,迅速改變的CODEBASE 。 Without such tests to back you up, anyone who thinks unplanned massive changes to codebase (read hacking) is a recipe for success is courting disaster.沒有這樣的測試,以回你,誰認為,無計劃的大量更改的CODEBASE (閱讀黑客入侵)是一個成功的秘訣是災難。

Pages: 1 頁數: 1 2