| 
| Results |  
| 
| Choice | Votes |  | Percent |  
	| No flash ROM technology | 9 | 11.7% |               |  
	| No linking capability | 22 | 28.6% |                                |  
	| No programmability | 2 | 2.6% |     |  
	| Cut processor speed in half | 11 | 14.3% |                 |  
	| Cut available RAM in half | 16 | 20.8% |                        |  
	| 25% reduction in display resolution | 17 | 22.1% |                          |  |  
| 
 
| Re: If you were forced to make one of the following sacrifices on your favorite calculator model, which would you choose? |  
| Travis Evans   |  
| 
My favorite TI model being the TI-89(t) and non-TI model being HP 50g, in a way I've already made a sacrifice of reduced display resolution on the HP: 160x100 vs. 131x80 (that's more like a 34.5% reduction).  But it's not so bad since the HP has better display and font customizability and tends to make better use of the pixels overall.
 |  
| Reply to this comment | 24 December 2012, 21:50 GMT |  |  
| 
 
| Re: If you were forced to make one of the following sacrifices on your favorite calculator model, which would you choose? |  
| calcvids   (Web Page)
 |  
| 
Considering most of my calculator usage is on non-Flash devices (83 and 86), I wouldn't necessarily miss losing Flash. 
 |  
| Reply to this comment | 25 December 2012, 09:26 GMT |  |  
| 
 
| Re: If you were forced to make one of the following sacrifices on your favorite calculator model, which would you choose? |  
| Stefan Bauwens   (Web Page)
 |  
| 
No programability ofcourse! :PNo, I chose the  last option, although I doubted to perhaps choose the speed reduction.
 |  
| Reply to this comment | 25 December 2012, 15:53 GMT |  |  
| 
 
| Re: If you were forced to make one of the following sacrifices on your favorite calculator model, which would you choose? |  
| Zeroko   (Web Page)
 |  
| 
The only one that can be fixed is lack of programmability, of course. (^_^)
 |  
| Reply to this comment | 25 December 2012, 20:03 GMT |  |  
| 
 
| Re: If you were forced to make one of the following sacrifices on your favorite calculator model, which would you choose? |  
| Travis Evans   |  
| 
Another possibility in the case of calcs with built-in card readers (like HP 50g) is lack of linking, since I can and do get along just fine transferring stuff to/from the PC and other calcs just using the SD card. Perhaps that might be considered cheating in a way, though. :-P
 |  
| Reply to this comment | 25 December 2012, 23:55 GMT |  |  
| 
 
| Re: If you were forced to make one of the following sacrifices on your favorite calculator model, which would you choose? |  
| jiangshi   |  
| 
I suppose our choices depend a lot on what we are using our calculators for. I chose to sacrifice linking because using the calculator ( TI-92+ ) for mathematics including graphing is more important to me than connecting to my PC or another calculator.
 |  
| Reply to this comment | 29 December 2012, 17:33 GMT |  |  
| 
 
| Re: If you were forced to make one of the following sacrifices on your favorite calculator model, which would you choose? |  
| Ranman   (Web Page)
 |  
| 
This is a no brainer. Cut CPU speed in half -- force us to be better, more efficient coders.
 |  
| Reply to this comment | 4 January 2013, 18:25 GMT |  |  
| 
 
| Re: If you were forced to make one of the following sacrifices on your favorite calculator model, which would you choose? |  
| ghest1138   |  
| 
Half the RAM! I don't ever use that much on my 83+, but I don't think it would be that big of a sacrifice. The TI-81 works just fine with only 2.4 KB of RAM (Well, sort of fine)
 |  
| Reply to this comment | 5 February 2013, 21:11 GMT |  |  
| 
 
| Re: If you were forced to make one of the following sacrifices on your favorite calculator model, which would you choose? |  
| Adept   (Web Page)
 |  
| 
Wow, the only reasons someone would put 25% reduction in display resolution is because they're trolling! :P Jesus Christ, imagine how crappy it would look if it was 72x48! That would be murder! :D
 |  
| Reply to this comment | 2 May 2013, 05:04 GMT |  |  |