I've been in a bit of a debate regarding SOAP vs. REST web service interfaces. I found this post on why Google is dropping their SOAP search API. Here's an excerpt :
Here are some thoughts on those test frameworks :
- PHPUnit : Good for back-end work, but weak with front-end (browser) work
- SimpleTest : Same as PHPUnit
- Watir : Very mature and popular browser test app, but requires knowledge of Ruby scripting language
The other day I was downloading several podcasts from the net, while doing an expensive rsync across my slow home network. My dual core CPU was showing 50% on one CPU, about 0% on the other, and my network was shown at about 1%.
My iTunes had a "download multiple streams" checkbox that was unchecked. I thought running multiple streams might actually slow things down due to thrashing/context switching, but I checked it to give me multiple streams.
I had an earlier article about how diversifying into commodities can give higher total returns with lower volatility.
But now the question is, how should one invest in commodities? Do like my high school physics professor who bought a bunch of copper tubing during the Jimmy Carter memorial inflation of the early 1980s?
Lately, I've been looking to increase the diversification in my retirement portfolio by investing in both commodities AND long-term bonds.
Crazy? Aren't these diametrically opposed views? Commodities love inflation, just like long-term bonds hate inflation.
It's hard to say where inflation is headed, although at least relative to now it seems likely to go up. But how much more inflation can we expect, and more importantly, now much of that is already priced in long-term bond prices.
I had a case where I had to build Git on an older Red Hat based system. Unfortunately, the system was so old that yum wasn't really supported. So I had to install the needed libraries (RPMs) "by hand" via rpm -i. There was one package that I had to update via rpm -U.
On my rather bare system, I found I had to install the following RPMs to get Git to compile :
cpp curl curl-devel e2fsprogs-devel gcc glibc-devel glibc-headers glibc-kernheaders krb5-devel krb5-libs make openssl openssl-devel wget zlib-devel
When upgrading servers, you may encounter this question : Should we stay at at 32-bit OS, or 'upgrade' to a 64-bit OS?
To me, the big advantage of a 64-bit OS is the ability to address (use) more than 4 gigabytes of RAM. I sometimes bump into that limit on my desktop,
so I think it's best to have a 64 bit OS for servers.
Larger memory space isn't the only advantage, however. From Wikipedia :
I'm not sure of the cost/benefit of spell checking of source code, but there seem to be a couple cheap/free utilities that can help with this.
Free Python package :
Commercial shareware - $59.99 (Windows)
Another commercial shareware version - $39.99 (Windows)
Here's one man's experience checking Java source code with a "generic plain English" spell checker :
I had some patches in one Git repository that I wanted to apply to a different repository. Here's a useful link I found on this :
Here's what I did.
First, copy the original repository you want to get patch from. This may not be necessary in all cases, but in my case the original repository was on another machine, so this just puts everything on the same machine.
$ git clone ssh://email@example.com/repos/origRepo $ cd origRepo