1.) Don’t commit after every update statement
2.) Don’t commit once for every update statement
Both of those are really meant torwards updates that come in large groups. For example I dropped over 4000 rows out of database at work over the past month. One commit for that many rows is not a good idea. But one commit after each row is a bad idea too. Instead commit in smallish groups.
Merry Christmas!
Enjoy the Penguins!
I just saw a headline on LXER that reads:
Debian women may leave due to ’sexist’ post
Truth be told here, in my opinion, any project that has to have a special team just for women already has much deeper issues than some stupid post on a mailing list. Gentoo has women developers I’m sure. They hold no special title the men do not hold and are in no special groups. I think Exherbo has at least one. If thats actually a man with a girl’s name I apologize and recommend you to Johnny Cash.
Regardless, I don’t know whats going on in Debian Land, but trouble is brewing. If Debian wants to reach out to female Linux users, which I find to be silly, there is no need for a special female swat team to wrangle them up for you. In all honesty, woman, like men, will use what they want. If that’s not Linux, then thats to bad. Stallman has spent almost two decades (if not more) trying to convert anyone, much less men. And, well, all its earned him is a reputation as a GNU gnut job.
Enjoy the Penguins!
The problem I find with programming books like 90% of the education texts out there is that they are so dry. As a mathematics and history major in college no one understands dry reading better than I. Between those two subjects I think I’ve pretty much covered all the bases so to speak. One book I have found that isn’t quite as dry as the rest that I own is Programming Ruby: The Pragmatic Programmers’ Guide. Once you make it past the first chapter, which is your typical dry (and overly brief) run through of your basic programming structures, it actually becomes a very entertaining book. You make a mock juke box which sounds stupid, and it is, but its presented in a fun and entertaining way that holds your attention despite it being quite stupid. I’d recommend it if you don’t own it. I’m sure someone will be quick to point out you can read the book for free on the internet… but don’t that version is old and full of bugs. A lot of which appear corrected in the version I own. Which I can describe no better than as the Second Edition.
Enjoy the Penguins!
Its not often I find decent computer things to read on the internet but since I have found something nice to read I will share it. Its entitled, The Problem With Threads. That link is a direct link to the PDF file from Berkeley.edu, which has way to many “e”s in it. Do enjoy, I found it very interesting.
Enjoy the Penguins!
I recently read a post on Planet Larry about someone trying out OpenRC. Does anyone else know anything about it? I’m curious and would love to try it, especially if it really is “better.” But on the same hand I just got Gentoo installed properly and would hate to destroy before I even get it fully setup.
Enjoy the Penguins!
Well, I finally Gentoo installed again and half way configured. I’m running AMD64 with Fluxbox and Awesome and I’m logging in through SLiM. If you goto the Gentoo Wiki I wrote the whole page on SLiM so if you need help setting it up I think I’ve pretty much covered everything. I started the page on Awesome and as of this writing I’m still the only one to contribute to the page. If you goto it you’ll be able to see how much I know about it. Which is basically nothing. I didn’t get SLiM fixed till the other night so I’ve honestly only ever logged with Awesome as my window manager once. Its a work in progress.
I re-started the page on Paludis there too. Someone else came in and did a lot of work on it though. Thus if you don’t like it odds are it wasn’t me. I started at least one other page but as you can tell by me not remembering it, it isn’t important.
I posted previously on writing a Vim plugin to pull vimrc’s off of Google Docs using the Google Docs API. Well there isn’t really an API there. Not one worth mentioning. All it really lets you do it list the files for someone. Though it does curiously enough let you upload new ones, but provides no method for downloading them. Thus I’ve given up on the Vim plugin project. Pulling the vimrc off of Google Docs without an API would very painful and not worth my time. I did learn a lot about ruby though, and python strangely enough.
Enjoy the Penguins!
Well, it basically sucks. So never mind.
Enjoy the Penguins!
I’ve never written by own Vim plugin but I spent the past couple of days hacking other peoples to see if I could get them to do things they weren’t intended to do. Well, the good news it did what I wanted it to do. The bad news is, what I wanted it to do doesn’t work. Life can be mean to you like that sometimes. I have learned a lot though.
Speaking of which. Wow, what happened to WordPress? I’m using the free version from WordPress. Needless to say things have really changed. For the better I think though. I’m still a little lost in the interface though. I dont’ know.
Back to Vim though. Vim has extension for Python, Ruby, and Perl. The problem for me, is while I’d like to write my extention in Ruby, Google Docs only supports Python. Okay, Google Docs’ API supports other languages, but of those three, it only does Python, so I’m going to attempt a crash course in Python in order to make my own plugin. Wish me luck!
Enjoy the Penguins!
First, I’ve updated my vim scripts again. Please don’t ask me what changed. I don’t know and I don’t keep them in a git repository. Personally, I think me opening up a free account at like say GitHub just for that is a waste of space. If I had a legitimate project there I would consider it. I find it funny I just said all that because no one has ever once asked what I changed.
Has anyone ever noticed how horribly close Perl syntax is to bash? Why?! Did the guy just want to re-write bash with extra options and then use it on his Windows box? There is no reason. Bash is really a very ugly language and Perl, looking just like it, is ugly as well. Why anyone would ever really want to use either is beyond me. Knowing bash is more or less necessary. But I would never want to do a whole program in it. That’s crazy (and for more reasons than its ugly).
Enjoy the Penguins!
