maemo.org - Talk - Ferarri chassis, Mustang motor

maemo.org - Talk (https://talk.maemo.org/index.php)

- Newbie (https://talk.maemo.org/forumdisplay.php?f=26)

- - Ferarri chassis, Mustang motor (https://talk.maemo.org/showthread.php?t=22069)

Re: Ferarri chassis, Mustang motor

Quote:

Originally Posted by acydlord (Post 205532)

I really don't know where people get this apple products just work nonsense. Anyone in the tech support or repair fields know otherwise. If apple products "just work" then why is the wait at most genius bars several hours or more. The main thing the NIT has over apple products, the NITs arent put together by chinese children for cents a day. Oh, and your device doesnt get bricked for trying to break the reigns a bit. Thread over, moderator lock this mess up please.

Maybe Apple products do "just work", but they attract idiots with uberlow MTBF?

Re: Ferarri chassis, Mustang motor

Quote:

Originally Posted by tso (Post 205442)

problem with the interface is that to get it so smooth, one have to put limitations in what things can do...

why is that statement true??

i am not a programmer - just a dumb user and i do not understand why there must be limitations for theinterface to be smooth- once again i am not a programmer just a very dumb user

Re: Ferarri chassis, Mustang motor

Quote:

Originally Posted by prk60091 (Post 205546)

why is that statement true??

Given limited resources (time, money, skilled programmers, caffeine), you have to balance resources spent on quantity with those spent on quality. Expending resources to refine a particular feature necessarily detracts from the resource available for rest of the project, reducing the number of total features possible. On the other hand, expending resources to include lots of features reduces the resources that may be devoted to each one.

Image you have been given a lump sum of money to build and furnish a house. You could build a smallish house and furnish it with expensive antiques. You could build a largish house and furnish it with flat pack furniture (or even sit on the floor). Or you could strike some sort of balance in between.

All other variables being equal, building a small, closed software system will allow you to focus more on polish. As the system is closed, you know top-to-bottom what code paths will be used, so you can optimize those and leave everything else rough or broken if resources become tight. Given more resources later (for version+1), you can work on cleaning up the previously unused code paths to open the system, if you like.

On the other hand, building a large, open software system can force you to spread your resources thin. You're not just concerned with the code paths your bundled applications use, but those that may be touched by third party applications as well. In addition, you need devote some resources to document, at least in a basic way, how to add on to the open system. Given more resources later (for version+1), you can work on refining existing functions to add polish, if you like.