Which library/framework did you ditch as being too complex for the problem it is solving? [closed]

Question

... and coded the functionality "manually"?

As a rather metaphorical example, you'd hardly need a library for solving quadratic equations, although such libraries do exist and someone takes them seriously.

As a more questionable case, depending on the circumstances I may ditch jQuery (for example when I don't need to support some stone age browsers): it does simplify some things but it adds another layer of complexity and unreliability to DOM. And overusing jQuery leads to absurd problems, such as one seen recently on SO: how do I assign an empty href to an a tag with jQuery? Turned out it was a HTML question, not even JavaScript.

Another absurd case and yet non-obvious for many is using some templating engine/language built on top of another templating system: PHP. Third level of templating anyone?

And another one: sometimes just spitting out XML with (figurally) printf is far easier than doing it with some monstrous XML engine.

Any other cases from your experience?

Answer 1

Much of MS enterprise library and most 3rd party controls for .net have left me with this feeling after a bit of use.

Your mileage may vary

Answer 2

Windows Communication Foundation

The fact that it's got a picture of a Swiss Army knife on the homepage kind of sums it all up for me. Imagine the XML configuration is about four times as long as the actual code that you write, and it's still very difficult to write SOAP services that are interoperable between C#, Java, PHP, Python and all those other languages that it was "supposed to" be interoperable with...

In all future projects, I'm just going to stick with REST.

Answer 3

One of the problems I've experienced with people "rolling their own" is that -- while their approach is often faster and simpler -- it is also more likely to be brittle, have bugs, be incomplete, and/or contain security flaws.

Simple example: it might be 10 times easier to use printf to emit XML than to use a library:

printf("<xml>%s</xml>", str);

but did you remember to escape special characters in str? For example '<' and '&'? Some people might say "no I didn't" and proceed to write this:

printf("<xml><![CDATA[%s]]></xml>", str);

But it'll still emit broken XML if str contains the substring "]]>" anywhere in it. Edge case -- sure. But still a valid scenario which could lead to unexpected problems with serious consequences.

There are many times and places where "rolling your own" may be appropriate, but it sometimes takes a lot of experience and knowledge to identify when it is appropriate. That is why I often encourage junior programmers to prefer using established libraries (where available) instead of self-implemented routines.

Answer 4

Log4Net

The library is good, but the documentation is horrendous. It was overkill for what I wanted to do.

I used Trace instead.

Answer 5

SharePoint

Don't get me wrong, SharePoint is awesome if you need most of the things it comes with (and it comes with a lot!), but if you don't know what you're doing or only need it for one or two things, it is MASSIVELY not worth the effort and configuration.

Answer 6

ASP.NET WebForms - Although as .NET web developer it's been my bread and butter for a long time, since I started using the MVC framework (and coming from a PHP / Smarty Template environment) -- you realize that sometimes there are just better ways to do web development and the abstraction that it uses is overkill and leaky.

Answer 7

Not that Delphi4PHP needs any bad press, but I tried it (version 2.0) and it was extremely hard to bend it to my will. I wanted to use it to make a youtube style web app for clients to view training videos, but it was too cumbersome and when I tried it to combine PHP frameworks (VCL4PHP, Zend, Smarty and Recess) I ran into the inevitable, gotta rename everything because there's no namespaces in PHP 5 problem.

That being said, I didn't roll my own in the end. I used just learned from my mistakes and decided to keep it very simple and use CodeIgniter and FlowPlayer (with JQuery).

I've got a hankering that whatever frameworks make it out of PHP 5 alive, PHP 6 is going to have some awesome frameworks which might actually play nice together.

Answer 8

Weka

I do a lot of machine learning work, and if I ever just need something simple like Naive Bayes or logistic regression, I love ditching Weka. It has good implementations of some fairly complicated machine learning algorithms, but the API is a crufty overengineered excessively object-oriented old-school (pre-generics) Java API. Things that annoy me about it:

1. It rolls its own resizeable array that nothing else uses, guaranteeing busywork converting back and forth.

2. Lots of sequential coupling where methods have to be called in a specific order and unless you really RTFM carefully, you won't realize it.

3. Every instance has to be an Instance object, and I have to declare explicitly with an Attribute object whether it's nominal or numeric. This leads to lots of busywork converting data to the form Weka wants. This is especially annoying since the Weka API throws so many exceptions that code compiling does not mean it's likely to work anyhow. If I were designing the API, I'd be liberal in what I accepted (maybe just take an array of Object) and just introspect the data to figure out what I got and what the right thing to do with it is.

Answer 9

In almost every case I've done this, I've ended up regretting it:

• Using the PHP oci_* functions instead of a wrapper library turned out to be a bad move because of code maintainability. Porting all the code to Zend_Db made developing maintaining the database code much easier.
• Rolling my own ajax grid component, which took up too much time to develop further, given how fast some of the other grid components evolve. I'm currently porting it all to Ext JS grids because with those there's a huge mass of third-party functionality available.
• Avoiding libraries like prototype and jquery led to repeated occurrences of cross-browser issues, often hard to track down. The Ext JS port has solved my cross-browser woes. It is magic, even if it is a vast framework that took me weeks to understand.

I've come to the conclusion that it's much better to pick a few reliable third party frameworks, and use them as the foundation for everything you do. Those frameworks are developed and debugged by someone else, which is an incredible time-saver once you've standardized on them and understand them well.

Answer 10

Spitting out HTML on a debug port on an app. I needed some simple way to get some current data (with automatic refreshing). Pulling in a library to format it would have been good, but it was easier to just printf it.

I've also rejected on library for another: We use a large, complex XML library in most of our stuff. After spending 4 hours one day trying to get it working in a new app, I just said 'bag it', and pulled in TinyXML. It's no where near as powerful, but it takes a LOT less effort to make it do simple stuff.

Answer 11

Recently I've been working on a scripting language compiler that I can use within my applications. I've used others, but none do exactly what I need them to do. So I figured why not try to write my own? It may be a year or two before its really suitable for general use, but thats ok. Plus, its a great learning experience.

Another 'roll my own' solution is the pieces used to translate my applications. There's existing libraries, but I didnt like any of them. So I made my own.

And Delphi's database components. I hate'em. Always have. So I made my own database interface that works the way I want one to work (and exactly as the one I made for PHP works, making coding across languages easier).

Basically, when given an option, I typically end up making my own library.

Answer 12

System.Text.RegularExpressions

Regex is so complex and so slow. I'll very rarely use Regex and usually write my own text parsing and matching.

Occasionally I'll find Regex useful for really complex matching.

Answer 13

On a particular project I ditched EJB3. It gave me dependency injection and container managed transaction handling. But it introduces huge dependencies (e.g. JBoss) and made the system difficult to write automated tests for. Now I've stripped it down to JPA + constructor dependency injection.

Answer 14

Ohhh, so many. I've worked on quite a few agile projects using open source apis. Great when they work, but often we have suffered developers with a fetish for bringing in all sorts of 3rd party apis, some obscure, some not, just because they want to use one or two classes in them. The end result being a mish-mash of code and hacked together systems. They hand it over claiming it's the best code ever, leave and the poor slobs who pick it up find an unintelligible, undocumented mess full of dependency issues and hacks.