I want to ask, if you make an application completely creating an interface from scratch, I use only standard Parents, then in what environment will this be done better?

Closed due to the fact that it is necessary to reformulate the question so that you can give an objectively correct answer to the party Nofate ♦ 28 Dec '16 at 11:12 .

The question gives rise to endless debates and discussions based not on knowledge, but on opinions. To get an answer, rephrase your question so that it can be given an unambiguously correct answer, or delete the question altogether. If the question can be reformulated according to the rules set out in the certificate , edit it .

  • Standard parenta - meaning without the use of add. libraries? Those. naked winapi? Well, this is a shoot in the head. Most likely it will be easiest to use C ++, because There are more examples of use. - gecube
  • In general, the question is asked incorrectly. Correctly so C ++ or Pascal or Visual C ++ or Delphi. - stanislav

5 answers 5

With Delphi not familiar!

There are some advantages to using pluses :)

First, knowing C ++, it is possible to use a large number of different libraries, be it GUI, multitriding, or network development. In addition, (in my opinion) C ++ has more community and more potential than Delphi.

Secondly. Regarding the guides and pros: here are the titles of books on Qt . I am sure that the software developed on it will be of higher quality than Delphi, and even pure WinAPI. In addition, applications created using C ++ / Qt can be recompiled and they will work without problems on both MacOSX and Linux.

  • Well, the dolphin had one serious trump card. Under the name Kylix. But he rested in Bose = (There is still Lazarus, with which there is limited compatibility. On the other hand, the ObjectPascal language used in Delphi is a little more sparing for non-pro-programmers. Because in the present C ++ a lot of pitfalls. Although I would also write it on C ++ / Qt. - gecube
  • Delphi seems to have launched a new trump card. The latest version of XE2, apparently, offers development for Windows and OS X. - Nofate ♦
  • 3
    After a couple of years on delphi in C ++, I saw not pitfalls, but three cars of a zapadlo, as if they had been specifically shoved by the community there. You write a piece of code for a book, but it is platform-specific, wants three libraries (you can only recognize them by undefined variables), which are scattered all over the world and one of them is incompatible in versions, and the other is written in Spanish. Its great fun. And here you need not professionalism, but a great desire for sex at least somewhere. I have enough of it, so I didn’t like it)) In general, I’m for Delphi, if you don’t need the “newest developments”. All IMHO, did not want to offend anyone. - Sh4dow

I do not agree.

It all depends on the amount of gray matter of the one who does.

and again there will be a holivar that is cooler than C ++ or Delphi

    Summing up and expressing his opinion:

    C ++:

    1. You can use the most powerful (besides cross-platform) toolkits: Qt !!!, GTK +, xwWidgets and if you dig a lot more.
    2. Congenital crossplotform - transferring to another platform and writing the initially cross-platform code is relatively painless and obviously possible.
    3. Speed ​​†‹вЂ‹ - an order of magnitude higher than the speed of applications on Delphi and many other languages.
    4. The size of the compiled code is minimal.

    Delphi:

    1. Quick development. Ideal for simple office applications.
    2. Pretty simple debugging.
    3. MUCH less opportunity for inexperience nakosyachit in the code.
    4. LARGE amount of compiled code.
    5. Complete lack of cross-platform.
    • one
      Delphi: the size of the program on the "WinPailed Nude" is very slightly different from the size of the program on C ++ with qt. About cross-platform writing above, and usually dolphists are not focused on linux (for allergies like linuksoidov on Windows). If they make an adequate platform for makosi - we can assume that holy war has begun in the literal sense - with ++ / nix / open source vs delphi / win / corporation. Cyberpunk is now ^^ - Sh4dow
    • Pro vinapi fully agree. But, in my opinion, rarely goes to Delphi in such jungle. Many use Delphi as a RAD development environment. Stumbled quickly with a mouse, wrote an extremely clear (you make a mistake in FIG) code - and everything works. And about the size in such cases, little is thought. And about ExePack, if I'm not mistaken, it does not reduce the amount of compiled code, but only packs Exe-shnik. When it starts, unpacking to the previous volume occurs. I'm right? But, in fact, this is again the disadvantages that do not bother anyone. - Alexey Kotov
    • > rarely anyone goes into such a jungle That's exactly the main problem, and not in the environment / language. I only add controls with the mouse (not always), the rest with pens, + assembler, + optimization 3 times, etc. About packers - eem, yes, there is already my fail, did not penetrate. Thanks for the info, by the way) More, apparently, I will not use. - Sh4dow

    Delphists and sylpusists forever in confrontation, this question has tormented many. Some poured object pascal and derivative products (Delphi, BDS Delphi) with mud and scarcity, others say the opposite is that C ++ (Visual) is difficult to build information systems, as the work with Borland DB honed to the maximum. Battles of disputes I still remember between pascal workers and live supporters. If the mind is there, then in any toolkit you can create a sweet candy product that will be loved to look expensive. In general, I know both Delphi and C ++, for me they are almost equivalent. The future for c #, if we talk about application programming. If we talk about networks and the Internet, then it's time to hit the cloud technology, in 4-6 years they will flood us). The ideology of OOP is the same in the general case, but with c ++ it has more practical code, and as people rightly said, most libraries were written on it. Probably faster on c ++, although I would experiment both there and there).

      make an application completely creating an interface from scratch

      Do you mean WinAPI naked? Then, perhaps, better with ++.