It's amusing how the times have changed. Back in 2002, you couldn't get a job unless you wrote "object oriented code" in your resume. Nowadays, state is evil

It's amusing how the times have changed. Back in 2002, you couldn't get a job unless you wrote "object oriented code" in your resume. Nowadays, state is evil (pun intented) and OO is the naughty child - "Bro, do you even write functional?", yet no one writes haskell (neither do I). Seeing articles like these for 2006 trying to shoe-horn Objects in C is amusing! This is not a nostalgic post about the gool ol' days, today we know so much more about what works and what doesn't in large applications. State _is_ bad and should be encapsulated. Pure functions are your friend. Objects... egh. We don't talk about objects, we refer to them as "this guy".