Thread: @ / to rom devs
View Single Post
  #3 (permalink)  
Old 10-20-2008, 01:30 PM
spetrillo's Avatar
spetrillo
VIP Member
Offline
Location: Pearl River, NY
 
Join Date: Mar 2007
Posts: 1,019
Reputation: 679
spetrillo knows their stuffspetrillo knows their stuffspetrillo knows their stuffspetrillo knows their stuffspetrillo knows their stuffspetrillo knows their stuff
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: @ / to rom devs

Quote:
Originally Posted by rstoyguy View Post
Some like to have a rom ready to go. And that's what makes all the rom's different. Each chefs personal touch or programs installed. Everyone pretty much has the same ingredients available to them, it's what they include in their app list that makes people download and install their rom. And by apps, I mean skins or themes as well. Some offer a clean version you can customize as well. Before I learned how to cook, I would go with a "full" rom, then I went through a period of wanting a "clean" rom with uc that I could customize with .cabs, then I found nexvisions hulk rom and decided to cook them myself.

It's all a personal preference I suppose
This is the great dilemma affecting all chefs. I personally started with a 6700, so I had to keep my ROM lean and mean just so it would fit. On my 6800 I was afforded more room, and thus I included a bit more stuff. On my current 6900 I am actually back to the debate of all in or all out. Current thought was to leave the ROM lean and mean, and then CAB everything else. Doing it this way gives you the most flexibility when new releases of things you use come out. You dont have to continually flash a new ROM. Just uninstall the existing CAB, soft rest, and then install the updated CAB.

I am sure the pendulum will swing the other way soon enough for me. In fact I am starting down that route with the 20755 kitchen.