Software Fashion
fedor writes "Software fashions come and go, but they always claim a few victims on the way. Where there's fashion, you'll find that rather weak willed person who is the Stupid Fashion Victim (or the SFV for short).
This great article from Software Reality is all about fashion in software. Do you all remember WAP? In a couple of years some of the current 'technologies' will be gone too. The article mentions VB.NET, struts and XP as current fashion..."
My vote is the
Runner-up: The adventure games a'la Sierra's.
45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
I'd like to nominate collections frameworks as another fad that obviously didn't get the word that it should die. Painfully.
You take one look at Java Collections, and see a slew of overspecialized subclasses of underspecalized abstract root classes, so that its hard to do a key-pair lookup without writing one yourself, which defeats the purpose of the Java framework! </rant>
#define DRM chmod 000
No, they were refering to that one Italian programmer who was supposed to be the next big thing.
It eventually got to the point that we were getting very little work done, because we were always changing things in mid-development to appease her insane demands. Finally, our group got together, and formulated a formal plan for dealing with her insane requests.
We implimented the plan, and have not had any problems ever since.
Our team project manager put together a pretty good summary of what the plan entailed, which can be found here
I think you are over critical of OO. Sure if you are doing anything in the systems area, OO may not be the answer for you. However, OO abstraction is so much more than "fancy structs". OO, if use effectively, can help us create highly complex software systems that are highly adaptable, reusable, and understandable. Using design patterns (only as needed of course), one can communicate a design with a much more concise description. Properly design inheritance and composition relationships can help a piece of software acheive better longevity.
OO is really a natural progression to structured programming. Sure it may not be the "Silver Bullet" but it certainly is a big step.
WARNING: DO NOT CLICK LINK! JOKE IS IN DOMAIN NAME!
Most software looks like this!
WARNING: DO NOT CLICK LINK! JOKE IS IN DOMAIN NAME!
Ron Paul 2012
Yep! ANT is crazy! A weaker, multi-platform, single languange "make".
Yeah, make isn't the best, but it works, it's complete, and people use it for everything. Except Java.
Sure you could use ANT for other languages. I've yet to see it embrased for anything other than Java.
So much for the multi-platformness of Ant.
Where a single class would previously have worked just fine, EJB requires up to seven (!) classes ...
.NET code bring an 8-way box to it's knees. That code would execute faster on my digital watch! Uh-huh.
Wow, you didn't work hard enough memorizing the anti-Java propaganda sheet. It's seven files, if you count XML descriptors and perhaps a DTO.
And where a simple constructor would previously have served, EJB requires a long JNDI call.
What, can't cache the Home interface? Have you ever written an EJB in your life?
Such a program could otherwise execute quickly on a 286 8MHz, a machine less than 1/1000th as powerful as the one running the EJB. I regularly encounter shops that have huge farms of commodity boxes to run very trivial EJBs that would otherwise execute on a single box just fine.
I've seen