Why Delphi "dies" or "programmer is not a reader, programmer is a writer"
Hello, dear habrazhiteli! Happy New Year! I wish you a successful coding, a reckless code, understanding managers, intelligent subordinates and patience in parsing the code written by the predecessor.
I want to share some thoughts about reducing the popularity of my beloved programming language - Delphi. So, let's not pull the cat by the balls, but take the bull by the horns.
In the era when Delphi was born, the personal computer began to be introduced everywhere where the benefits of its introduction could be seen. But one computer is not enough to extract benefits. There is also auser operator who works as an intermediary between business data and an information system, and the information system itself - the programs that store, process and issue these same data.
')
So, to get as much profit as possible, you need to reduce the cost of
It is because of these reasons that there are thin clients a la terminals, operators poking the right buttons in the right sequence and information systems written by students as term papers.
Object Delphi, grown from procedural Pascal, has a very low entry threshold, provides minimal dependency on third-party libraries, and provides access to data stored in various DBMSs.
If the design of the system the relationship between iron and Delphi is poorly traced, then the following three profit conditions are associated with Delphi very much.
Software component , in other words, the operating system. Delphi allows you to write programs that work in MS Windows, which gained popularity at a frantic pace - it’s not a problem to install pirated Windows. How is it there ... J3QQ4 ...
Training of operators If the operator knows the basics of working in Windows, then you can get by with a simple instruction that indicates which button to press.
The development of an information system. A low threshold of entry actually allowed a student or a group of students to write an IC in accordance with the modest requirements of the customer.
It is the low threshold of entry and played a fatal role in the fate of Delphi. My free brief retelling of how it all happened.
Thus, the main reasons for a temporary sunset Delphi:
That is, the programmers were mostly engaged in the Delphi environment and the language, but their management is lame in both legs. Everything rests on him.
If these reasons together manifest themselves in another language / technology, then we can say that it also has / will have problems. Take Silverlight for example. He also has a low threshold of entry, but on the rest of the points they have all type-top. I hope no one will argue that MS is not a major vendor or a vendor that does not support its offspring in all imaginable and unthinkable ways.
Of course for Delphi, it's not so bad. Now the language has an adequate host, the language is not shaky, it is not developing. But the trust of customers / managers is hard to return. Truth those who still remained faithful to the language, more careful. For example, when recruiting to a team, they are more thoroughly trying to identify the level of training, not chasing new releases of the language. Delphi 7.0 suits many people (like Windows XP :) They say that Gisler with Total Commander is still sitting on the second version.
For example, I will try to describe the current state of affairs in my city. A small handful of offices that know about each other, if not all, then for a long time. All, without exception, are fed from the bottomless state treasury - there are a lot of tenders for the creation of e-government. Within this framework, projects are developed mainly in C # and Java. Zoo DBMS is attached: IBM DB2, MS SQL, Oracle, FireBird. In the team: one or two hardworking gurus, 3-4 students or freshly baked graduates, two or three dead weight. What is not always different people. A team is from 2 to 10 people on 2-4 projects. On average, out of five projects: one is new, two are refinement of the old, two are incomprehensible with something, as a rule, office work (SAP, DocsVision) or commissioning and iron works.
So, almost always a new project is written either in C # or in Java. Refinement of the old - it is almost always a fine finishing / alteration / repair written in Delphi.
You look at all this and it becomes sad at heart. But read the promises of Delphi developers and take heart. And in order to help them in their difficult task, he convinced his office to purchase a couple of licenses and start one project on the fresh edition of Delphi.
IMHO, can not such a wonderful language just gulf. Be sure there are enthusiasts of the business. So many wonderful programs written on it. I want to believe that more will be written.
I, in turn, urge fans of Delphi not to be idle, but to try to popularize it in their circles. We will help some Embarcadero managers to correct their mistakes and support our favorite language.
I want to share some thoughts about reducing the popularity of my beloved programming language - Delphi. So, let's not pull the cat by the balls, but take the bull by the horns.
In the era when Delphi was born, the personal computer began to be introduced everywhere where the benefits of its introduction could be seen. But one computer is not enough to extract benefits. There is also a
')
So, to get as much profit as possible, you need to reduce the cost of
- iron component
- software component
- operator training
- information system development
It is because of these reasons that there are thin clients a la terminals, operators poking the right buttons in the right sequence and information systems written by students as term papers.
Object Delphi, grown from procedural Pascal, has a very low entry threshold, provides minimal dependency on third-party libraries, and provides access to data stored in various DBMSs.
If the design of the system the relationship between iron and Delphi is poorly traced, then the following three profit conditions are associated with Delphi very much.
Software component , in other words, the operating system. Delphi allows you to write programs that work in MS Windows, which gained popularity at a frantic pace - it’s not a problem to install pirated Windows. How is it there ... J3QQ4 ...
Training of operators If the operator knows the basics of working in Windows, then you can get by with a simple instruction that indicates which button to press.
The development of an information system. A low threshold of entry actually allowed a student or a group of students to write an IC in accordance with the modest requirements of the customer.
It is the low threshold of entry and played a fatal role in the fate of Delphi. My free brief retelling of how it all happened.
- Delphi became more and more popular, support of new DBMS is being introduced
- the number of projects implemented with Delphi is getting bigger
- the number of Delphi programmers is increasing
- the global (not only in the USSR-Russia, but also in the USA) crisis of technical personnel training begins
- requirements for information systems are complicated in accordance with the development of technology
- Delphi developers are mistaken in the direction of technology development (dotnet was not yet relevant)
- customers cannot distinguish a good Delphi programmer from a bad one - there are no certificate authorities
- the number of projects written by non-programmers is increasing
- the number of projects requiring support increases (changes in the code / logic)
- customers are increasingly hearing that "it is easier to rewrite than to fix / finish"
- and it is said as bad programmers who have not understood the code
- so good, whose hair moves from what he saw bydlokoda
- Delphi developers do not keep up with new technologies, although this is not critical, but ...
- more and more people / customers / executives start thinking that “Delphi is bad”
- Delphi competitors are not sleeping, and more and more "tasty" technology
cakes arerolling out - a good programmer no matter what to write, they “go” to another language, there are less and less good Delphi programmers
- Delphi freezes in development, brings losses, owners change one after another
- rumors about the
demise ofthe development of the language - Customers for new projects are trying to choose another language, because they are tired of rewriting the same thing from scratch, without the hope that all this will work in the future and that the project code will have support
- Universities bend under the market, Delphi are beginning to be excluded from student training programs
- Delphi is less frequently mentioned in technical circles, many
considerit tobecalled "dead"
Thus, the main reasons for a temporary sunset Delphi:
- low threshold of entry
- lack of certification centers
- management mistakes
- lack of "advertising" in the media, or rather the presence of anti-advertising
- lack of support for large vendors, unlike competitors
That is, the programmers were mostly engaged in the Delphi environment and the language, but their management is lame in both legs. Everything rests on him.
If these reasons together manifest themselves in another language / technology, then we can say that it also has / will have problems. Take Silverlight for example. He also has a low threshold of entry, but on the rest of the points they have all type-top. I hope no one will argue that MS is not a major vendor or a vendor that does not support its offspring in all imaginable and unthinkable ways.
Of course for Delphi, it's not so bad. Now the language has an adequate host, the language is not shaky, it is not developing. But the trust of customers / managers is hard to return. Truth those who still remained faithful to the language, more careful. For example, when recruiting to a team, they are more thoroughly trying to identify the level of training, not chasing new releases of the language. Delphi 7.0 suits many people (like Windows XP :) They say that Gisler with Total Commander is still sitting on the second version.
For example, I will try to describe the current state of affairs in my city. A small handful of offices that know about each other, if not all, then for a long time. All, without exception, are fed from the bottomless state treasury - there are a lot of tenders for the creation of e-government. Within this framework, projects are developed mainly in C # and Java. Zoo DBMS is attached: IBM DB2, MS SQL, Oracle, FireBird. In the team: one or two hardworking gurus, 3-4 students or freshly baked graduates, two or three dead weight. What is not always different people. A team is from 2 to 10 people on 2-4 projects. On average, out of five projects: one is new, two are refinement of the old, two are incomprehensible with something, as a rule, office work (SAP, DocsVision) or commissioning and iron works.
So, almost always a new project is written either in C # or in Java. Refinement of the old - it is almost always a fine finishing / alteration / repair written in Delphi.
You look at all this and it becomes sad at heart. But read the promises of Delphi developers and take heart. And in order to help them in their difficult task, he convinced his office to purchase a couple of licenses and start one project on the fresh edition of Delphi.
IMHO, can not such a wonderful language just gulf. Be sure there are enthusiasts of the business. So many wonderful programs written on it. I want to believe that more will be written.
I, in turn, urge fans of Delphi not to be idle, but to try to popularize it in their circles. We will help some Embarcadero managers to correct their mistakes and support our favorite language.
Source: https://habr.com/ru/post/111554/
All Articles