這些年來，我們已經看到很多新的技術和語言使應用開發比以往更加令人興奮。比如Python和Ruby語言的出現，雖然不能提供突破性的功能，但是提供了一些支持的替代方式來生產軟件。Ruby on Rails，或者ROR，就是一個這樣的功能使開發者以更非凡的速度容易的進行基于web的應用開發，使得常見應用的功能開發不再那么令人痛苦。 This is a great move in the right direction, and many developers have since made the transition to such languages to further lessen the strain that was ever present with languages such as C++ or Java, but it doesn ’ t provide a be - all - and - end - all for applications development as it still means having to learn a new technology. What ’ s more, despite the surge of new technologies that have been appearing, you can see that they are only really of benefit to desktop or server - side web development, while the client side for web applications remain firm with Flash, HTML, JavaScript, and VBScript, for the simple reason that older browser technologies have a greater coverage on users ’ machines. This means that, while we now have a larger choice of tools for creating our applications, we are perhaps further segregating our development team members and forcing possible rifts into our software stability and production timescales. So why are we suffering these issues and what can be done to dispose of these rifts we keep making for ourselves while continuing to embrace technology developments? The issues here are not about how such technologies interact, or about the functionality they provide, but about how we develop for them. 想一想這些。 If humans, like technology, needed to interact with one another, we would use an agreed form of communication; written English in the case of this book. If we were to seek employment in a country whose entire population didn ’ t speak our language, we are sure this would hinder our progress very much, as it would be hard enough to even convey that we were seeking employment, let alone be capable of performing many of the available work positions on offer. Yet, in respect of many programming languages and technologies available, they often communicate very well with each other using processes of their own, but the way in which we interact with them can be very diverse. When new languages are created, the syntax they support is often chosen to reflect the flavor of programmer the language is likely to attract, the features the language provides, the structure of the compiler, and the general taste of the language ’ s author, to name a few. 然而，一個編譯工具通常只是一個巧妙地程序，分析你的代碼并轉換它為一個更加機器可讀的語法，所以它只是盡可能可信的創建一個編譯工具可以實現從一種語言到另一種。一個編譯器這正是Nicolas Cannasse思考的，并促使他創造Haxe編譯器的問題。