You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Unless "grandmother" and "child" are not by age, but by activity of mind. For many who successfully use all the possibilities of modern realities, much more than the "advanced youth"
And why should you "use all the features" if you need exactly one of them for your specific needs? It is a salesman's position to list lots and lots of possibilities. It has been known for a long time that special solutions are more efficient than universal ones.
Cutting bread at home is more effective with a big knife with one blade than with universal one with 9 items, including fork and corkscrew. Not when you're camping.
You can write your own database in any language, but there are also DBMSs that work well with databases and do not implement photo editing capabilities in any way. For large databases, they are usually more efficient than general-purpose languages. But you can also do a small database in Excel. Whichever tool suits you best, that's the one you need.
When reporting on a business trip, look at the toolkit of a young accountant who has easily mastered the flagship Android - she doesn't use it, although it has a calculator too, but a specially weighted calculator lying on her desk, larger than Android (which also has a calculator) with a minimal set of big buttons. No buttons with trigonometric functions, which, however, would be needed in a schoolboy's calculator.
Where it makes sense to apply OOP, that's where it should be applied. It seems obvious. But what should the MQL language be used for?
Perhaps it is intended for organizing the interface with the user? The Visual Components Library in Delphi is one of a kind. Expert Advisors and scripts are intended to replace the human being on the computer, this interface is in direct conflict with their purpose. That is, it is in the way. Just like unnecessary items in a penknife. Or a nailer on the end of the steel handle of a universal hammer - it not only scratches, but also shifts the centre of gravity from the striker to the handle.
What kind of specialisation is really required of an MQL? This language must implement what is impossible with other tools. That is receiving data from the server and sending requests to the server. With the ability to pass the information to external programs. Let anyone can implement OOP, or bottom-up or top-down development, or extreme programming, or visual programming, etc., in the universal development tools in any way he/she wishes.
I would be glad if instead of OOP in MQL5 there would be a possibility to find out broker's commission programmatically. It is lacking and the commission is known in the terminal. This is, in my opinion, an obvious flaw.
Also, somehow it came to mind.
If anyone is willing, you could write a good article with an example for beginners on this piece of slag, how not to program.
Reg Konow, sorry for the criticism.
Look, I'd answer you now, but you'll get banned. To put it mildly - you show your results, then you'll talk about slag.
He once said that there would be no ticks with locs in mt5 as a matter of principle. Even got people banned for discussing it. So?
It's not a question for me, ask the source directly.
I don't see the point. Besides, it was a rhetorical question.
If we talk about the user, MetaQuotes has done a lot to accustom the user to the features of MT5.
Remember what was MT4 before 230 build (the last build I remember was decompiled).
And now MT4 is almost indistinguishable from MT5, even though they have a different architecture. All this was done for users to bother their dillings requiring switching, and this switching will be comfortable, same buttons, same functions, all in the same folders.
Because the dillings themselves do not want to leave their comfort zone. They do not want to, so they have to pay more money for it, the license on MT5 will be more expensive than on MT4.
And here we suddenly get into the field of licensed products pricing, so I am going to stop talking about it, because it is like counting other people's money.
In order to have your own opinion in this section of business you need to have experience in selling at least one product for more than $100K.
Of course, for an experienced programmer and developer, MQL5 is nothing. But think of newcomers and self-taught people who want to master programming just to implement their "genius" strategies. And they will find it hard to master the additional features, and when choosing a platform, they are unlikely to think too much. That is the problem.
What's the problem for a self-taught novice? This post is written by a self-taught beginner. After mql4 it took me 2-3 weeks to write my first indicator in mql5. I have only been improving my knowledge.
What kind of tricks are we talking about? The functions that in OOP are called methods, or the overloading of functions? After all, in mql5, you can do without the classes at all, no one forbids it. Well, if you're talking about those who can't figure it out, well... If it doesn't concern you, remember V.S. Vysotsky.
and straight into freelancing.
Everything is much simpler. No one forbids to write in procedural style in mql4 and mql5 - it is exactly the same. As well as with the use of OOP - in both cases.
Peter just made up a problem and prays for it. Most likely because he himself is unable to understand it. Or maybe it's because he likes to overcome difficulties and difficulties. Of the two paths that lead to the same result, he chooses the long and thorny one. But then he feels like a cool programmer. I think this is the reason behind his aversion to OOP. I could be wrong of course, but I usually feel people.
For example, I hate inludes in the form of libraries, because I'm not sure what's stuffed in them and how it may help me, it's easier to write a dozen functions
similar to the one for Retug Konow.
Well, the law of conservation of energy: why decompile the library and understand it if everything works without it?
P.S.
Have you seen my top about moose?
The first differs from the second in length. And the meaning is equally clear.
What is easier to read - concise code or a two-screen wide sprawl?
It's easier and faster for me to read a short code. If you like moving the code horizontally with the slider on each line - go ahead and do it, who forbids you.
I've seen such code from a beginner - I almost lost my eyes and refused to look into it until he renames his
"Variable for storing total profits of PositionsSelected byMagic" to
"profit_all_by_magic";
1. the_chart_id can be read by a Russian-speaking person faster than m_chart_id.
2. If there are hundreds of variables in a program, Russian provides indispensable support.
All this can be tested in an experiment.
The speed of reading and comprehending code in the native language will always be faster and the memorization will be better.
You just need to work out the rules of variable naming in Russian. Instead of "variable_to_hold_general_profit_position, just: general_profit.
If you give your grandmother a flagship iPhone or Android to replace her broken push-button phone and try to explain all the new features compared to her old phone, then 90 percent of the time she'll say that her old phone was better, because it had buttons and you could feel with your fingers what button you pressed. And I think the maximum achievement for her, except for making calls will be to learn how to send SMS, particularly gifted grandmother may even be able to teach you to Whatsapp. Everything else will look like a "fifth wheel" to her. And it will be easier for her to ask someone on the street how to get to Lizyukov Street than to open Google maps. For the power of habit is immense!
You are good at finding arguments, Nikolay).
Grandmother may also grasp everything without any problems. She just subconsciously does not want some trinket to drag her staid mind into the whirlpool of unnecessary information. She's right).
And why should you "use all the features" if you need exactly one of them for your specific needs? It is a salesman's position to list lots and lots of possibilities. It has been known for a long time that special solutions are more effective than universal ones.
Cutting bread at home is more effective with a big knife with one blade than with universal one with 9 items, including fork and corkscrew. Not when you're camping.
You can write your own database in any language, but there are also DBMSs that work well with databases and do not implement photo editing capabilities in any way. For large databases, they are usually more efficient than general-purpose languages. But you can also do a small database in Excel. Whichever tool suits you best, that's the one you need.
When reporting on a business trip, look at the toolkit of a young accountant who has easily mastered the flagship Android - she doesn't use it, although it has a calculator too, but a specially weighted calculator lying on her desk, larger than Android (which also has a calculator) with a minimal set of big buttons. No buttons with trigonometric functions, which, however, would be needed in a schoolboy's calculator.
Where it makes sense to apply OOP, that's where it should be applied. It seems obvious. But what should the MQL language be used for?
Perhaps it is intended for organizing the interface with the user? The Visual Components Library in Delphi is one of a kind. Expert Advisors and scripts are intended to replace the human being on the computer, this interface is in direct conflict with their purpose. That is, it is in the way. Just like unnecessary items in a penknife. Or a nailer on the end of the steel handle of a universal hammer - it not only scratches, but also shifts the centre of gravity from the striker to the handle.
What kind of specialisation is really required of an MQL? This language must implement what is impossible with other tools. That is receiving data from the server and sending requests to the server. With the ability to pass the information to external programs. Let anyone can implement OOP, or bottom-up or top-down development, or extreme programming, or visual programming, etc., in a universal development tool.
I would be glad if instead of OOP MQL5 included the possibility to find out brokerage companies' commission programmatically. It is not enough, and we know the commission in the terminal. This, in my opinion, is an obvious defect.