About ubiqx

These are the little training wheels that keep getting re-invented; the small parts in that drawer in the kitchen. It's those things that are always in your way when you're looking for something else, but are never there when you really need them. Our goal is to be the good neighbor who always seems to have the missing flange-screw or cup of sugar that you need when you're in the middle of a project.

The ubiqx^® name and the tetrahedron logo are Registered Service Marks.

Yes, that's what we provide--and we're proud of it. There's a lot of otherwise good code out there that suffers because the programmers did not sidetrack themselves trying to get some base-level undergrad CS construct working properly. This is perfectly reasonable. If you are implementing a filesharing protocol or a graphics package or a web server you probably don't want to spend time fussing with a splay tree. Been there, done that, move on.

The somewhat dismissive tone of the Freshmeat comment, however, exemplifies the problem that the ubiqx library is trying to solve. That is, many feel that these "undergrad CS" constructs are not worth the time it takes to code them up. As a result people don't build them at all, or worse (eg. linked lists), they rebuild them every time they need one instead of re-using their own code. Blech.

So, as described above, what we're trying to do (in our spare time when we're not working on what others consider to be "significant", "massive", or "trendy" projects) is to code up good-quality, re-usable, base-level foundation pebbles. The standard C libraries contain similar bits, such as the qsort() function. The ubiqx library simply provides additional tools. Don't dismiss them, use them. We've written them so you don't have to.

Share and enjoy.