In case you forgot tomorrow is the last day to cancel or change your rate plan on Netflix. Starting September 1st Netflix will introduce a new plan that is 60% higher than the current DVD/Streaming option today. Not only are they raising the prices without any help from you (read: they will raise the rate automatically) the execs at Netflix actually had the nerve to mask this change as a good thing for users. Sure, raising rates is always best for the user.

Okay, here goes:

Dear Reed Hastings (Netflix CEO),

I have been a Netflix customer for quite some time, you know, when all popup ads were from Netflix and every 3rd spam email was your friend asking to join because it was the hottest thing since Pets.com. Well fast forward a few years and you guys have forced me to cancel a service I once loved. You have decided instead of building a better product to screw everyone that helped your company get to where it is today. Rather than realize not everyone* has the ability to pay more for less you decided to make the product basically worthless. With so many better options, Redbox for DVD/Blu-Ray rentals and Hulu Plus, torrents and so many other sources for online content, Netflix doesn’t serve a purpose.

You could have grown the company while working with more providers to beef up the streaming service, remove stupid expiration policies on streaming content and then (after you built up streaming) split the two options. However as it stands right now with device restrictions and limited library I wouldn’t be surprised if your companies marketshare started to slip.

Lastly, as a developer, i’ve loved working with the Netflix API in the past but you even started to make that suck.

Its time to close our accounts, just like we did those annoying popup ads back in the early days of the web.

Sincerely,
M. Keefe
Ex Netflix Customer

* One note, i’m not saying I can’t pay 60% more, I just don’t think anyone should have to.



After using Lion since the day it was released (about a month ago) I feel the need to warn others! First off the install/purchase process is all handled through the Mac App Store*, which is interesting. No real opinion on that. Once the file was downloaded the installation is like any other OS X install, until you get to the part where Lion loses your account profile (sometimes) and locks you out of you own damn machine.

Now you better have another internet connected device because you need to Google and find the fix. Then wait about an hour for your profile to be recovered. Once you have everything ready you get to watch some of your apps get removed and locked away because Lion removed support for PPC, without any warning that I saw (other than release notes). For me the only app that got removed was Dropbox, but others have lost much worse.

At this point you should be back to using your computer as you were before upgrading, but wait, things seem “iOS like”. Thats correct, Lion is a “iOS++” and it sucks. iOS does convert to desktop usage all that well. Starting with the “natural-scrolling” which is a great thing to argue with other Mac fans.. but I don’t like it. Then comes the “hidden scroll-bars” but the worst part is the fact Lion is a memory and resource hog. I get the “beach ball” more now than I did before. Not being happy with performance I upgraded my MacBook Pro with 8GB of ram and its still not as performant as Snow Leopard was.

I’m sure you are asking, why post this? Simple, after a quick comment on Twitter this morning it got me thinking that Apple really doesn’t care about the desktop market or computers like they once did. Apple is all focused on mobile which is great for iOS but not so much for OS X users.

I guess desktop users are like the dinosaur to Apple, only problem is desktop development and usage is still as popular for actual users. Not “smartphone users” that need to check-in to the local McDonalds. It will be interesting to see how the next couple of years shift developers away from OS X. Which honestly will suck since their are some awesome apps, Transmit, Versions, 1Password, Things and TextMate, to name a few.

* Well I do have one bitch, that being Apple gets a cut of the sale and doesn’t offer trial versions. Not to mention soon they will drop the hammer on “forbidden apps” just like they did with iOS.

While working on a project I found the need to create subdomains on my local server to shorten the localhost URL and test some of the core features I was in the process of developing. After scouring the internet for quite some time and getting conflicting tips/tricks I finally got everything configured. However for my own future use and anyone else interested I figured i’d write a quick little post about the process.

For those unfamiliar with what MAMP is, you can check it out here.

As the title states this guide is for MAMP installations however most of the information can be re-used for other systems.

Editing the /etc/host file

Start by editing the host file, located in the root of your computer. You cannot see this file in Finder due to it being hidden (though PathFinder can) so open Terminal (/Applications/Utilities/Terminal) and type the following command

sudo vi /etc/hosts

The sudo command will require you to enter your password, and assumes temporary or “sudo” root for this task.

Note: If you use TextMate you could replace the “vi” portion with “mate” and it will open the host file inside TextMate for much quicker editing. Though you will be required to enter your password to save your changes.

Once you enter your password  you’ll be presented with a text editor. Type “i” to be able to edit the file, navigate (with arrow keys) to the 127.0.0.1 localhost line and replace it with:

127.0.0.1 localhost mysite.localhost.com

Replace mysite with your desired subdomain. Then save the file by hitting ESC and typing SHIFT+: then type “wq” and hit ENTER. This will write the file to disk and close the file.

Editing the Apache configuration

Now that the host file has been configured we need to set up the Apache portion. If you typed “mysite.localhost.com” in your web browser it’d either show a “server not found” error or display the default MAMP directory. We obviously want to display the new location, whether it be a new directory or a completely different location on your local web server.

Open Finder and navigate to the MAMP installation directory to locate the httpd.conf configuration file. The full path (default) is:

/Applications/MAMP/conf/apache/httpd.conf

Open the httpd.conf file and scroll all the way to the bottom. You should see a note about Virtual Hosts, such as:

### Section 3: Virtual Hosts
## VirtualHost: If you want to maintain multiple domains/hostnames on your# machine you can setup VirtualHost containers for them. Most configurations# use only name-based virtual hosts so the server doesn’t need to worry about# IP addresses. This is indicated by the asterisks in the directives below.

Add the following line of code, which enables name based virtual host mapping.

NameVirtualHost 127.0.0.1:80

After that add the following block of code. Which configures the path to your virtual hosts. The first block of code always has to be your default since Apache routes linear, which you may be familiar with using ModRewrite.

<VirtualHost 127.0.0.1:80>
ServerName localhost
DocumentRoot /Library/WebServer/Documents
</VirtualHost>

Then add the block for your new subdomain.

<VirtualHost 127.0.0.1:80>
ServerName mysite.localhost.com
DocumentRoot /Library/WebServer/Documents/mysite
</VirtualHost>

Now restart MAMP (either by opening/closing the app OR opening and closing the preferences panel) for your changes to take effect. Now when you type in “mysite.localhost.com” in your web browser you should see your new directory (or 404 if you haven’t actually created the directory yet).

Update: For those not using MAMP you just need to edit the httpd.conf file located wherever you installed Apache. Then just use the command line to restart Apache. If you’re scared of the command line you can also restart your entire computer, though that may take upwards of 3-10 minutes depending on your setup.

Thats all. To recap we edited the /host file and httpd.conf configuration file to enable subdomains on a development server to more closely resemble the live environment (which is always the goal).

« Prev - Next »