What architectures / improvements / patterns would you like to see burning in hell? [closed]

As it currently stands, this开发者_运维百科 question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 13 years ago.

While developing software, developers always tend to curse about some language specifics, "improvements" that made language less understandable, buggy.

What obstacles / improvements have you met, that you'd be pleased no one ever invented / introduced?

My 2 cents:

I cursed for 3 days at delphi 2009. I had an internal compiler error, with no clue what I was doing wrong. It turned out I couldn't inherit a Generic class declared in another unit.

---

Python. Because whitespace shouldn't be meaningful except where absolutely necessary. :-D *ducks*

C++. A nasty hack on top of C to allow OOP, resulting in horrific syntax and a lack of garbage collection, instead of the ground-up redesign needed for OOP like Java or C#. *ducks again*

MUMPS. The name says it all.

Perl5's OOP infrastructure - feels like a nasty hack on top of a language that wasn't originally intended to be OOP.

---

Singleton Pattern (also known as Global Variable in Disguise Pattern).

---

n-Tiered design. The next time I inherit a "solution" that contains a functionally empty "BusinessObjects" project, I'm going to strangle someone. I'm amazed that this pattern is still so prevalent 15 years after I first encountered it. As I said in another answer, layering is great for lasagna, but it isn't automatically a good choice for all software.

http://thedailywtf.com/articles/the-mythical-business-layer.aspx

---

Big Ball of Mud architectures, although in that case it's more a lack of invention rather than a new one.

---

Big Design Up Front

---

Any and all "improvments" to BASIC. BASIC was a broken thing from the start. VB was an attempt to fix it but -- FAIL. Then VB.Net was made, so that by the time people realized the mess that they were in, they'd be knee deep in hell.

---

To be honest I would like to see Java burning in Hell or at least they should create a complete remake of it (I know there is already one called C#).