Second, realize that a "sweeping rewrite" entails just as much work as the first write. The only thing you will (should) get from current code is a functionalty demonstration. (I.e., the current version is a "throwaway" prototype.)
Then, take everything you know about software development, learn a lot more, write the requirements specification, get it approved, then start thinking about technology, languages, and design. Coding should be about a third of the effort - the middle third. (Final third is test/debug/test cycle. If you didn't know that already, then don't even attempt this.)
Slashdot Mirror
First, read all previous comments.
Second, realize that a "sweeping rewrite" entails just as much work as the first write. The only thing you will (should) get from current code is a functionalty demonstration. (I.e., the current version is a "throwaway" prototype.)
Then, take everything you know about software development, learn a lot more, write the requirements specification, get it approved, then start thinking about technology, languages, and design. Coding should be about a third of the effort - the middle third. (Final third is test/debug/test cycle. If you didn't know that already, then don't even attempt this.)