Skip to main content

MVC architecture and VFP on Rails

After hearing about Brian's speech to the Chicago Fox User Group and then reading more from Randy Jean's Blog: Exploring VFP on Rails, I just wanted to try it on my own.



Randy's post goes into a lot of great detail with some code, so I'll let you read it there but the benefit of VFP in a Rails style environment is that it's SUPER easy to create an application to get you started: create a web share and register a single very small COM server. That's it.



And then you can customize it on the fly.



I know of a few developers who downplay the "buzz" of Rails, noting that it's not as scalable as some environments or that all of the tools just aren't there. 37Signals, part of the group that created RubyonRails or at least made it super popular with their BaseCamp and other related sites, addressed this in their Getting Real book - with their approach of interface first, then worry about scalability. (you can read it online here) - the main take-away from that was:



"If you’ve got a huge number of people overloading your system then huzzah!

That’s one swell problem to have. The truth is the overwhelming

majority of web apps are never going to reach that stage."



Many VFP developers may cringe at that approach - you should plan for scalability - but one can't argue with the success that this company has had with it and if you can build in new features in days instead of months, it might be worthwhile.



I'm going to be interviewing Brian for an upcoming FoxShow and we'll also do a screencast along with it. And no, it won't take 12 months for a new FoxShow <g> - it will be up by mid-next week.









Powered by ScribeFire.

Comments

Anonymous said…
VFP developers have been accepting low scalability for their web apps, like with Ruby, for years by using file-based West Wind webconnection. Anybody that has a really busy site using that technology knows the pain..

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...