I don't really want to provide any information relayed to me which might have been in private, but the gist is that server that my site runs off of is basically a one man operation (run by a friend of mine) and he's not going to have enough time to handle dozens of service requests on top of a full time job. Over time my access to the server has become less (first I was jailed, then the jail was more restricted, etc..) to the point where his newest server was not planned to have any shell access for users. These plans were all probably scrapped when his automated user system plan failed and he was basically forced into shutting down his server.
You are viewing an archive of posts for February, 2005. You can also head back to the blog home.
Been using ViM for a while, and decided to use the X version (gViM) for my Java class. The X version comes with a fairly gorgeous color theme, and I wanted it to actually come up every time I used it. I searched quickly for some way to do this in the GUI, but since its Vim I figured (rightly) that most things were done through the RC file. A little research on the Vim irc wiki got me a few options that I've wanted for a while, so I figured I'd share them:
Courtesy of OS Galaxy blog syndication came a link about Mockup, which is actually a bit hard to explain; or at least, its relations to the rest of my thoughts on the subject of desktop Linux (which I feel is still somewhat of an oxymoron.) The Register gave some light play at this Linux desktop perdicament today, and I mostly agree with their take on the freak mainstream and linux's preparation thereof.
Just when you figure you have something figured out, changes happen which change the dichotomy of the argument. The way QT4's Windows license is going to work out is that if you want to develop and distribute programs for free on Windows using QT, you can; provided that your work is released under the GPL. If you want to develop and distribute programs and not share the source, you can, provided you purchase a commercial license.
Sometimes I wish that one toolkit would just win, and then I wouldn't need to waffle back and forth between them. They can look the same and function quite similarly; it IS possible; but in the example image, I had to wrestle with spacing issues in Qt for quite some time in order to get it identical to the Gtk version. Part of me has just wanted Gtk to get better than Qt so that I could actually use it and not feel like I'm implementing parts that should be done for me (like cut&paste).
The average latency for blogposts has increased for me and for others, but the bandwidth has stayed about the same, regardless of what format I'd rather employ. The problem lately is that I detest my ¼ complete backend and the entire structure behind it; Jerm's decision, although heavily ridiculed by myself and yet others, was the right one, because he and I are of a particular breed of perfectionist that can either have everything absolutely perfect, or nothing being satisfactory at all. I am just not capable of doing small, incremental design changes; when I get into a process, I put my all into it, and when I back out, I forget about it and use that space for other things. I work best in batch mode, a-la Knuth.
public domain
