|
|
|
|
|
by jrockway
1915 days ago
|
|
I think if you require users to bring their own computer, you can be insulated enough from hardware costs to not really care about memory usage, and that's mostly fine. I have worked on set top boxes at an ISP. We designed and manufactured the hardware; if we could get away with 512MB of RAM instead of 1GB of RAM, that was basically pure profit for us. So some attention was paid to memory use, because it had a real dollar cost associated with it. (I guess I'll point out that the engineering samples had a gig of RAM, and someone got the idea to write the UI in Dart running inside Chrome instead of the very legacy Java that we had on the previous hardware generation... so the production models did not ship with 512MB of RAM.) To some extent, being careful about memory usage is not the only way to make the business work -- you could, after all, charge more for the service or make people buy the CPE outright. But, being an ISP mostly involves getting enough people to buy the service to make it worth digging up a neighborhood to run fiber; you don't want to sour the deal by costing more than the competition with less able CPE. Doubling the RAM available to software engineers may improve the user experience by more than 100%, but nobody picks their ISP for the software than runs on their TV box, so it's probably wise to be careful. My point here is that some programmers do have to care about memory usage. If you include a computer as part of your product, you will someday be looking at the BOM cost of the bundled computer in an attempt to turn cost into profit. |
|