Now studios can release one disc that is pretty much universally playable. This should go a long way to encourage the adoption of HD-DVD AND Blu-ray. If these discs become prevalent, and people realize that they could upgrade their DVD player to a Blu-ray player, and still play their last 10 movies, but in higher quality on their HDTV, they might actually consider the upgrade. As opposed to now, where people might not upgrade because they must buy NEW movies and start a NEW collection in order to enjoy what they see as "slightly" better picture quality over DVD (as well as massive DRM!).
If I was a movie studio executive, I would support these triple-layer discs at any cost.
I am working on a small (around 40,000 lines) 2D platform-style game in C using the Allegro library. I started the development last year in MSVC 6, because that was all I knew (before switching to Linux). Now that I use Linux, I learned vim, and enjoy it immensely for smaller projects, Makefiles, etc. Even though I found vim's taglist plugin, which allowed me to navigate between functions quickly like I had been used to, I found it insufficient for my needs. Eclipse CDK sounds nice, but I stopped trying to use it after about a half hour because it was far too bloated for my Dell laptop with a Celeron processor. I eventually settled on Anjuta, which I find amazing. I like how you can have it list every function in your project (distributed across multiple source files even) listed alphabetically on the left side. Autocompletion is nice, saving me typing time, and one key build + one key execution = saved time as well. I discovered Code::Blocks from this thread, though, and will investigate.
In the end, if I'm developing in C, I use: vim for smaller files, because it is better at moving text around, Anjuta for larger projects, because it is better at navigating through all the files/functions, and MSVC if I HAVE to because I'm on a Windows Only environment where I can't install anything else (like work!). The End.
I thought Google's solution for this was to transition from a click-based revenue model to a transaction-based revenue model. That is, instead of charging per click, they charge per each successful transaction that occurs as a result of the ad's placement. If 0.05% of clicks result in a sale, for example, they would charge 2000 times one click for each successful sale. Of course, if no sales occur, this would result in less revenue for Google; they would have to enforce a floor charge to ensure they make money from every advertisement.
Slashdot Mirror
Now studios can release one disc that is pretty much universally playable. This should go a long way to encourage the adoption of HD-DVD AND Blu-ray. If these discs become prevalent, and people realize that they could upgrade their DVD player to a Blu-ray player, and still play their last 10 movies, but in higher quality on their HDTV, they might actually consider the upgrade. As opposed to now, where people might not upgrade because they must buy NEW movies and start a NEW collection in order to enjoy what they see as "slightly" better picture quality over DVD (as well as massive DRM!).
If I was a movie studio executive, I would support these triple-layer discs at any cost.
I am working on a small (around 40,000 lines) 2D platform-style game in C using the Allegro library. I started the development last year in MSVC 6, because that was all I knew (before switching to Linux). Now that I use Linux, I learned vim, and enjoy it immensely for smaller projects, Makefiles, etc. Even though I found vim's taglist plugin, which allowed me to navigate between functions quickly like I had been used to, I found it insufficient for my needs. Eclipse CDK sounds nice, but I stopped trying to use it after about a half hour because it was far too bloated for my Dell laptop with a Celeron processor. I eventually settled on Anjuta, which I find amazing. I like how you can have it list every function in your project (distributed across multiple source files even) listed alphabetically on the left side. Autocompletion is nice, saving me typing time, and one key build + one key execution = saved time as well. I discovered Code::Blocks from this thread, though, and will investigate.
In the end, if I'm developing in C, I use: vim for smaller files, because it is better at moving text around, Anjuta for larger projects, because it is better at navigating through all the files/functions, and MSVC if I HAVE to because I'm on a Windows Only environment where I can't install anything else (like work!). The End.
I thought Google's solution for this was to transition from a click-based revenue model to a transaction-based revenue model. That is, instead of charging per click, they charge per each successful transaction that occurs as a result of the ad's placement. If 0.05% of clicks result in a sale, for example, they would charge 2000 times one click for each successful sale. Of course, if no sales occur, this would result in less revenue for Google; they would have to enforce a floor charge to ensure they make money from every advertisement.