Warning: Constant ABSPATH already defined in /home/public/wp-config.php on line 27

Warning: Cannot modify header information - headers already sent by (output started at /home/public/wp-config.php:27) in /home/public/wp-includes/feed-rss2-comments.php on line 8
Comments on: Haloscan Not Talking https://whynow.dumka.us/2009/02/28/haloscan-not-talking/ On-line Opinion Magazine...OK, it's a blog Sun, 01 Mar 2009 05:03:19 +0000 hourly 1 https://wordpress.org/?v=6.4.3 By: Bryan https://whynow.dumka.us/2009/02/28/haloscan-not-talking/comment-page-1/#comment-43176 Sun, 01 Mar 2009 05:03:19 +0000 http://whynow.dumka.us/?p=7893#comment-43176 Given the cost of hardware, I’m having a hard time understanding why anyone doing anything 24/7 isn’t using RAID. I remember paying $800 for a 10 MB drive back when a new pick-up costs $7K, so skimping on hardware is rather foolish.

I hate mergers and acquisitions, the users/customers always get shafted.

]]> By: Steve Bates https://whynow.dumka.us/2009/02/28/haloscan-not-talking/comment-page-1/#comment-43174 Sun, 01 Mar 2009 04:28:46 +0000 http://whynow.dumka.us/?p=7893#comment-43174 Actually, they got it going after about half that time.

One commenter on the service blog asked a very reasonable question, though: why was the crashed HD not in a RAID?

The new project leader (well, new since JS-Kit took over) has a pretty good attitude, seems to have inherited a mess, and has been completely candid in his communications with irate users (including me) about the nature and magnitude of the problem. I just hope his candor doesn’t get him fired by the new owners, who may be a bit more, um, corporate than the previous ones. (I’m speculating; I have no evidence of that.)

]]>