Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I use dreamhost's lowest cost plan for my personal sites. They have comparably poor security, uptime and performance, but they have enormous bandwidth and disk capacity for the money -- the disk capacity was the deciding factor for me. Plus they have a pretty liberal software suite and a rather nice control panel.

    I recommend them highly for personal and development sites, but I do not recommend their low-end offering for any site you actually care about.

    • Plus they have a pretty liberal software suite and a rather nice control panel.

      Yes, this is nice. However, they keep very tight reins on resource usage (time/cpu/memory), so it's difficult to do anything more than the most trivial software operation. (Your process will get killed by their resource monitor).

      I too would recommend Linode for anything other than static-page-serving/backup.

      There ARE (many) cheaper VPSes out there, but Linode seems to be the best in terms of avoiding disk failure. Personally, I'v

  • I just canceled my mostly doing-nothing Dreamhost account. I use Linode for everything now.

    --
    rjbs
  • See this thread [perl.org] from early this year. Fortunately, I did get all my money back.

    FWIW: I've been very happy w/ Bluehost since the switch.

  • I have about 10-20 domains currently sitting in one very cheap DreamHost account.

    Positives:
    Infinite (for most intents and purposes) disk and bandwidth, great control panel that keeps gets better, straight forward language, very low overhead to look after stuff in terms of my time. Doesn't force me to be a system administrator like most of the virtual machine places. Despite shared hosting, I can still get SSH, SVN, etc access.

    Downside:
    No CPU. No Memory. Less ability to do REALLY custom things.

    So I have two