[] The text is added to the translator, because some translation feels not necessarily accurate, I hope some family will correct. Contact me: edwardzhou@bit.edu.cn
When the Delphi name was just started, Delphi was a code as a strict confidential project Beta version of Borland. This project is based on Borland's Object Pascal language, which is the next-generation visual development environment on the Windows platform. After the development team experienced a 6-month in-depth study, the conceptual feasibility test and market analysis were conceptually, this code was born in the mid-1993 mid-1993. At that time, members of the Pascal Development Team made a lot of good code for new products in the Office of the R & D (Research and Development) Manager Gary Whizin. The office is not big, the development team is not big - on the R & D, Quality Management Department, Pubs [I don't know how to translate] and the market department. Anders Heilsberg, Chuck Jazdzewski, Allen Bauer, Zack Urlocker, Richard Nelson, I, there are other frequent visits to discuss this or that topic in Gary's office. This is often made to the new product, and the office will continue to continue from the office to the corridor. Borlandy has been using the "Different" product code, some and easy to book proverbs or background, let the weird name and market or product focus. The code should have no obvious relationship with the product, so that even the sneak listener heard the code mentioned in the dialogue, it is not easy to think of the products discussed. A casual code and a good code of a good code are the intrinsic essence in the latter. The most memorable thing is the code of Quattro Pro 4.0: "Buddha", it actually wants to occupy the status of Lotus! [This sentence is double: the Buddha is sitting on the lotus, and the Lotus position refers to the status of Lotus, on the one hand, the lotus seat. This sentence of this sentence: The Most Memorable for me Was The Codename for Quattro Pro 4.0: "Budda". Why? It is to assume the lotus position!] We stay in the Gary office, entangled in a variety of raising quirks. A strategic decision is introduced a few days ago - let the new Pascal products are centered on database tools and connections, so the Gary is eager to highlight the new highlights of the product and development group on the database. The product is not a small thing to the database, I remember that there was a lot of reservations for the "tarnish" Pascal tool "tarnish" Pascal, I used this idea for almost a year. This tilt is a big gambling for Borland, but Borland is very careful, preparing and implementing it. It seems that let Delphi become the database product is the Borland's Pascal tool breaks VB and C market extrusion and let Delphi become an important reason for the development tools. Gary wants to name "Oracle" to the product, which reflects the product and Oracle's SQL connection. However, "Oracle" is not satisfied with everyone. In addition to relish of Oracle and its database server products, this code itself suggests its server nature, and our products are only used to generate clients to access Oracle and other servers.
How are you talking about with God? The phrase of the "Delphi Temple" collapsed from my head! So I put forward "delphi", meaning: if you want to talk to God, go to Delphi (visit the temple)! This proposal is not a hole, Delphi is an old name, a historic place, a passionate temple on a lost civilized site. This is hard to make people ideally! Just as some articles that have been published, the method of visiting the gods through the Delphi method is famous in a certain aspect - it gives a hygienic or a variety of answers, not a good partner of the data management tool. Everyone can ask God to make the problem, but to explain (compilation) the menssenger's answer (the people in the market) expensive this). However, in general, Delphi code is classic than the other semantic dual-level names proposed in the office. Pascal is a classic programming that links a classic Greek image and a PASCAL-based development tool that makes people feel comfortable. And according to Greek legend, Delphi's temple is the least scandal. We have used many codes in the 1.0 version development engineering of the product, and the Beta version of the Beta version of the news unit and the company's briefing is fictitious. This way we can limit rumors and trace messages from He leaks. We don't want others to know something about our current product. In addition to "Delphi", other code can be discarded. When developing approaching ends and final Beta release, the marketing department began to call this product in news units and company briefings. At this point, the rumors are four, and the development tool circle is talking about the secret project of Borland's secret project "Delphi". JD Hildebrand wrote a series of comments for Windows Tech Journal (Windows Development Magazine) in Delphi, the theme is "Delphi Discussion Month" (he explained: I can't tell you what Delphi, but I can say it will change our life). When the product is going to be launched, the result of the official naming will make people feel tasteless. The functional name is AppBuilder, which indicates what the product is for easy sales. In fact, AppBuilder has appeared in the IDE (integrated development environment) as some internal class names, such as the class name of the IDE main window (the development department succumbed to functional naming requirements and started using this name early). But AppBuilder cannot stimulate the imagination, and it cannot be functionally functional in the world's world-functional names, only for users who use the same language in the world. Fortunately, before the Delphi plan, Novell's Visual AppBuilder was listed. Many people in Borland are happy, because the name of the name is finally suspended. Because the functional name is not discussed, it is more and more people in Borland tend to use Delphi as the name of the product. But Delphi is named internally, still not fully recognized. The head of the market is worried that this iconic (not functional) name is to get the market recognition, and the company needs to pay additional efforts. Because he believes this is not reasonable, he asked him to vote in the development team. But the result is only one vote (guess who?) Veto Delphi this name. What makes us angry is that someone concludes that the view of the development team cannot accurately reflect the market's requirements (what I heard is "sample is not pair"), so investigated in the beta version tester.
