Older blog entries for etrepum (starting at number 30)

titus: You should just put the library in your source file list. That way you get depends functionality, and you're guaranteed that the library you're linking in is the one you're "depending" on. GCC's linker is dumb -- better to tell it precisely what file you want.

titus: Platypus is not what you want for packaging Python applications. You want to use py2app, or at worst case, the standard library bundlebuilder.

jluke: Maybe you should blame the application developers, and not the programming language. I've seen good applications written in Perl and bad applications written in Java.. that doesn't mean that Perl is a good language to write applications in, or that Java is a bad one. You've probably run into Python programs written by people who don't know the language very well or just aren't very experienced at developing software that works.

Stevey: Apple has solved the distcc availability problem by leveraging Rendezvous. It advertises as _distcc._tcp.

markonen: Apple won't bundle readline, it's GPL.

hub: Although the Mach-O binary format does use "hardcoded" dylib paths (they are more like hints, though), the paths can be relative to an executable (as in an application bundle). This is how you are supposed to distribute applications. You can rewrite the load command paths post-link with install_name_tool(1), or influence the search path for dylibs at runtime with the dyld(1) environment variables (though I consider this a hack to be used only at development time).

The way dyld works is different (than dlls on win32 or "shared libraries" on Linux/BSD/etc.), but it most certainly not broken. It's just as flexible as anything else (actually more so, in many respects), you just need to RTFM.

osullivj: Although using generators to do asynchronous I/O might seem like a cute deisgn idiom, it's really just a silly hack to get around a fundamental flaw of the Python VM. There is a fix for this, called Stackless Python. The only tradeoff is that your code is no longer useful with a stock Python interpreter, but in many cases you control enough of the environment to where that isn't a big deal, beacuse you can just package up Stackless Python with your application. It's even binary compatible (bytecode and extensions) with regular Python.

elanthis, xf: Yes, if you order a *just announced* Mac, it will take a while to get. It's common knowledge, they will let you know approximately when it will ship. It's basically a preorder.

I don't know what there is to complain about. Apple has great customer service. If you want a computer that day, then go to the store and buy one... or call them up and ask "if I order this today, when will I get it?". They aren't going to lie to you.

URLs are Universal Resource Locators. Needlessly using query strings that break when you send a URL to a person on another computer (or another web browser on the same computer) is probably not a good idea if you're doing web development.

So just stop doing it, ok? It sucks for the users, especially if your script totally busts apart at the seams when the non-universal URL is visited by another browser.

lindsey: "C# doesn't force you to... This seems bad." No, it's not bad. Programming languages should do what you want, not vice versa.