4 ms·

stacktrace from hell - a consequence of stacking frameworks over frameworks. This is the state of our craft as of today :(. This has nothing to do with Java as

• nnq 10y ago
  Indeed! I'm trying to convince people to follow a mantra like "Use thin not thick abstractions (this example is thick)! They are leaky anyway and the thin ones are easier to debug and plug." Unfortunately 90% of people don't grok the difference between crappy abstractions, no real abstractions at all and good thin abstractions. So we end up with this hell because we want to prevent reinventing wheels, and to keep teams of monkey pumping code without giving them change to masturbate doing architecture that they'll get wrong anyway. Hopefully functional and reactive will bring some light because as far as I see the ability to do "good quality thin-abstractions OOP" is a quality that few posses, cannot be thought and cannot be learned if you don't already have the intuitions for it. With procedural+OOP paradign most are condemned to live either in the spaghetti-code-hell or in the 1000feet-deep-stack-traces-hell (best place to see this is in "modern PHP" ecosystems: WordPress-hell vs. Zend/Symfony-hell) :|