Generalized Rant Thread

Miscellaneous Topics
#81

Let me do a optimization summary:

  1. Engineering time is the most valuable resource.
  2. Optimization is really about attempting to meet a set of goals with some metric for success. Not really those set of things that ideally your language and compiler should ideally be able to do auto-magically do for you. Those are ideally “compiler optimizations”. When one is attempting to beat their compiler and/or hold its hand, then best case situations one can only expect very small localized linear time increases and should be avoided unless exactly known to be necessary.
  3. Performing any task has an associated opportunity cost of twice the amount of time spent performing it.
  4. On considering speed increases, then the most important are algorithmic and data-structure oriented at the high level. And of these the most important are both non-linear and one that if a “bad” choice is made, then changing to a better option requires significant engineering time. Simple example: attempt to go from an unstructured world to some set of spatial partitioning.
  5. “premature optimization” is IMHO an oxymoron. This is because “no reasonable goal” is being moved toward. It is simply one example of wasting time. All of which are equally bad.
#82

Wow post cool guys hi.

#83

“Hi guys, cool post! Wow!” meant you suppose I. :o

#84

Doing of the thing that you talk to says I don’t.

#85

Why is that?

#86

Is it just me or does everybody have a tattoo to, you know, express their individuality?

#87

My individuality is divided.

#88

I express mine by not having a tattoo ;D

#89

I also liked things like the BMW ad, on broadcast TV and an audience of millions: “You are one in a million. And you want your car to be, too.”

Or something like that. There are continual variations on the theme and they always make me laugh.

#90

You’re one in a million. That means there’s seven thousand people exactly like you.

#91

That’s quite an assumption, that there aren’t more, there are plenty planets and universes out there.

#92

Yes, but they wouldn’t be people, would they? :persecutioncomplex:

#93

Well they wouldn’t exactly be human unless somehow they went through the same evolutionary steps.

#94

From Roquen’s Dictionary of Computer Science:

interface (java): A type definition designed to allow multiple inheritance of type to address cross-cutting concerns in some set of two or more otherwise distinct types. In practice however it is most often used to address the fact that java doesn’t support C/C++ header files. Another unintended usage includes design-by-composition, without using, ya know, the composition part.

#95

And I’m -so- glad this is the case. Everything relating to a class in one source file, not two or more that are scattered all over the place. Absolutely loving it.

#96

One of the best features of Java IMHO :slight_smile:

Cas :slight_smile:

#97

@gimbal: Ah, but you (currently) can’t break one type into two using interfaces…you have to use at least three. If you’re only breaking into two, then the size of one doesn’t decrease.

(Oh, add added more to my definition)

#98

So, you’re really going to love defender methods then?! :stuck_out_tongue:

#99

Personally I think defender methods are awesome.

#100

So do I! However, they do scatter code around a bit more, which @gimbal said he doesn’t like - worth it in my opinion.