I agree: aim to get both (ultimate desktop workstation with a laptop/netbook for portability). As a bonus, it can be useful to have a spare computer (like if the need should arise to consult the internet while installing Arch Linux, or something).
If it's not economical to do both right away, then start with one, and eventually add the other.
To all proponents of dynamically typed languages: How do you deal with this situation? Is it something you encounter on a regular basis? Or is there some holy grail of code maintenance in dynamically typed land as well?
Have any of you guys that strongly enjoy dynamic typed languages tried implicit-but-statically typed languages like C# and F#? If so, have you used them enough to form reasons for the paradigm you like more?
Really, the only times I've had these sorts of problems (while not using a REPL) is when I've been using code that was ported from a statically-typed language, so I'm guessing a different sort of dynamic programming style or code maintenance emerges. I'm having trouble pinpointing what these differences are at the moment, but perhaps someone who's investigated this issue more deeply has some suggestions for us.
Other advantages include getting to work with a strongly typed language, traditional OOP support, more advanced debugging tools, better asset creation tools, and a nice library of free code.
There are people who also consider prototypal inheritance an advantage (over the non-"traditional OOP" classical inheritance that you speak of).