Recommendations for RPN Calculators?
sg3000 asks: "My trusty old HP 48S graphing calculator, that served me since engineering school, seems to be giving up the ghost. I haven't used it in a few years, but recently I put new batteries in it. It works, but it makes a loud static/white noise sound when it's on. The noise is not as noticeable when I hold it, but when I set it down on a hard surface, it's really loud. Then it sucks the batteries down incredibly fast (I put new batteries in it, and two days later, they were drained). Any suggestions on what I should buy as a replacement?"
"I'm in graduate school now, and since I'm taking an accounting course, where they don't want us digging out our laptops during a test, I need to buy another calculator. I'm a big fan of reverse polish notation (RPN), so I'd prefer to get another HP calculator.
Do companies still make calculators? I'd love to get another HP 48, but I'm not even sure if HP even makes calculators like that any longer -- on their web site, they're all cheapo-looking single line deals. I've read about something called an HP 48g, but HP has nothing about it on their web site."
Why does HP's current calculator lineup suck?
Depending on how hard you work your calculator, you might do better to get a PDA and run a calculator program on it. If you bang on your calculator keys for hours, get a real calculator.
I use Palm PDAs (my current one is a Tungsten T) and I run a program called RPN on it. It's programmable and it has graphing, but I haven't used those features; but as a general-purpose RPN calculator, it's kept me happy.
What I really want is something similar to Palm RPN that is programmable in Python.
Anyway, the best thing about this is that I always have it with me. I used to have an HP calculator, but it was never handy when I wanted it.
steveha
lf(1): it's like ls(1) but sorts filenames by extension, tersely
The same team that made the 48 worked on the 49.
The only 'problem' with the 49 is the soft non-clicky keys.
Although, it has the added benefit of not being piss slow and has a (thank God) hard case.
I agree that keypresses saved are minimal, if not sometimes nonexistant in simple equations. In fact, for many simple single-operation equations, the process of learning RPN is far too complicated to justify using it at all.
RPN, however, can be likened to the Dvorak keyboard layout. It is entails a slightly involving process to learn. For many purposes, this is simply a pain. The true power only shines in complicated equations, such as those which make use of brackets.
The following equation shall be typed on an algebraic calculator, followed by an RPN calculator. [;] will be the button name for [Enter].
25 ( 46 ) + 254 - 2462 / ( 645 - 2453 )
Algebraic:
25*46+254-2462/(645-2453);
RPN:
25;46*254+2462;645;2453-/-
In the above example, you will realise that the number of keypresses is exactly the same. (In fact, if you cheat and leave out the second bracket on the algebraic calculator, that calculator edges out the RPN by one keystroke!) However, there are three immediate benefits to the RPN calculator:
Over time, the amount of keypresses will not really be changed too drastically. However, the true power is the convenience and the ease of use. Unfortunately, like the Dvorak keyboard, RPN will slowly fade in the non-specialised markets due to the fact that it takes too much time to learn.