Ask HN: Programming with Visual FoxPro
I've the opportunity to work in an interesting project. The problem is that I would have to program using Visual FoxPro and I don't know if I should.
I'm beginning to program using Python/Django and I really like the language. I've some projects(mostly web) that I would like to develop in the future.
What do you think, to program using Fox could be useful for my future projects?
So here's my take from a python lover that works with old MS technology (ASP in my case).
It all depends. There's nothing wrong with working with an older technology when you have to. Not everything is state of the art and it's good to understand that developing from a blank canvas is nothing like developing on a legacy system. It's humbling to think that at one point, the author of the system you will be working on sat down and thought about how wonderful their new baby would be too.
That being said, it's draining to work with dead technology. It doesn't matter how wonderful the project is, you can't escape that nagging feeling that every minute you spend in the dead tech is a minute you're not spending learning the new tech, and that you're falling ever so slightly behind.
My level of python knowledge hasn't improved as much as it should have since I began learning it back in 03 ish. Since then, with django and others that language has exploded, while I have plateaued. This is because 80% of my working hours are spent in dead technologies.
It's something to ponder as you make your decision, but I'd need more information to point you in a specific direction.
If it isn't a long-term commitment then I think it could be a helpful learning experience even if you never (hopefully?) use the technology again.
In 2004 I had to build a data collection app using MS Access to help a law firm client prepare for a trial. It actually ended up being the best tool for the job because they were operating in a Microsoft environment, the app was a throwaway and Access was a quick means to an end, in this case a self-contained GUI front-end and (in its own way) relational back-end.
It was fun not to care about the technology choice and to instead focus entirely on building a professional-grade application.
And if you're getting paid to learn something new, that's pretty cool too, and provides more perspective when returning to Python or whatever.
Depends on how long it is. If it will tie up substantial amounts of time (months, years) that you would rather put towards your future projects, then no.
If it's shorter term - then yes. Learning something new is always valuable (it teaches you to think better) and working on interesting projects is what this is all about.