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

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Respect

Respect is something humans give to each other through personal connection. It’s the bond that forms when we recognize something—or someone—as significant, relatable, or worthy of care. This connection doesn’t have to be limited to people. There was an  article  recently that described the differing attitudes towards AI tools such as ChatGPT and Google Gemini (formerly Bard). Some people treat them like a standard search while others form a sort of personal relationship — being courteous, saying “please” and “thank you”. Occasionally, people share extra details unrelated to their question, like, ‘I’m going to a wedding. What flower goes well with a tuxedo?’ Does an AI “care” how you respond to it? Of course not — it reflects the patterns it’s trained on. Yet our interaction shapes how these tools evolve, and that influence is something we should take seriously. Most of us have all expressed frustration when an AI “hallucinates”. Real or not, the larger issue is that we have hi...

Friend vs Therapist vs LLM: Shades of Grey

The conversations with AI series brings up a single point and then compares it between different LLM engines. These types of conversations were one of the many contributing factors to my writing of " Towards Consciousness " that explores the benefits and issues of creating a conscious AI. In this scenario, I was interested in seeing how an LLM might differ from a friend or therapist on issues that may have nuanced responses or contexts. In doing so, I came up with an interesting discussion on shades of grey. My Premise: Is it a bit strange to be using an LLM as a sober second thought? Every time I walk down this path of “why use an LLM to do certain things”, I come back to the alternatives that people like to say. “Why not bring it up with a friend?” A friend typically has your back or will say whatever to support their own agenda. “A therapist?” That’s someone who is “trained” to be impartial. But a computer? A computer is impartial based on two logical outcomes. If you say ...