Linked by Thom Holwerda on Mon 3rd Sep 2012 20:46 UTC, submitted by MOS6510
General Development I like this one: "By definition, a program is an entity that is run by the computer. It talks directly to the CPU and the OS. Code that does not talk directly to the CPU and the OS, but is instead run by some other program that does talk directly to the CPU and the OS, is not a program; it's a script." Here's the other eleven.
Thread beginning with comment 533839
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: C++
by satsujinka on Tue 4th Sep 2012 17:36 UTC in reply to "RE[4]: C++"
satsujinka
Member since:
2010-03-11

All those containers are duplicates of other containers in the STL. Also, Boost is a nightmare, not a benefit.

If you can't manage an array, then you have no right to be talking about "complicated things." Arrays are not difficult things to work with. Push, pop, insert, and delete are all straight forward functions (that C should have defined, but I digress.) Keeping track of the length is also not difficult (and can be managed by the push/pop/insert/delete functions.)

GUI programming is not crazy because it's complicated, it simply isn't complicated. It's tedious. But more to the point, the current style of GUI programming is crazy because it ignores good coding conventions )such as reduction of coupling.) This is practically a requirement of most GUI frameworks, because they insist on ignoring the fact that they're dealing with a reactive system. Instead of making themselves reactive, they use the event model (which only poorly emulates the desired properties, because it requires explicit handling of events.)

Reply Parent Score: 1

RE[6]: C++
by kwan_e on Tue 4th Sep 2012 23:31 in reply to "RE[5]: C++"
kwan_e Member since:
2007-02-18

All those containers are duplicates of other containers in the STL. Also, Boost is a nightmare, not a benefit.


Only because it's obvious you have no idea how to code C++ properly.

If you can't manage an array, then you have no right to be talking about "complicated things." Arrays are not difficult things to work with. Push, pop, insert, and delete are all straight forward functions (that C should have defined, but I digress.) Keeping track of the length is also not difficult (and can be managed by the push/pop/insert/delete functions.)


And yet the number one security defect continues to be caused by buffer overruns and other low level array management. It's not about difficulty, it's about SAFETY.

If you're more concerned about bragging rights rather than doing the Right Thing, you have no right to be programming for a job at all. Why the hell should people waste time writing the same array management stuff over and over again, introducing bugs (even the best of us still do), when we already have a library that does it.

Reply Parent Score: 4

RE[7]: C++
by satsujinka on Wed 5th Sep 2012 05:40 in reply to "RE[6]: C++"
satsujinka Member since:
2010-03-11

Sets, queues, and stacks are all lists. They have slight restrictions, but that's the very definition of "minimal change." Boost is quite commonly regarded as a major example of terrible software (by the non-C++ using community.)

It is about difficulty, because I've already enumerated how to use arrays safely. Pointing out that lots of developers have bad habits is simply a red herring. I've already mentioned that I wish array manipulation had been included in the stdlib, but you can find/make a library for it as well. The only reason that buffer overflows are still so common is that many developers have NIH syndrome (or are simply ignorant about what's available to them, a problem that C++ doesn't solve.)

Reply Parent Score: 1