Linked by Thom Holwerda on Tue 21st Sep 2010 21:32 UTC, submitted by diegocg
Qt After many months of designing, coding, reviewing, testing and documenting, Qt 4.7.0 is finally ready for the big time. Although it's a little more than nine months since Qt's last feature release (4.6.0 on December 1, 2009), the seeds of some of the new stuff in 4.7 were sown much earlier. Indeed, many of the ideas behind the biggest new feature in Qt 4.7.0, Qt Quick, were born more than two years ago, not long after Qt 4.4 was released
Thread beginning with comment 442297
To view parent comment, click here.
To read all comments associated with this story, please click here.
turrini
Member since:
2006-10-31

I am C programmer for over 20 years and never had any of the problems you mentioned above.\

The difficults that novice programmers encounter are because they don't know computing at all.

That's why they makes mistakes.
That's why they can't develop in C/C++.

A real programmer must know, MUST KNOW, the machine he is operating.

Otherwise, they keep themselves in ignorance and use .NET, Java or SomeOtherManagedAndEasyLanguage.

Edited 2010-09-23 19:19 UTC

Reply Parent Score: 3

siride Member since:
2006-01-02

Read the C++ FQA. It's not just beginner mistakes. The language is fundamentally *nasty*.

I've also done C for quite some time. I've done assembly. I even wrote my own assembler and my own virtual machine. I've done C++, Java, Perl, PHP, C# and, sigh, even VBA. I have books on operating system kernels and how the computer works on a low-level. I've taken classes in that stuff. Believe me, I'm not just saying this because I don't get pointers. I get pointers. I can deal with C++, but it's such a fscking pain and the more I use other languages, the more I find them to be considerably superior except in the performance/memory-usage department. Better, though, is to write most of your app in a managed language and write the performance critical core in C++ or another unmanaged language.

Reply Parent Score: 3

turrini Member since:
2006-10-31

C/C++ aren't nasty. They are flexible.

Programmers who can't stand flexibility, should never try C/C++, so they would never say that C is horrible or difficult.

People often say that something is horrible or not feasible when they do not understand.

We, C/C++ programmers, are very happy with our language. It's flexible, blazing fast, cientific and fantastic.

I do business programming for living too. And I code in C++.

C/C++. They fits our needs.

Reply Parent Score: 2

axilmar Member since:
2006-03-20

Better, though, is to write most of your app in a managed language and write the performance critical core in C++ or another unmanaged language.


Why waste time on going back and forth between two languages? it's counter productive.

Using a managed language when it's not required it's also a waste of resources.

Reply Parent Score: 2

nt_jerkface Member since:
2009-08-26


That's why they makes mistakes.
That's why they can't develop in C/C++.


You should work on English before any programming language so you don't sound like Skwisgaar Skwigelf.


Otherwise, they keep themselves in ignorance and use .NET, Java or SomeOtherManagedAndEasyLanguage.


RealCarpentersDontUseNailGuns.

You seem to not realize that lot of C# programmers have a C++ background. A big reason why MS used C syntax was to make it appealing to programmers with existing C/C++ experience.

Sometimes it makes sense to use managed code, sometimes it doesn't. But being completely dismissive of managed languages doesn't make any sense at all.

Watch out for those pointers, don't want to leave yet another buffer overflow exploit.

Reply Parent Score: 2

turrini Member since:
2006-10-31

English is not my native language and I don't care.
Esperanto Estos la cefa lingvo de la mondo.

Those who choose C# are lazy. Sorry, but that's the truth.

Programmers must work hard EVERY TIME. That's my oppinion.

Reply Parent Score: 1